wogiflow 2.5.3 → 2.5.5

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

@@ -594,6 +594,50 @@ ${Object.entries(config.channels?.members || {}).map(([name, ch]) =>
 \`\`\`
 Then read responses from \`.workspace/messages/\` and synthesize findings.
 
+## Waiting for Worker Results (CRITICAL — Automatic Return Path)
+
+Workers **automatically write results** to \`.workspace/messages/\` when they complete a task. You do NOT need to ask them to report back — the task-completed hook writes a \`task-complete\` message automatically.
+
+**After dispatching a task, poll for results:**
+\`\`\`bash
+# List all pending messages (newest first)
+ls -t .workspace/messages/*.json 2>/dev/null | head -5
+
+# Read the latest message
+cat .workspace/messages/$(ls -t .workspace/messages/*.json 2>/dev/null | head -1) 2>/dev/null
+\`\`\`
+
+**Or read all messages from a specific worker:**
+\`\`\`bash
+# Find messages from a specific repo
+grep -l '"from": "<repo-name>"' .workspace/messages/*.json 2>/dev/null
+\`\`\`
+
+**Polling pattern after dispatch:**
+1. Dispatch task via \`curl -s -X POST http://localhost:{port} -d "..."\`
+2. Wait ~5 seconds for the worker to start processing
+3. Poll \`.workspace/messages/\` for new \`task-complete\` messages from that worker
+4. If no message after 30s, check the worker's \`ready.json\` for task status
+5. Once message arrives, read it and present the results to the user
+
+**Message format** (what workers write automatically):
+\`\`\`json
+{
+  "id": "msg-XXXXXXXX",
+  "from": "<repo-name>",
+  "to": "manager",
+  "type": "task-complete",
+  "subject": "Task completed: <title>",
+  "body": "**Task**: ...\\n**Files changed**: ...\\n**Summary**: ...",
+  "taskId": "wf-XXXXXXXX",
+  "status": "pending"
+}
+\`\`\`
+
+**After reading a result**: Present the findings to the user. If the task requires follow-up (e.g., bug investigation found the issue in the other repo), dispatch the fix to the appropriate worker.
+
+**You are the SINGLE interface for the user.** They should never need to look at worker terminals. Read the messages, synthesize, and present.
+
 ## Reading Member State (What to Read, When)
 
 | When | What to Read | Path |
@@ -1307,10 +1351,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.3",
+  "version": "2.5.5",
   "description": "AI-powered development workflow management system with multi-model support",
   "main": "lib/index.js",
   "bin": {

package/scripts/hooks/core/task-completed.js

@@ -282,6 +282,63 @@ async function handleTaskCompleted(input) {
     } catch (_err) {
       // Non-critical - registry manager may not be available
     }
+    // Write results back to workspace message bus if running as a workspace worker
+    if (result.completed && process.env.WOGI_WORKSPACE_ROOT) {
+      try {
+        const workspaceRoot = process.env.WOGI_WORKSPACE_ROOT;
+        const repoName = process.env.WOGI_REPO_NAME || path.basename(process.cwd());
+        const messagesDir = path.join(workspaceRoot, '.workspace', 'messages');
+        fs.mkdirSync(messagesDir, { recursive: true });
+
+        // Build a summary from available task data
+        const summary = [];
+        if (completedTask.title) summary.push(`**Task**: ${completedTask.title}`);
+        if (completedTask.type) summary.push(`**Type**: ${completedTask.type}`);
+        if (input.changedFiles?.length) summary.push(`**Files changed**: ${input.changedFiles.join(', ')}`);
+        if (input.summary) summary.push(`**Summary**: ${input.summary}`);
+
+        // Read the last request-log entry for richer context
+        try {
+          const logPath = path.join(PATHS.root, 'request-log.md');
+          if (fs.existsSync(logPath)) {
+            const logContent = fs.readFileSync(logPath, 'utf-8');
+            const lastEntry = logContent.split(/^### R-/m).pop();
+            if (lastEntry && lastEntry.length < 2000) {
+              summary.push(`**Log entry**:\n${lastEntry.trim()}`);
+            }
+          }
+        } catch (_err) {
+          // Non-critical
+        }
+
+        const message = {
+          id: 'msg-' + require('node:crypto').randomBytes(4).toString('hex'),
+          from: repoName,
+          to: 'manager',
+          type: 'task-complete',
+          priority: 'medium',
+          timestamp: new Date().toISOString(),
+          subject: `Task completed: ${completedTask.title || completedTask.id}`,
+          body: summary.join('\n') || `Task ${completedTask.id} completed successfully.`,
+          taskId: completedTask.id,
+          actionRequired: false,
+          status: 'pending'
+        };
+
+        const msgPath = path.join(messagesDir, `${message.id}.json`);
+        fs.writeFileSync(msgPath, JSON.stringify(message, null, 2));
+
+        if (process.env.DEBUG) {
+          console.error(`[Task Completed] Workspace message written: ${msgPath}`);
+        }
+      } catch (err) {
+        // Non-critical — workspace messaging is best-effort
+        if (process.env.DEBUG) {
+          console.error(`[Task Completed] Workspace message failed: ${err.message}`);
+        }
+      }
+    }
+
     // Check pending queue — notify user if items are waiting
     try {
       const { getPendingCount } = require('../../flow-pending');