groove-dev 0.27.2 → 0.27.3

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## v0.27.3 — Planner sees ready-to-resume teammates (2026-04-12)
+
+Fixes a Mode 1 / Mode 2 detection bug where a planner spawned duplicate agents instead of routing work to existing teammates.
+
+**The bug**
+When a team is created with empty prompts (the "spawn the team first, then assign tasks" pattern), the builders complete in a few seconds (no task to do → return). Their status flips to `completed`. Later, when the planner spawns and looks at its intro context, the team section only listed `running`/`starting` agents — so the planner saw "you are the only agent on this project right now" and went Mode 1, spawning duplicates instead of routing to the existing ready-to-resume team.
+
+Not a regression from v0.27.x — this has been brittle for any empty-prompt team flow. Surfaced now.
+
+**Fix**
+- Introducer's team section now includes **recent completed teammates** alongside active ones, scoped to the same `teamId` with a 1-hour freshness window. Shown as "ready to resume" with an explicit note: *"Teammates marked 'ready' are part of your team. They finished their last task and will resume their session when assigned new work. If you're a planner, route new tasks to them by role — do NOT spawn duplicates."*
+- Planner role prompt (`process.js`) updated: Mode 2 detection now references the intro context's Team section directly, not just `AGENTS_REGISTRY.md`. Explicitly instructs: *"Teammates listed as 'ready to resume' are REAL agents. They WILL pick up new work when routed. NEVER spawn a new agent of a role that already exists."*
+
+**What this means for you**
+The flow that felt perfect — spawn the team, then iterate with the planner task-by-task — now works regardless of whether the builders are actively running or resting between tasks.
+
 ## v0.27.2 — Drop velocity trigger (2026-04-12)
 
 Following up on v0.27.1: the role-multiplier fix addressed the planner but left the same false-positive class live for any agent doing heavy exploration on a large codebase. Dropping velocity-based rotation entirely rather than papering over it further.

package/node_modules/@groove-dev/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/cli",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "GROOVE CLI \u2014 manage AI coding agents from your terminal",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/node_modules/@groove-dev/daemon/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/daemon",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "GROOVE daemon — agent orchestration engine",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/node_modules/@groove-dev/daemon/src/introducer.js

