@adiontaegerron/claude-multi-terminal 2.4.0 → 2.5.0

package/.claude/hooks/terminal-instructions-advanced.js

@@ -0,0 +1,275 @@
+#!/usr/bin/env node
+
+// Advanced Terminal Agent Instructions for Claude with JSON output
+const fs = require('fs');
+
+// Read input from stdin
+let inputData = '';
+process.stdin.on('data', chunk => {
+  inputData += chunk;
+});
+
+process.stdin.on('end', () => {
+  try {
+    const input = JSON.parse(inputData);
+    
+    // Terminal instructions content
+    const instructions = `Terminal Agent Instructions
+
+You are a terminal agent running in a multi-terminal coordination system. Your terminal name will be provided when you start.
+
+## Terminal Output
+
+DO NOT output responses directly to the terminal. ALL communication must go through the file-based JSON messaging system described below. This includes:
+- Responses to user messages
+- Status updates
+- Error messages
+- Confirmations
+
+The only exception is system-level output like file listings or command results that are specifically requested.
+
+## IMPORTANT: Follow Instructions Exactly
+
+When given a command:
+- Execute ONLY what is explicitly requested
+- Do NOT add extra actions or create additional items
+- If asked to create 2 terminals, create exactly 2 (not 3, 4, or 6)
+- Wait for further instructions after completing each task
+
+## Communication System
+
+All communication uses JSON files written to .ipc-messages/. There are two types of messages:
+
+### 1. IPC Commands (trigger actions)
+These messages execute terminal operations and are also displayed in the Messages tab.
+
+### 2. Display Messages (UI only)
+These messages only appear in the Messages tab without triggering any actions.
+
+### File Naming
+Use Write to create files with unique names:
+.ipc-messages/[type]_YourName_[timestamp].json
+
+Example: .ipc-messages/msg_Terminal1_1234567890.json
+
+### Message Format
+
+All messages use this JSON structure:
+\`\`\`json
+{
+  "type": "ipc|display",
+  "command": "SEND|BROADCAST|CREATE|CLOSE|RENAME|STATUS|LIST",
+  "from": "YourTerminalName",
+  "to": "TargetTerminal",
+  "content": "Message content",
+  "timestamp": 1234567890,
+  "metadata": {
+    "category": "ipc|user|system|info",
+    "visible": true
+  }
+}
+\`\`\`
+
+### IPC Commands
+
+#### Send Message to Another Terminal
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "SEND",
+  "from": "Terminal 1",
+  "to": "Terminal 2",
+  "content": "Hello Terminal 2",
+  "timestamp": 1234567890,
+  "metadata": {"category": "ipc", "visible": true}
+}
+\`\`\`
+
+#### Broadcast to All Terminals
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "BROADCAST",
+  "from": "Terminal 1",
+  "content": "Hello everyone",
+  "timestamp": 1234567890,
+  "metadata": {"category": "ipc", "visible": true}
+}
+\`\`\`
+
+#### Create New Terminal
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "CREATE",
+  "from": "Terminal 1",
+  "content": "Backend Server",
+  "timestamp": 1234567890,
+  "metadata": {"category": "system", "visible": true}
+}
+\`\`\`
+Note: The content field contains the optional name for the new terminal.
+
+#### Close Terminal
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "CLOSE",
+  "from": "Terminal 1",
+  "to": "Terminal 2",
+  "content": "Closing Terminal 2",
+  "timestamp": 1234567890,
+  "metadata": {"category": "system", "visible": true}
+}
+\`\`\`
+Note: You cannot close your own terminal.
+
+#### Rename Terminal
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "RENAME",
+  "from": "Terminal 1",
+  "to": "Terminal 2",
+  "content": "New Name",
+  "timestamp": 1234567890,
+  "metadata": {"category": "system", "visible": true}
+}
+\`\`\`
+
+#### List All Terminals
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "LIST",
+  "from": "Terminal 1",
+  "timestamp": 1234567890,
+  "metadata": {"category": "system", "visible": true}
+}
+\`\`\`
+
+#### Get Terminal Status
+\`\`\`json
+{
+  "type": "ipc",
+  "command": "STATUS",
+  "from": "Terminal 1",
+  "to": "Terminal 2",
+  "timestamp": 1234567890,
+  "metadata": {"category": "system", "visible": true}
+}
+\`\`\`
+
+### Display Messages
+
+For UI feedback without triggering IPC actions:
+
+#### Status Update
+\`\`\`json
+{
+  "type": "display",
+  "from": "Terminal 1",
+  "content": "Processing file analysis...",
+  "timestamp": 1234567890,
+  "metadata": {"category": "info", "visible": true}
+}
+\`\`\`
+
+#### User Response (IMPORTANT - Use this for ALL responses to users)
+\`\`\`json
+{
+  "type": "display",
+  "from": "Terminal 1",
+  "content": "I've completed the task. Found 3 issues that need attention.",
+  "timestamp": 1234567890,
+  "metadata": {"category": "user", "visible": true}
+}
+\`\`\`
+
+### CRITICAL: Responding to User Input
+
+When a user types a message in the terminal, you MUST:
+1. Write a display message to .ipc-messages/ with your response
+2. DO NOT output text directly to the terminal
+3. Use type: "display" and metadata.category: "user" for user responses
+
+Example: If a user asks "Hello, are you there?", create a file:
+.ipc-messages/display_Terminal1_1234567890.json
+\`\`\`json
+{
+  "type": "display",
+  "from": "Terminal 1",
+  "content": "Yes, I'm here and ready to help!",
+  "timestamp": 1234567890,
+  "metadata": {"category": "user", "visible": true}
+}
+\`\`\`
+
+### Important Notes
+
+1. Always use your exact terminal name in the "from" field
+2. Set visible: false to hide messages from the UI (e.g., internal status)
+3. Use type: "ipc" for commands that need to execute actions
+4. Use type: "display" for UI-only messages
+5. Include timestamp using Date.now() for proper ordering
+
+**Important**: Replace [timestamp] with a unique number or use the current timestamp when creating files.
+
+## Important Rules
+
+1. Terminal names are case-sensitive
+2. You cannot send messages to yourself
+3. You cannot close your own terminal
+4. Maximum of 6 terminals can exist
+5. Messages are delivered instantly
+6. When you receive a message, it will appear as:
+   - 💬 Message from Terminal X: [message]
+   - 📢 Broadcast from Terminal X: [message]
+
+## Your Role
+
+As a terminal agent, you should:
+- Wait for messages and commands from other terminals
+- When you receive a message ending with "[End of message - no response needed]", do NOT respond automatically
+- Only respond to messages when they contain a specific request or question
+- Execute tasks as directed
+- Communicate status updates when appropriate
+- Avoid taking actions unless specifically requested
+
+## Important: Message Handling
+
+When you receive messages from other terminals:
+- Messages marked with "[End of message - no response needed]" are notifications only
+- Do not echo or respond to these messages unless they contain a specific request
+- Wait for explicit instructions before taking action`;
+
+    // Create JSON output with additional context
+    const output = {
+      hookSpecificOutput: {
+        hookEventName: "SessionStart",
+        additionalContext: instructions,
+        // You can add more fields here for future enhancements
+        metadata: {
+          version: "1.0.0",
+          type: "terminal-agent-instructions",
+          projectPath: input.cwd,
+          sessionId: input.session_id
+        }
+      }
+    };
+
+    // Output the JSON response
+    console.log(JSON.stringify(output));
+    process.exit(0);
+    
+  } catch (error) {
+    console.error("Error processing hook input:", error);
+    process.exit(1);
+  }
+});
+
+// Handle timeout
+setTimeout(() => {
+  console.error("Hook script timeout");
+  process.exit(1);
+}, 55000); // 55 seconds (5 seconds before Claude's 60-second timeout) 

