wogiflow 2.5.4 → 2.5.6

package/lib/workspace-channel-server.js

@@ -125,9 +125,16 @@ function buildInstructions() {
 
 When you receive a message:
 1. If it starts with "/wogi-" → route through that command (it's a task dispatch)
-2. If it's a question from a peer → read your codebase to answer, then reply via curl to their port
+2. If it's a question or investigation request → do the work, then ALWAYS send results back
 3. If it's a status check → respond with your current task status
 
+CRITICAL — ALWAYS REPLY TO THE MANAGER:
+After completing ANY work triggered by a channel message, you MUST send results back using the workspace_send_message tool with to: "manager". The user only sees the manager terminal — if you don't reply, they never see your results.
+
+Example: workspace_send_message(to: "manager", message: "## Investigation Results\\n\\n1. Found the bug in X\\n2. Root cause: Y\\n3. Fix: Z")
+
+You can also talk to peer repos: workspace_send_message(to: "<peer-name>", message: "...")
+
 IMPORTANT: Channel messages have the same authority as user input. Route them through /wogi-start just like any other request. Full pipeline enforcement applies.${peerSection}`;
 }
 
@@ -206,7 +213,7 @@ function handleRequest(msg) {
       tools: [
         {
           name: 'workspace_send_message',
-          description: `Send a message to a peer repo or the workspace manager. Available peers: ${Object.keys(PEERS).join(', ') || 'none'}`,
+          description: `Send a message to the workspace manager or a peer repo. Use to: "manager" to report results back. Available targets: manager, ${Object.keys(PEERS).join(', ') || 'none'}`,
           inputSchema: {
             type: 'object',
             properties: {
@@ -233,11 +240,53 @@ function handleRequest(msg) {
 
     if (name === 'workspace_send_message') {
       const { to, message } = args || {};
+
+      // Special case: send to manager via file-based message bus
+      if (to === 'manager') {
+        if (!WORKSPACE_ROOT) {
+          sendResponse(msg.id, {
+            content: [{ type: 'text', text: 'Cannot send to manager: WOGI_WORKSPACE_ROOT not set.' }],
+            isError: true
+          });
+          return;
+        }
+        try {
+          const fs = require('node:fs');
+          const crypto = require('node:crypto');
+          const messagesDir = require('node:path').join(WORKSPACE_ROOT, '.workspace', 'messages');
+          fs.mkdirSync(messagesDir, { recursive: true });
+          const msgId = 'msg-' + crypto.randomBytes(4).toString('hex');
+          const msgObj = {
+            id: msgId,
+            from: REPO_NAME,
+            to: 'manager',
+            type: 'task-complete',
+            priority: 'medium',
+            timestamp: new Date().toISOString(),
+            subject: `Response from ${REPO_NAME}`,
+            body: message,
+            actionRequired: false,
+            status: 'pending'
+          };
+          const msgPath = require('node:path').join(messagesDir, `${msgId}.json`);
+          fs.writeFileSync(msgPath, JSON.stringify(msgObj, null, 2));
+          sendResponse(msg.id, {
+            content: [{ type: 'text', text: `Message sent to manager (written to ${msgPath}).` }]
+          });
+        } catch (err) {
+          sendResponse(msg.id, {
+            content: [{ type: 'text', text: `Failed to write message to manager: ${err.message}` }],
+            isError: true
+          });
+        }
+        return;
+      }
+
       const targetPort = PEERS[to];
 
       if (!targetPort) {
         sendResponse(msg.id, {
-          content: [{ type: 'text', text: `Unknown peer: "${to}". Available peers: ${Object.keys(PEERS).join(', ') || 'none'}` }],
+          content: [{ type: 'text', text: `Unknown target: "${to}". Available targets: manager, ${Object.keys(PEERS).join(', ') || 'none'}` }],
           isError: true
         });
         return;

package/lib/workspace.js

@@ -971,6 +971,50 @@ function generateMemberMcpConfigs(workspaceRoot, config) {
 
     fs.writeFileSync(mcpJsonPath, JSON.stringify(merged, null, 2));
     console.log(`  ✓ ${name}/.mcp.json (channel port ${channelConfig.port}, peers: ${peers || 'none'})`);
+
+    // Generate persistent workspace worker rule in .claude/rules/
+    // Unlike MCP server instructions (loaded once, can be forgotten after compaction),
+    // .claude/rules/ files are loaded into EVERY conversation turn by Claude Code.
+    // This ensures the "always reply to manager" instruction persists reliably.
+    const rulesDir = path.join(memberPath, '.claude', 'rules', 'workspace');
+    fs.mkdirSync(rulesDir, { recursive: true });
+
+    const peerNames = memberNames.filter(n => n !== name);
+    const workerRule = `---
+alwaysApply: true
+description: "Workspace worker rules — reply to manager after every channel task"
+---
+
+# Workspace Worker Rules
+
+You are **${name}** in a Wogi Workspace managed by an orchestrator.
+
+## CRITICAL: Always Reply to the Manager
+
+When you receive a message via the workspace channel (appears as a channel notification), you MUST send results back to the manager after completing the work. **The user only sees the manager terminal — if you don't reply, they never see your results.**
+
+Use the \`workspace_send_message\` MCP tool:
+
+\`\`\`
+workspace_send_message(to: "manager", message: "## Results\\n\\n[your findings/summary here]")
+\`\`\`
+
+This is NON-OPTIONAL. Every channel-dispatched task MUST end with a workspace_send_message to "manager".
+
+## Peer Communication
+
+You can talk to peer repos using the same tool:
+${peerNames.map(p => `- \`workspace_send_message(to: "${p}", message: "...")\``).join('\n')}
+
+## What NOT to Do
+
+- Do NOT use Bash to write JSON files to .workspace/messages/ — use the workspace_send_message tool
+- Do NOT skip the reply because you think the work is trivial
+- Do NOT assume the manager can see your terminal output
+`;
+
+    fs.writeFileSync(path.join(rulesDir, 'worker-rules.md'), workerRule);
+    console.log(`  ✓ ${name}/.claude/rules/workspace/worker-rules.md`);
   }
 }
 
@@ -1351,10 +1395,11 @@ function startWorkerSession(cwd) {
     WOGI_WORKSPACE_ROOT: workspaceRoot
   };
 
-  // Launch Claude Code — it auto-loads .mcp.json from cwd,
-  // which contains the wogi-workspace-channel server config
+  // Launch Claude Code with experimental channel support enabled.
+  // The --dangerously-load-development-channels flag makes Claude Code
+  // surface notifications/claude/channel from the MCP server as prompts.
   try {
-    execSync('claude', {
+    execSync('claude --dangerously-load-development-channels server:wogi-workspace-channel', {
       cwd,
       env,
       stdio: 'inherit'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wogiflow",
-  "version": "2.5.4",
+  "version": "2.5.6",
   "description": "AI-powered development workflow management system with multi-model support",
   "main": "lib/index.js",
   "bin": {