@@ -16,10 +16,30 @@ export class Introducer {
   generateContext(newAgent, options = {}) {
     const { taskNegotiation } = options;
     const agents = this.daemon.registry.getAll();
-    // Only include ACTIVE agents — not completed/killed ones from previous sessions
-    // Completed agents' work is captured in the journalist's project map, not here
-    const others = agents.filter((a) => a.id !== newAgent.id &&
-      (a.status === 'running' || a.status === 'starting'));
+
+    // Team awareness must include completed teammates, not just running ones.
+    // Agents that finished an empty-prompt standup (common pattern: spawn the
+    // team upfront, then direct them task-by-task) sit in `completed` status
+    // until resumed. Hiding them from the new agent's context makes planners
+    // falsely conclude "I'm alone" and spawn duplicate roles.
+    //
+    // Scope to the same team so one team's agents don't leak into another's
+    // context. Completed teammates get a 1-hour freshness cutoff so truly
+    // stale ones don't clutter the intro.
+    const COMPLETED_WINDOW_MS = 60 * 60 * 1000;
+    const sameTeam = (a) =>
+      a.id !== newAgent.id &&
+      (!newAgent.teamId || a.teamId === newAgent.teamId);
+    const activeOthers = agents.filter((a) =>
+      sameTeam(a) && (a.status === 'running' || a.status === 'starting')
+    );
+    const recentCompleted = agents.filter((a) => {
+      if (!sameTeam(a)) return false;
+      if (a.status !== 'completed') return false;
+      const ts = a.lastActivity ? new Date(a.lastActivity).getTime() : 0;
+      return Date.now() - ts < COMPLETED_WINDOW_MS;
+    });
+    const others = [...activeOthers, ...recentCompleted];
 
     const lines = [
       `# GROOVE Agent Context`,
@@ -42,8 +62,17 @@ export class Introducer {
     if (others.length === 0) {
       lines.push('You are the only agent on this project right now.');
     } else {
-      lines.push(`## Team (${others.length} other agent${others.length > 1 ? 's' : ''})`);
+      const activeCount = activeOthers.length;
+      const readyCount = recentCompleted.length;
+      const parts = [];
+      if (activeCount > 0) parts.push(`${activeCount} active`);
+      if (readyCount > 0) parts.push(`${readyCount} ready to resume`);
+      lines.push(`## Team (${others.length} teammate${others.length > 1 ? 's' : ''} — ${parts.join(', ')})`);
       lines.push('');
+      if (readyCount > 0) {
+        lines.push(`**Teammates marked "ready" are part of your team.** They finished their last task and will resume their session when assigned new work. If you're a planner, route new tasks to them by role — do NOT spawn duplicates.`);
+        lines.push('');
+      }
 
       // Collect all files created by teammates for the project files section
       const allTeamFiles = [];
@@ -51,7 +80,8 @@ export class Introducer {
       for (const other of others) {
         const scope = other.scope?.length > 0 ? other.scope.join(', ') : 'unrestricted';
         const dir = other.workingDir ? ` — dir: ${other.workingDir}` : '';
-        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${other.status}`);
+        const statusLabel = other.status === 'completed' ? 'ready to resume' : other.status;
+        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${statusLabel}`);
 
         // Get files this agent created/modified
         const files = this.daemon.journalist?.getAgentFiles(other) || [];

package/node_modules/@groove-dev/daemon/src/process.js

@@ -196,8 +196,10 @@ Do NOT re-explore the entire codebase. You already know it from team creation.
 Just read the specific files related to the bug/feature, decide which existing agent should handle it, and write the routing config. This should be FAST — under 5 tool calls.
 
 HOW TO DETECT WHICH MODE:
-- Read AGENTS_REGISTRY.md. If it lists agents with roles matching your team (frontend, backend, fullstack), you are in MODE 2.
-- If no agents exist or only a planner exists, you are in MODE 1.
+- Check the Team section of YOUR intro context (above this prompt). If it lists any teammates — active OR ready-to-resume — you are in MODE 2.
+- If no teammates exist or only a planner exists, you are in MODE 1.
+- Teammates listed as "ready to resume" are REAL agents on your team. They finished their last task and await new instructions. They WILL pick up new work when you route it to them via recommended-team.json. Do NOT treat them as absent.
+- NEVER spawn a new agent of a role that already exists in your team. A second backend when a backend already exists is always a bug.
 
 After completing your plan, you MUST write .groove/recommended-team.json — EVERY TIME, no exceptions.
 

package/node_modules/@groove-dev/gui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/gui",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "GROOVE GUI — visual agent control plane",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "groove-dev",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "Open-source agent orchestration layer — the AI company OS. Local model agent engine (GGUF/Ollama/llama-server), HuggingFace model browser, MCP integrations (Slack, Gmail, Stripe, 15+), agent scheduling (cron), business roles (CMO, CFO, EA). GUI dashboard, multi-agent coordination, zero cold-start, infinite sessions. Works with Claude Code, Codex, Gemini CLI, Ollama, any local model.",
   "license": "FSL-1.1-Apache-2.0",
   "author": "Groove Dev <hello@groovedev.ai> (https://groovedev.ai)",

package/packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/cli",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "GROOVE CLI \u2014 manage AI coding agents from your terminal",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/packages/daemon/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/daemon",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "GROOVE daemon — agent orchestration engine",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/packages/daemon/src/introducer.js

@@ -16,10 +16,30 @@ export class Introducer {
   generateContext(newAgent, options = {}) {
     const { taskNegotiation } = options;
     const agents = this.daemon.registry.getAll();
-    // Only include ACTIVE agents — not completed/killed ones from previous sessions
-    // Completed agents' work is captured in the journalist's project map, not here
-    const others = agents.filter((a) => a.id !== newAgent.id &&
-      (a.status === 'running' || a.status === 'starting'));
+
+    // Team awareness must include completed teammates, not just running ones.
+    // Agents that finished an empty-prompt standup (common pattern: spawn the
+    // team upfront, then direct them task-by-task) sit in `completed` status
+    // until resumed. Hiding them from the new agent's context makes planners
+    // falsely conclude "I'm alone" and spawn duplicate roles.
+    //
+    // Scope to the same team so one team's agents don't leak into another's
+    // context. Completed teammates get a 1-hour freshness cutoff so truly
+    // stale ones don't clutter the intro.
+    const COMPLETED_WINDOW_MS = 60 * 60 * 1000;
+    const sameTeam = (a) =>
+      a.id !== newAgent.id &&
+      (!newAgent.teamId || a.teamId === newAgent.teamId);
+    const activeOthers = agents.filter((a) =>
+      sameTeam(a) && (a.status === 'running' || a.status === 'starting')
+    );
+    const recentCompleted = agents.filter((a) => {
+      if (!sameTeam(a)) return false;
+      if (a.status !== 'completed') return false;
+      const ts = a.lastActivity ? new Date(a.lastActivity).getTime() : 0;
+      return Date.now() - ts < COMPLETED_WINDOW_MS;
+    });
+    const others = [...activeOthers, ...recentCompleted];
 
     const lines = [
       `# GROOVE Agent Context`,
@@ -42,8 +62,17 @@ export class Introducer {
     if (others.length === 0) {
       lines.push('You are the only agent on this project right now.');
     } else {
-      lines.push(`## Team (${others.length} other agent${others.length > 1 ? 's' : ''})`);
+      const activeCount = activeOthers.length;
+      const readyCount = recentCompleted.length;
+      const parts = [];
+      if (activeCount > 0) parts.push(`${activeCount} active`);
+      if (readyCount > 0) parts.push(`${readyCount} ready to resume`);
+      lines.push(`## Team (${others.length} teammate${others.length > 1 ? 's' : ''} — ${parts.join(', ')})`);
       lines.push('');
+      if (readyCount > 0) {
+        lines.push(`**Teammates marked "ready" are part of your team.** They finished their last task and will resume their session when assigned new work. If you're a planner, route new tasks to them by role — do NOT spawn duplicates.`);
+        lines.push('');
+      }
 
       // Collect all files created by teammates for the project files section
       const allTeamFiles = [];
@@ -51,7 +80,8 @@ export class Introducer {
       for (const other of others) {
         const scope = other.scope?.length > 0 ? other.scope.join(', ') : 'unrestricted';
         const dir = other.workingDir ? ` — dir: ${other.workingDir}` : '';
-        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${other.status}`);
+        const statusLabel = other.status === 'completed' ? 'ready to resume' : other.status;
+        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${statusLabel}`);
 
         // Get files this agent created/modified
         const files = this.daemon.journalist?.getAgentFiles(other) || [];

package/packages/daemon/src/process.js

@@ -196,8 +196,10 @@ Do NOT re-explore the entire codebase. You already know it from team creation.
 Just read the specific files related to the bug/feature, decide which existing agent should handle it, and write the routing config. This should be FAST — under 5 tool calls.
 
 HOW TO DETECT WHICH MODE:
-- Read AGENTS_REGISTRY.md. If it lists agents with roles matching your team (frontend, backend, fullstack), you are in MODE 2.
-- If no agents exist or only a planner exists, you are in MODE 1.
+- Check the Team section of YOUR intro context (above this prompt). If it lists any teammates — active OR ready-to-resume — you are in MODE 2.
+- If no teammates exist or only a planner exists, you are in MODE 1.
+- Teammates listed as "ready to resume" are REAL agents on your team. They finished their last task and await new instructions. They WILL pick up new work when you route it to them via recommended-team.json. Do NOT treat them as absent.
+- NEVER spawn a new agent of a role that already exists in your team. A second backend when a backend already exists is always a bug.
 
 After completing your plan, you MUST write .groove/recommended-team.json — EVERY TIME, no exceptions.
 

package/packages/gui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/gui",
-  "version": "0.27.2",
+  "version": "0.27.3",
   "description": "GROOVE GUI — visual agent control plane",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",