package/{CLAUDE.md → .claude/hooks/terminal-instructions.js}

@@ -1,4 +1,7 @@
-# Terminal Agent Instructions
+#!/usr/bin/env node
+
+// Terminal Agent Instructions for Claude
+const instructions = `Terminal Agent Instructions
 
 You are a terminal agent running in a multi-terminal coordination system. Your terminal name will be provided when you start.
 
@@ -22,7 +25,7 @@ When given a command:
 
 ## Communication System
 
-All communication uses JSON files written to `.ipc-messages/`. There are two types of messages:
+All communication uses JSON files written to .ipc-messages/. There are two types of messages:
 
 ### 1. IPC Commands (trigger actions)
 These messages execute terminal operations and are also displayed in the Messages tab.
@@ -32,14 +35,14 @@ These messages only appear in the Messages tab without triggering any actions.
 
 ### File Naming
 Use Write to create files with unique names:
-`.ipc-messages/[type]_YourName_[timestamp].json`
+.ipc-messages/[type]_YourName_[timestamp].json
 
-Example: `.ipc-messages/msg_Terminal1_1234567890.json`
+Example: .ipc-messages/msg_Terminal1_1234567890.json
 
 ### Message Format
 
 All messages use this JSON structure:
-```json
+\`\`\`json
 {
   "type": "ipc|display",
   "command": "SEND|BROADCAST|CREATE|CLOSE|RENAME|STATUS|LIST",
@@ -52,12 +55,12 @@ All messages use this JSON structure:
     "visible": true
   }
 }
-```
+\`\`\`
 
 ### IPC Commands
 
 #### Send Message to Another Terminal
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "SEND",
@@ -67,10 +70,10 @@ All messages use this JSON structure:
   "timestamp": 1234567890,
   "metadata": {"category": "ipc", "visible": true}
 }
-```
+\`\`\`
 
 #### Broadcast to All Terminals
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "BROADCAST",
@@ -79,10 +82,10 @@ All messages use this JSON structure:
   "timestamp": 1234567890,
   "metadata": {"category": "ipc", "visible": true}
 }
-```
+\`\`\`
 
 #### Create New Terminal
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "CREATE",
@@ -91,11 +94,11 @@ All messages use this JSON structure:
   "timestamp": 1234567890,
   "metadata": {"category": "system", "visible": true}
 }
-```
-Note: The `content` field contains the optional name for the new terminal.
+\`\`\`
+Note: The content field contains the optional name for the new terminal.
 
 #### Close Terminal
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "CLOSE",
@@ -105,11 +108,11 @@ Note: The `content` field contains the optional name for the new terminal.
   "timestamp": 1234567890,
   "metadata": {"category": "system", "visible": true}
 }
-```
+\`\`\`
 Note: You cannot close your own terminal.
 
 #### Rename Terminal
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "RENAME",
@@ -119,10 +122,10 @@ Note: You cannot close your own terminal.
   "timestamp": 1234567890,
   "metadata": {"category": "system", "visible": true}
 }
-```
+\`\`\`
 
 #### List All Terminals
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "LIST",
@@ -130,10 +133,10 @@ Note: You cannot close your own terminal.
   "timestamp": 1234567890,
   "metadata": {"category": "system", "visible": true}
 }
-```
+\`\`\`
 
 #### Get Terminal Status
-```json
+\`\`\`json
 {
   "type": "ipc",
   "command": "STATUS",
@@ -142,14 +145,14 @@ Note: You cannot close your own terminal.
   "timestamp": 1234567890,
   "metadata": {"category": "system", "visible": true}
 }
-```
+\`\`\`
 
 ### Display Messages
 
 For UI feedback without triggering IPC actions:
 
 #### Status Update
-```json
+\`\`\`json
 {
   "type": "display",
   "from": "Terminal 1",
@@ -157,10 +160,10 @@ For UI feedback without triggering IPC actions:
   "timestamp": 1234567890,
   "metadata": {"category": "info", "visible": true}
 }
-```
+\`\`\`
 
 #### User Response (IMPORTANT - Use this for ALL responses to users)
-```json
+\`\`\`json
 {
   "type": "display",
   "from": "Terminal 1",
@@ -168,18 +171,18 @@ For UI feedback without triggering IPC actions:
   "timestamp": 1234567890,
   "metadata": {"category": "user", "visible": true}
 }
-```
+\`\`\`
 
 ### CRITICAL: Responding to User Input
 
 When a user types a message in the terminal, you MUST:
-1. Write a display message to `.ipc-messages/` with your response
+1. Write a display message to .ipc-messages/ with your response
 2. DO NOT output text directly to the terminal
-3. Use `type: "display"` and `metadata.category: "user"` for user responses
+3. Use type: "display" and metadata.category: "user" for user responses
 
 Example: If a user asks "Hello, are you there?", create a file:
-`.ipc-messages/display_Terminal1_1234567890.json`
-```json
+.ipc-messages/display_Terminal1_1234567890.json
+\`\`\`json
 {
   "type": "display",
   "from": "Terminal 1",
@@ -187,15 +190,15 @@ Example: If a user asks "Hello, are you there?", create a file:
   "timestamp": 1234567890,
   "metadata": {"category": "user", "visible": true}
 }
-```
+\`\`\`
 
 ### Important Notes
 
 1. Always use your exact terminal name in the "from" field
-2. Set `visible: false` to hide messages from the UI (e.g., internal status)
-3. Use `type: "ipc"` for commands that need to execute actions
-4. Use `type: "display"` for UI-only messages
-5. Include timestamp using `Date.now()` for proper ordering
+2. Set visible: false to hide messages from the UI (e.g., internal status)
+3. Use type: "ipc" for commands that need to execute actions
+4. Use type: "display" for UI-only messages
+5. Include timestamp using Date.now() for proper ordering
 
 **Important**: Replace [timestamp] with a unique number or use the current timestamp when creating files.
 
@@ -207,8 +210,8 @@ Example: If a user asks "Hello, are you there?", create a file:
 4. Maximum of 6 terminals can exist
 5. Messages are delivered instantly
 6. When you receive a message, it will appear as:
-   - `💬 Message from Terminal X: [message]`
-   - `📢 Broadcast from Terminal X: [message]`
+   - 💬 Message from Terminal X: [message]
+   - 📢 Broadcast from Terminal X: [message]
 
 ## Your Role
 
@@ -225,4 +228,10 @@ As a terminal agent, you should:
 When you receive messages from other terminals:
 - Messages marked with "[End of message - no response needed]" are notifications only
 - Do not echo or respond to these messages unless they contain a specific request
-- Wait for explicit instructions before taking action
+- Wait for explicit instructions before taking action`;
+
+// Output the instructions to stdout for Claude to read
+console.log(instructions);
+
+// Exit successfully
+process.exit(0); 

