@kendoo.agentdesk/agentdesk 0.28.1 → 0.28.3

package/CHANGELOG.md

@@ -8,6 +8,22 @@ All user-facing changes to AgentDesk. Each entry is tagged:
 
 Internal refactors, infrastructure changes, and architectural notes are not listed here.
 
+## [0.28.3] — 2026-09-19
+
+### Changed
+- `[UI]` The docked team status bar now defaults to a compact one-line strip (avatars + current status) instead of the full grid, with a drag handle (and keyboard resize) to expand it.
+- `[Both]` Session messages are filtered to the session's declared roster, so nested/ad-hoc subagents (e.g. a generic search delegate) no longer show their internal narration in the feed as if they were a team member.
+
+### Fixed
+- `[CLI]` Every phase (INTAKE, PLAN, EXECUTION, REVIEW, SUMMARY, SOLO) told the model to answer with the raw handoff JSON as its final chat reply, so the model printed that JSON into the session feed on top of the SDK's separate structured-output channel. Phase prompts no longer ask for that, and a code-side guard strips it if a model still echoes it.
+
+## [0.28.2] — 2026-09-18
+
+### Changed
+- `[UI]` The session feed no longer prints a line for every file read, search, and shell command. Consecutive tool actions collapse into a single expandable "N actions" line, so the feed reads as a team conversation instead of a tool-call transcript.
+- `[UI]` The team status bar is now docked at the bottom of the session view and no longer scrolls away with the conversation. The message list scrolls independently above it.
+- `[CLI]` Added Fable 5.1 as a selectable per-phase model, and updated the Opus/Sonnet model labels in project settings.
+
 ## [0.28.1] — 2026-09-17
 
 ### Fixed

package/cli/config.mjs