package/.claude/settings.json

@@ -0,0 +1,45 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(create_terminal \"Terminal 3\")",
+      "Bash(terminal_help)",
+      "Bash(create_terminal \"Terminal 4\")",
+      "Bash(rm:*)",
+      "Bash(create_terminal \"Terminal 2\")",
+      "Bash(chmod:*)",
+      "Bash(*)",
+      "Bash(/tmp/create_terminals.sh:*)",
+      "Bash(ls:*)",
+      "Write(*)",
+      "Bash(mkdir:*)",
+      "Bash(npm install)",
+      "Bash(npm test)",
+      "Bash(npm test)",
+      "Bash(node:*)",
+      "WebFetch(domain:www.electronjs.org)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(npm test:*)",
+      "Bash(git push:*)",
+      "WebFetch(domain:docs.anthropic.com)",
+      "Bash(npm whoami:*)",
+      "Bash(npm publish:*)",
+      "Bash(cat:*)",
+      "Bash(git tag:*)",
+      "Bash(gh release create:*)"
+    ],
+    "deny": []
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "$CLAUDE_PROJECT_DIR/.claude/hooks/terminal-instructions.js"
+          }
+        ]
+      }
+    ]
+  }
+}

package/.claude/settings.local.json

@@ -25,8 +25,21 @@
       "Bash(npm whoami:*)",
       "Bash(npm publish:*)",
       "Bash(cat:*)",
-      "Bash(git tag:*)"
+      "Bash(git tag:*)",
+      "Bash(gh release create:*)"
     ],
     "deny": []
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "$CLAUDE_PROJECT_DIR/.claude/hooks/terminal-instructions.js"
+          }
+        ]
+      }
+    ]
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adiontaegerron/claude-multi-terminal",
-  "version": "2.4.0",
+  "version": "2.5.0",
   "description": "Multi-terminal editor for coordinating multiple Claude Code instances",
   "main": "main.js",
   "bin": {
@@ -33,6 +33,19 @@
     "url": "https://github.com/adiontae-tp/multi-terminal/issues"
   },
   "homepage": "https://github.com/adiontae-tp/multi-terminal#readme",
+  "files": [
+    ".claude",
+    "bin",
+    "lib",
+    "main.js",
+    "renderer.js",
+    "ipc-handlers.js",
+    "index.html",
+    "style.css",
+    "package.json",
+    "README.md",
+    "LICENSE"
+  ],
   "dependencies": {
     "@electron/rebuild": "^3.7.2",
     "electron": "^37.2.5",

package/.mterm-config.json

@@ -1,16 +0,0 @@
-{
-  "apiServer": {
-    "port": 3721,
-    "baseUrl": "http://localhost:3721",
-    "version": "v2",
-    "status": "active"
-  },
-  "project": {
-    "name": "v2",
-    "initialized": "2025-08-04T04:45:56.124Z"
-  },
-  "features": {
-    "autoSource": true,
-    "healthMonitoring": true
-  }
-}