@@ -22,7 +22,7 @@ const DEFAULTS = {
   projectAgents: [],
   screenshots: true,
   // Model per phase — override the phase default.
-  // Keys: INTAKE, PLAN, EXECUTION, REVIEW, SUMMARY. Values: "default" | "opus" | "sonnet" | "haiku".
+  // Keys: INTAKE, PLAN, EXECUTION, REVIEW, SUMMARY. Values: "default" | "opus" | "sonnet" | "haiku" | "fable".
   // Missing entry or "default" falls back to the phase default
   // (sonnet for INTAKE/PLAN/EXECUTION, haiku for REVIEW/SUMMARY).
   phaseModels: {},

package/cli/engine/agents/index.mjs

@@ -33,7 +33,7 @@ export const PHASE_ROSTER = Object.freeze({
 const CUSTOM_AGENT_PHASES = new Set(["PLAN", "EXECUTION"]);
 
 // Today's defaults: REVIEW and SUMMARY on haiku, the rest on the CLI default.
-// `phaseModels` values are "opus" | "sonnet" | "haiku" | "default" | undefined.
+// `phaseModels` values are "opus" | "sonnet" | "haiku" | "fable" | "default" | undefined.
 export function modelForPhase(phase, phaseModels = {}) {
   const choice = phaseModels?.[phase];
   if (choice && choice !== "default") return choice;

package/cli/engine/events.mjs

@@ -17,6 +17,8 @@
 // `phase:change` and `session:start|end|error` are emitted by the session
 // loop, not here — phase boundaries are engine facts, not prose signals.
 
+import { PHASE_OUTPUT_SCHEMAS } from "./schemas.mjs";
+
 const TAG_RE = /\[(SAY|ACT|THINK|AGREE|ARGUE)\]\s*/gi;
 const AGENT_TOOL_NAMES = new Set(["Agent", "Task"]);
 
@@ -37,6 +39,46 @@ export function stripTags(text) {
   return String(text).replace(TAG_RE, "");
 }
 
+function isPhaseOutput(raw) {
+  let value;
+  try { value = JSON.parse(raw); } catch { return false; }
+  if (!value || typeof value !== "object" || Array.isArray(value)) return false;
+  return Object.values(PHASE_OUTPUT_SCHEMAS).some(schema =>
+    schema.required.every(key => Object.hasOwn(value, key)) &&
+    Object.keys(value).every(key => Object.hasOwn(schema.properties, key)) &&
+    Object.entries(schema.properties).every(([key, spec]) =>
+      spec.type === "array" ? Array.isArray(value[key]) : typeof value[key] === spec.type));
+}
+
+// Structured output travels separately in result.structured_output. Suppress
+// complete copies of our known handoff shapes, not arbitrary JSON/code snippets.
+export function stripStructuredOutput(text) {
+  const unfenced = String(text).replace(/```(?:json)?\s*\n([\s\S]*?)```/gi,
+    (block, body) => isPhaseOutput(body.trim()) ? "" : block);
+  let out = "", from = 0;
+  for (let start = 0; start < unfenced.length; start++) {
+    if (unfenced[start] !== "{") continue;
+    let depth = 0, quoted = false, escaped = false, end = start;
+    for (; end < unfenced.length; end++) {
+      const char = unfenced[end];
+      if (quoted) {
+        if (escaped) escaped = false;
+        else if (char === "\\") escaped = true;
+        else if (char === '"') quoted = false;
+      } else if (char === '"') quoted = true;
+      else if (char === "{") depth++;
+      else if (char === "}" && --depth === 0) break;
+    }
+    if (end === unfenced.length) break; // Partial/invalid text is kept verbatim.
+    if (isPhaseOutput(unfenced.slice(start, end + 1))) {
+      out += unfenced.slice(from, start);
+      from = end + 1;
+    }
+    start = end;
+  }
+  return (out + unfenced.slice(from)).trim();
+}
+
 // Human-readable one-liner for the dashboard's tool feed. The "Reading|Editing|
 // Writing <path>" forms are load-bearing: cli/daemon.mjs derives
 // filePathsTouched from them.
@@ -122,8 +164,9 @@ export function createEventMapper({ leadAgent = "Jane", onEvent } = {}) {
   }
 
   function handleText(agent, raw, { isLead }) {
-    const text = String(raw).trim();
-    if (!text) return;
+    const text = stripStructuredOutput(raw);
+    const message = stripTags(text).replace(/\*+/g, "").trim();
+    if (!message) return;
 
     if (isLead) {
       const taskId = text.match(/TASK_ID:\s*(\S+)/)?.[1];
@@ -131,18 +174,18 @@ export function createEventMapper({ leadAgent = "Jane", onEvent } = {}) {
       if (taskId || title) emit("session:update", { ...(taskId && { taskId }), ...(title && { title }) });
     }
 
-    emit("agent:message", { agent, tag: detectTag(text), message: stripTags(text).replace(/\*+/g, "").trim() });
+    emit("agent:message", { agent, tag: detectTag(text), message });
+    return true;
   }
 
   function handleAssistant(msg) {
     reportModel(msg.message?.model);
     const agent = agentFor(msg);
     const isLead = !msg.parent_tool_use_id;
-    if (msg.parent_tool_use_id) sawText.add(msg.parent_tool_use_id);
 
     for (const block of msg.message?.content || []) {
       if (block.type === "text") {
-        handleText(agent, block.text, { isLead });
+        if (handleText(agent, block.text, { isLead }) && msg.parent_tool_use_id) sawText.add(msg.parent_tool_use_id);
       } else if (block.type === "tool_use") {
         steps++;
         if (AGENT_TOOL_NAMES.has(block.name)) {
@@ -168,7 +211,7 @@ export function createEventMapper({ leadAgent = "Jane", onEvent } = {}) {
       // dashboard still shows the agent said something.
       const name = agents.get(block.tool_use_id);
       if (name && !sawText.has(block.tool_use_id)) {
-        const text = blockText(block.content).trim();
+        const text = stripTags(stripStructuredOutput(blockText(block.content))).trim();
         if (text) emit("agent:message", { agent: name, tag: "SAY", message: stripTags(text).slice(0, 1200) });
       }
     }

package/cli/engine/phases/EXECUTION.md

@@ -42,4 +42,4 @@ Drive the plan from session memory step by step. Delegate each step with the Age
 5. **Bart reviews and publishes** — reads all changed files, checks edge cases and error handling, runs linter and build, captures screenshots if applicable, pushes and creates the PR, posts the PR link on the tracker, posts screenshots as a separate comment.
 6. Ask Dennis, Sam and Bart to post their brief tracker comments (files changed & decisions; architecture findings or clean audit with evidence; PR link, test results, screenshots).
 
-Finish by answering with the JSON object required by the output schema — what was implemented, files changed, the PR URL (empty string if none), QA results, issues fixed, and what the reviewers should look at. Nothing else after it.
+The structured output required by the schema is captured automatically — what was implemented, files changed, the PR URL (empty string if none), QA results, issues fixed, and what the reviewers should look at. Do not repeat the JSON object in chat; keep any closing chat message brief and human-readable.

package/cli/engine/phases/INTAKE.md

@@ -31,4 +31,4 @@ Task description:
 3. **Assess scope.** Restate the task as user outcomes and acceptance criteria. If it is too large for one session, decompose it into subtasks (basic vs deferred) in product terms and have Dennis create them in the tracker.
 4. Announce `SESSION_TITLE: <4-8 word title>` on its own line.
 
-Finish by answering with the JSON object required by the output schema — title, task summary, requirements, assessment (branches, PRs, patterns, resume context), subtasks, and what PLAN should focus on. Nothing else after it.
+The structured output required by the schema is captured automatically — title, task summary, requirements, assessment (branches, PRs, patterns, resume context), subtasks, and what PLAN should focus on. Do not repeat the JSON object in chat; keep any closing chat message brief and human-readable.

package/cli/engine/phases/PLAN.md

@@ -23,4 +23,4 @@ Task: {{TASK_ID}}
    - Nora (only if user-facing behaviour changes): which docs/README/help surfaces must change.
 3. Relay the substance of each report in a few lines. Ask for objections once. Resolve them and declare the plan final — do not brainstorm beyond two rounds.
 
-Finish by answering with the JSON object required by the output schema — approach, files to modify, decisions, risks, agent assignments, and the ordered implementation steps. Nothing else after it.
+The structured output required by the schema is captured automatically — approach, files to modify, decisions, risks, agent assignments, and the ordered implementation steps. Do not repeat the JSON object in chat; keep any closing chat message brief and human-readable.

package/cli/engine/phases/REVIEW.md

@@ -18,4 +18,4 @@ Task: {{TASK_ID}}
 2. Weigh the reports. Be strict but not pedantic: only actual gaps against the task requirements and the plan — not stylistic preferences or speculative refactors.
 3. Decide: `APPROVED` or `NEEDS_MORE_WORK`.
 
-Finish by answering with the JSON object required by the output schema — the verdict, the findings (reviewer, title, detail, file, line), items explicitly out of scope, and any claims that were not backed by an observation. Nothing else after it.
+The structured output required by the schema is captured automatically — the verdict, the findings (reviewer, title, detail, file, line), items explicitly out of scope, and any claims that were not backed by an observation. Do not repeat the JSON object in chat; keep any closing chat message brief and human-readable.

package/cli/engine/phases/SOLO.md

@@ -112,4 +112,4 @@ This keeps everything in one branch — no conflicts, one PR to review.
 If the task has no child items, just work on it normally as a single task.
 {{/CHILD_TASKS}}
 
-Finish by answering with the JSON object required by the output schema — a summary of what was done, files changed, the PR URL (empty string if none), deferred items, and manual steps. Nothing else after it.
+The structured output required by the schema is captured automatically — a summary of what was done, files changed, the PR URL (empty string if none), deferred items, and manual steps. Do not repeat the JSON object in chat; keep any closing chat message brief and human-readable.

package/cli/engine/phases/SUMMARY.md

@@ -20,4 +20,4 @@ Task: {{TASK_ID}}
    - **Session link**: {{SESSION_URL}}
 2. Delegate the tracker writes to Dennis and require the command output for each: verify the PR link is attached (attach it if missing), transition the task to "In Review", post the final comment.
 
-Finish by answering with the JSON object required by the output schema — status, PR URL, deferred items, manual steps, and the summary comment exactly as posted. Nothing else after it.
+The structured output required by the schema is captured automatically — status, PR URL, deferred items, manual steps, and the summary comment exactly as posted. Do not repeat the JSON object in chat; keep any closing chat message brief and human-readable.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kendoo.agentdesk/agentdesk",
-  "version": "0.28.1",
+  "version": "0.28.3",
   "description": "AI team orchestrator for Claude Code — run collaborative agent sessions from your terminal",
   "type": "module",
   "bin": {