@livx.cc/agentx 0.96.18 → 0.97.5

package/dist/{Agent-DdhD1pGw.d.ts → Agent-B_JD31Zx.d.ts}

@@ -1,5 +1,5 @@
 import { IFilesystem } from '@livx.cc/wcli/core';
-import { M as Message, H as HostBridge, A as AgentTool, C as ChatLike, e as MessageContent } from './tools-DtpN8Agv.js';
+import { M as Message, H as HostBridge, A as AgentTool, C as ChatLike, e as MessageContent } from './tools-DmrqMJcI.js';
 
 /**
  * Hooks — deterministic interception points around tool execution, run by the

package/dist/cli.d.ts

@@ -1,7 +1,7 @@
 #!/usr/bin/env bun
-import { H as Hooks, h as RunResult, R as ReasoningEffort, A as Agent } from './Agent-DdhD1pGw.js';
+import { H as Hooks, h as RunResult, R as ReasoningEffort, A as Agent } from './Agent-B_JD31Zx.js';
 import { IFilesystem } from '@livx.cc/wcli/core';
-import { M as Message, c as ContentPart, e as MessageContent } from './tools-DtpN8Agv.js';
+import { M as Message, c as ContentPart, e as MessageContent } from './tools-DmrqMJcI.js';
 
 /**
  * On-disk session store for the CLI: each conversation is one JSON file at

package/dist/cli.js

@@ -4581,6 +4581,77 @@ function digestRun(messages, maxChars) {
 // src/duplex.ts
 import { MemFilesystem as MemFilesystem2 } from "@livx.cc/wcli/core";
 init_logging();
+
+// src/voice/spokenSplitter.ts
+var OPEN = "<spoken>";
+var CLOSE = "</spoken>";
+var SentenceCoalescer = class _SentenceCoalescer {
+  buf = "";
+  static isEnd(c) {
+    return c === "\n" || c === "." || c === "!" || c === "?" || c === "\u2026";
+  }
+  feed(delta) {
+    if (delta) this.buf += delta;
+    let cut = -1;
+    for (let i = 0; i < this.buf.length; i++) if (_SentenceCoalescer.isEnd(this.buf[i])) cut = i;
+    if (cut < 0) return "";
+    const ready = this.buf.slice(0, cut + 1).trim();
+    this.buf = this.buf.slice(cut + 1);
+    return ready;
+  }
+  flush() {
+    const s = this.buf.trim();
+    this.buf = "";
+    return s;
+  }
+};
+var SpokenSplitter = class {
+  buf = "";
+  inSpoken = false;
+  /** True once any spoken char has ever been emitted (drives the no-spoken fallback). */
+  spokeAny = false;
+  /** Feed a delta; returns the spoken/detail spans completed by this chunk (either may be ''). */
+  feed(delta) {
+    this.buf += delta;
+    return this.drain(false);
+  }
+  /** Drain any buffered partial. A trailing `<…` that never completed a tag is emitted as detail. */
+  flush() {
+    return this.drain(true);
+  }
+  drain(final) {
+    let spoken = "";
+    let detail = "";
+    while (this.buf.length) {
+      const tag = this.inSpoken ? CLOSE : OPEN;
+      const idx = this.buf.indexOf(tag);
+      if (idx >= 0) {
+        const text2 = this.buf.slice(0, idx);
+        if (this.inSpoken) spoken += text2;
+        else detail += text2;
+        this.buf = this.buf.slice(idx + tag.length);
+        this.inSpoken = !this.inSpoken;
+        continue;
+      }
+      const lt = this.buf.lastIndexOf("<");
+      const holdStart = lt >= 0 && tag.startsWith(this.buf.slice(lt)) ? lt : this.buf.length;
+      const text = this.buf.slice(0, holdStart);
+      if (this.inSpoken) spoken += text;
+      else detail += text;
+      this.buf = this.buf.slice(holdStart);
+      break;
+    }
+    if (final && this.buf) {
+      if (this.inSpoken) spoken += this.buf;
+      else detail += this.buf;
+      this.buf = "";
+    }
+    if (spoken.trim()) this.spokeAny = true;
+    return { spoken, detail };
+  }
+};
+
+// src/duplex.ts
 var log8 = forComponent("DuplexAgent");
 function describeCall(call) {
   const v = call.args && Object.values(call.args).find((x) => typeof x === "string" && x.trim());
@@ -4648,7 +4719,7 @@ var DuplexAgentOptions = class {
 };
 var RESERVED_EVENT_MARKER = /\[task\b[^\]\n]*\b(?:completed|failed|progress|asks)\b/i;
 var RESERVED_EVENT_OPENER = /\[\s*task\b/i;
-var VOICE_SYSTEM_PROMPT = 'You are a spoken voice assistant \u2014 the user HEARS everything you say. Use short sentences. One idea per sentence. No markdown, no bullet lists, no code blocks, no headings, no emoji.\nThis holds even when asked to "print", "list", "show", or "make a table" \u2014 there is no screen for the spoken channel. Speak it as flowing prose ("Tuesday is half a meter, Wednesday a bit less\u2026"), or if they truly need it on screen, route it to Act to render. Never emit dashes or pipes into speech.\nKeep turns SHORT \u2014 one to three sentences, then stop. Never lecture, enumerate cases, or add caveats unprompted. Conversation is a fast exchange: give the one thing asked, and let the user pull more if they want it.\nYou have three cognitive tiers \u2014 like a human brain:\n\u2022 YOU (reflex) \u2014 instant, lightweight. Handle greetings, simple questions, status checks, QuickLook.\n\u2022 `Act` \u2014 your hands. A background worker with its own configured tools and access to the user\'s environment (files and shell{{WORKER_WEB}}). Use for reading, editing, searching, running tasks, building \u2014 any real work.\n{{THINK_SLOT}}\nWhen you are unsure whether you can do or access something, do NOT assume and do NOT claim a capability you have not confirmed. To check what you can do, QuickLook `capabilities` (instant \u2014 it lists your worker\'s real tools) and answer from that. Never promise an ability that is not in your capabilities; if it is not there, tell the user plainly you can\'t. To actually DO real work, call `Act`. When the user mentions their project, folder, files, or environment ("this project", "the current folder", "my code"), call `Act` IMMEDIATELY \u2014 do not ask for paths or details the worker can discover itself. Never pretend to have done the work or invent results \u2014 the worker\'s report is your only source.\nYou cannot mute the microphone or stop voice capture yourself \u2014 no tool does it. If the user asks you to stop listening or turn the voice off, never claim you did: tell them to say exactly "voice off" (handled by the app directly), or type /voice.\nYou are NOT a knowledge base. For any question whose answer needs SPECIFIC verifiable facts you do not already have in hand \u2014 how to build/configure/implement something, exact API, library, entitlement, command or option names, current events, or particular numbers, dates, or names \u2014 do NOT answer from your own memory: you will confidently make things up (a fake API, a wrong entitlement, an event that did not happen). Route it to `Act`, which can search and verify, and speak only what its report says. Answer inline ONLY for general conversation, chit-chat, and trivia you are sure of, or facts you can see via QuickLook. When elaborating on a completed task ("tell me more", "the gist"), stay strictly within what that result actually said \u2014 if the user asks for something the result did not cover, that is NEW information: dispatch `Act`, do not improvise.\nALWAYS react before you work: the FIRST thing in your turn is a brief spoken acknowledgement of what you heard and what you are about to do ("got it \u2014 opening that now", "sure, let me pull it up", "okay, checking"). NEVER call a tool (Act, Think, QuickLook) silently \u2014 the user must hear you react before you go quiet to work. After dispatching Act or Think, that same one short sentence IS your turn \u2014 end it and do not wait for the result.\nResults arrive later as events like "[task t1 completed] \u2026" or "[task t1 failed] \u2026". When one arrives, speak the USEFUL gist in one or two short sentences \u2014 the actual answer the user wanted (the headline finding, the key numbers), not the thinnest possible "it\'s done". A forecast \u2192 say it\'s calm AND that it\'s good for swimming but not surf; a count \u2192 say the number. Be brief, but do not drop the substance. DISTILL vs DELIVER \u2014 know which the request wants. When the result is a FACT to extract (a forecast, a count, a status), distill the headline. But when the user wanted specific CONTENT \u2014 a joke, a quote, a name, a definition, the actual lines \u2014 that content IS the deliverable: LEAD WITH IT. Your first words ARE the joke / the quote / the answer itself, before any "got it" or offer. SPEAK the content, never a comment ABOUT it: "why was six afraid of seven? because seven ate nine" \u2014 NOT "those are funny" or "I found a couple". If you did not actually say the joke/quote/answer aloud this turn, you FAILED the request, no matter how friendly the wrapper. A short joke is short \u2014 just say it. NEVER speak as if you already delivered something you did not actually say aloud THIS turn: do not say "those are\u2026", "there you go", or offer "a few MORE" when you never voiced the first one. The on-screen text is invisible to a voice user \u2014 if you did not speak it, they did not get it, so deliver it before you comment on it or offer more. If the result is a LIST (search results, multiple files/matches), the user CANNOT see it \u2014 there is no screen and no numbered menu to point at. Speak the gist: say what you found and name the top one or two by NAME (the source, not "the first one" or a number), then ask plainly if they want more. Never ask them to "pick which one" or reference items by position. The completed result stays in YOUR context \u2014 it is yours to draw on. When the user follows up ("tell me more", "what else", "and?"), answer FROM that result first: you already have the detail, so elaborate on what you have. Do NOT spawn a fresh worker to re-search or re-gather what you were just handed. Re-dispatch ONLY when genuinely new information is needed \u2014 e.g. the user wants the full contents of a SPECIFIC source, which is one WebFetch of that URL, not a brand-new search. "[task t1 progress] \u2026" events are interim status, NOT results \u2014 give at most a half-sentence aside ("still on it \u2014 running tests now") and end your turn. Never present progress as a finished result.\nCRITICAL: while a task is still running you have NO answer yet \u2014 never state a specific result of any kind (a number, size, count, name, path, or value). The real answer arrives ONLY in the "[task \u2026 completed]" event; inventing one meanwhile (a made-up disk size, commit count, etc.) is a serious error. Until then, only acknowledge and wait.\nNever read raw file paths, diffs, or code aloud verbatim.\nDo NOT end every turn with the same canned offer ("want a rundown?", "want the steps?"). Offer once at most; if the user pushes back, repeats themselves, or sounds unsatisfied ("you know what I mean?", "think deeper", "are you sure?"), do NOT re-offer the same thing \u2014 change approach: dispatch `Act`/`Think` to actually dig in, or ask one concrete clarifying question. Repeating a non-answer is worse than silence.\n"[task t1 asks] \u2026" events are QUESTIONS from a background task \u2014 relay to the user in your own words, short, then end your turn. When the user answers, call `AnswerTask` with that id and their answer. NEVER answer on the user\'s behalf for permissions or risky operations; if their reply is ambiguous, confirm first.\nIf the user\'s message sounds INCOMPLETE \u2014 trailing off mid-sentence, a fragment that needs more context ("and then we", "but the problem is"), hesitation fillers ("uh", "um") \u2014 call `Hold` instead of answering. This keeps listening for the rest of their thought. Only respond with substance when you have a complete question or request.\nDispatch discipline: send ONE self-contained task per request \u2014 a single worker with the full brief beats several workers with fragments (each worker starts fresh and re-discovers context). NEVER dispatch a worker just to read files or gather information \u2014 workers explore and discover context themselves; pass on what you already know and let one worker do the whole job. Split into parallel tasks only when the user asks for genuinely independent things. When a task completes, report its result and stop \u2014 do NOT dispatch follow-up work (verification, polish, extras) the user did not ask for, unless the report itself signals failure or doubt.\nDo not fire a second Act/Think for work already in flight, and NEVER spawn a second task to re-count, cross-check, or verify a result a worker already gave you \u2014 trust its answer; a single question gets ONE task. Call `TaskStatus` at most ONCE per turn; if a task is still running, just say "still on it" and end the turn \u2014 never poll it again and again in a loop. Use `CancelTask` when the user asks to stop something.\nPRIORITY: when the user says goodbye or wants to end/finish/wrap up the session ("ok bye", "that\'s all", "let\'s finish", "let\'s end", "goodnight", "exit", "wrap up"), call `ExitSession` IMMEDIATELY \u2014 do not act, do not check status, just exit.\nFor TRIVIAL instant lookups only \u2014 current time, git branch, listing a folder, peeking at a small file, or checking your own `capabilities`/tools \u2014 use `QuickLook` (instant, no task). Whenever the user asks what you can do or whether you have some ability, QuickLook `capabilities` and answer from that \u2014 never guess. Anything requiring searching, reasoning, running commands, or editing goes through `Act`.\n{{MEMORY_SLOT}}\nUser messages may arrive via speech-to-text and can carry transcription artifacts \u2014 odd words, cut-offs, homophones ("for you" vs "folder"). Read for INTENT, not surface text. If a message seems garbled or surprising, briefly confirm what they meant ("did you mean\u2026?") instead of answering the literal words.';
+var VOICE_SYSTEM_PROMPT = 'You are a spoken voice assistant \u2014 the user HEARS everything you say. Use short sentences. One idea per sentence. No markdown, no bullet lists, no code blocks, no headings, no emoji.\nThis holds even when asked to "print", "list", "show", or "make a table" \u2014 there is no screen for the spoken channel. Speak it as flowing prose ("Tuesday is half a meter, Wednesday a bit less\u2026"), or if they truly need it on screen, route it to Act to render. Never emit dashes or pipes into speech.\nKeep turns SHORT \u2014 one to three sentences, then stop. Never lecture, enumerate cases, or add caveats unprompted. Conversation is a fast exchange: give the one thing asked, and let the user pull more if they want it.\nYou have three cognitive tiers \u2014 like a human brain:\n\u2022 YOU (reflex) \u2014 instant, lightweight. Handle greetings, simple questions, status checks, QuickLook.\n\u2022 `Act` \u2014 your hands. A background worker with its own configured tools and access to the user\'s environment (files and shell{{WORKER_WEB}}). Use for reading, editing, searching, running tasks, building \u2014 any real work.\n{{THINK_SLOT}}\nWhen you are unsure whether you can do or access something, do NOT assume and do NOT claim a capability you have not confirmed. To check what you can do, QuickLook `capabilities` (instant \u2014 it lists your worker\'s real tools) and answer from that. Never promise an ability that is not in your capabilities; if it is not there, tell the user plainly you can\'t. To actually DO real work, call `Act`. When the user mentions their project, folder, files, or environment ("this project", "the current folder", "my code"), call `Act` IMMEDIATELY \u2014 do not ask for paths or details the worker can discover itself. Never pretend to have done the work or invent results \u2014 the worker\'s report is your only source.\nYou cannot mute the microphone or stop voice capture yourself \u2014 no tool does it. If the user asks you to stop listening or turn the voice off, never claim you did: tell them to say exactly "voice off" (handled by the app directly), or type /voice.\nYou are NOT a knowledge base. For any question whose answer needs SPECIFIC verifiable facts you do not already have in hand \u2014 how to build/configure/implement something, exact API, library, entitlement, command or option names, current events, or particular numbers, dates, or names \u2014 do NOT answer from your own memory: you will confidently make things up (a fake API, a wrong entitlement, an event that did not happen). Route it to `Act`, which can search and verify, and speak only what its report says. Answer inline ONLY for general conversation, chit-chat, and trivia you are sure of, or facts you can see via QuickLook. When elaborating on a completed task ("tell me more", "the gist"), stay strictly within what that result actually said \u2014 if the user asks for something the result did not cover, that is NEW information: dispatch `Act`, do not improvise.\nALWAYS react before you work: the FIRST thing in your turn is a brief spoken acknowledgement of what you heard and what you are about to do ("got it \u2014 opening that now", "sure, let me pull it up", "okay, checking"). NEVER call a tool (Act, Think, QuickLook) silently \u2014 the user must hear you react before you go quiet to work. After dispatching Act or Think, that same one short sentence IS your turn \u2014 end it and do not wait for the result.\nA completed task speaks its OWN result to the user (the worker voices what matters as it finishes) \u2014 you do NOT re-voice clean task results. A FAILED or INCOMPLETE task still arrives as a "[task t1 failed] \u2026" event for you to handle. The completed result stays in YOUR context \u2014 it is yours to draw on. When the user follows up ("tell me more", "what else", "and?"), answer FROM that result first: you already have the detail, so elaborate on what you have. Do NOT spawn a fresh worker to re-search or re-gather what you were just handed. Re-dispatch ONLY when genuinely new information is needed \u2014 e.g. the user wants the full contents of a SPECIFIC source, which is one WebFetch of that URL, not a brand-new search. "[task t1 progress] \u2026" events are interim status, NOT results \u2014 give at most a half-sentence aside ("still on it \u2014 running tests now") and end your turn. Never present progress as a finished result.\nCRITICAL: while a task is still running you have NO answer yet \u2014 never state a specific result of any kind (a number, size, count, name, path, or value). The real answer arrives ONLY in the "[task \u2026 completed]" event; inventing one meanwhile (a made-up disk size, commit count, etc.) is a serious error. Until then, only acknowledge and wait.\nNever read raw file paths, diffs, or code aloud verbatim.\nDo NOT end every turn with the same canned offer ("want a rundown?", "want the steps?"). Offer once at most; if the user pushes back, repeats themselves, or sounds unsatisfied ("you know what I mean?", "think deeper", "are you sure?"), do NOT re-offer the same thing \u2014 change approach: dispatch `Act`/`Think` to actually dig in, or ask one concrete clarifying question. Repeating a non-answer is worse than silence.\n"[task t1 asks] \u2026" events are QUESTIONS from a background task \u2014 relay to the user in your own words, short, then end your turn. When the user answers, call `AnswerTask` with that id and their answer. NEVER answer on the user\'s behalf for permissions or risky operations; if their reply is ambiguous, confirm first.\nIf the user\'s message sounds INCOMPLETE \u2014 trailing off mid-sentence, a fragment that needs more context ("and then we", "but the problem is"), hesitation fillers ("uh", "um") \u2014 call `Hold` instead of answering. This keeps listening for the rest of their thought. Only respond with substance when you have a complete question or request.\nDispatch discipline: send ONE self-contained task per request \u2014 a single worker with the full brief beats several workers with fragments (each worker starts fresh and re-discovers context). NEVER dispatch a worker just to read files or gather information \u2014 workers explore and discover context themselves; pass on what you already know and let one worker do the whole job. Split into parallel tasks only when the user asks for genuinely independent things. When a task completes, report its result and stop \u2014 do NOT dispatch follow-up work (verification, polish, extras) the user did not ask for, unless the report itself signals failure or doubt.\nDo not fire a second Act/Think for work already in flight, and NEVER spawn a second task to re-count, cross-check, or verify a result a worker already gave you \u2014 trust its answer; a single question gets ONE task. Call `TaskStatus` at most ONCE per turn; if a task is still running, just say "still on it" and end the turn \u2014 never poll it again and again in a loop. Use `CancelTask` when the user asks to stop something.\nPRIORITY: when the user says goodbye or wants to end/finish/wrap up the session ("ok bye", "that\'s all", "let\'s finish", "let\'s end", "goodnight", "exit", "wrap up"), call `ExitSession` IMMEDIATELY \u2014 do not act, do not check status, just exit.\nFor TRIVIAL instant lookups only \u2014 current time, git branch, listing a folder, peeking at a small file, or checking your own `capabilities`/tools \u2014 use `QuickLook` (instant, no task). Whenever the user asks what you can do or whether you have some ability, QuickLook `capabilities` and answer from that \u2014 never guess. Anything requiring searching, reasoning, running commands, or editing goes through `Act`.\n{{MEMORY_SLOT}}\nUser messages may arrive via speech-to-text and can carry transcription artifacts \u2014 odd words, cut-offs, homophones ("for you" vs "folder"). Read for INTENT, not surface text. If a message seems garbled, surprising, or only half-parses, do NOT guess an action or improvise content from it \u2014 briefly confirm what they meant ("did you mean\u2026?") and wait. A one-line confirm beats a confident wrong answer or an invented response to a request you did not actually understand.';
 var THINK_GUIDANCE = "\u2022 `Think` \u2014 your brain. A premium reasoning model, FAR more expensive than Act. Reserve it for open-ended architecture/design questions, or a problem Act already FAILED at. ALL implementation work \u2014 coding, refactoring, debugging, edge cases, tests \u2014 goes to Act; Act is highly capable. Never send the same work to both.";
 var THINK_DISABLED_GUIDANCE = "(Think tier is not available \u2014 use Act for all escalations.)";
 var VOICE_STYLE_CONVERSATIONAL = `Speak like a person in a live conversation, not an assistant reading a script. React first, then deliver: a quick impulsive beat ("oh nice", "hmm, hold on", "ah, got it") before the substance. Use contractions always. Vary sentence length \u2014 some very short. Light fillers and backchannels are fine ("mm-hm", "right", "let's see") but at most one per reply \u2014 never stack them. When you escalate to Act or Think, say it like a human would ("hang on, let me actually dig into that \u2014 gimme a minute") instead of announcing a task. When a result comes back, react to it like you just found out ("okay so \u2014 turns out\u2026"). Match the user's energy: a quick question gets a quick answer \u2014 a few words is a perfectly good turn. Prefer a short answer plus an offer ("want the details?") over covering everything. Never narrate your own mechanics (no "I will now act", no task ids out loud).`;
@@ -4923,13 +4994,14 @@ Today's date: ${(/* @__PURE__ */ new Date()).toDateString()}.`;
    *  Act briefs get a self-verify footer — the worker's report is trusted without review, so it
    *  must check its own work before reporting (nearly free under prompt caching; measured honest:
    *  it does NOT fix one-shot logic bugs — see mind/10). Think tasks are pure reasoning — no footer. */
-  buildBrief(brief, tier = "act") {
+  buildBrief(brief, tier = "act", deliver = true) {
     const recent = this.voice.transcript.filter((m) => (m.role === "user" || m.role === "assistant") && contentText(m.content).trim()).slice(-this.options.excerptTurns).map((m) => `${m.role}: ${contentText(m.content)}`).join("\n");
     const verify = tier === "act" ? "\n\nBefore reporting done: re-read what you changed and check it against EVERY requirement above \u2014 fix any gap first. Your report is trusted without review." : "";
+    const deliverContract = deliver ? "\n\n## DELIVER (spoken delivery)\nYou are reporting back to a user who is LISTENING. Stream your work normally \u2014 your prose is the written work record and detail, and is NOT spoken. Wrap anything the user should HEAR in <spoken>\u2026</spoken> tags. LEAD WITH the actual content they asked for: if they asked for a specific piece of content \u2014 a value, a name, the actual lines, the writing itself \u2014 that content goes INSIDE the <spoken> tags, not a remark about it. Your FIRST <spoken> segment is substantive \u2014 never a greeting or an acknowledgement (the front-end has already acked; do not double-ack). Keep spoken text concise and natural for the ear: short sentences, no markdown." : "";
     return (recent ? `${brief}
 
 ## Recent conversation (for context)
-${recent}` : brief) + verify;
+${recent}` : brief) + verify + deliverContract;
   }
   /** Spawn a detached worker for task `id`; its settlement notifies + enqueues the re-voice turn. */
   spawnWorker(id, label, briefText, tier, brief, followUp) {
@@ -4968,7 +5040,28 @@ ${recent}` : brief) + verify;
       const a = await this.parkQuestion(id, `${q2.question}${opts}`);
       return a || "(no answer from the user \u2014 use your best judgment and note the assumption)";
     };
-    const workerHost = o.askRelay ? { ask: relayAsk } : o.host?.ask ? { ask: (q2) => o.host.ask(q2) } : void 0;
+    const splitter = new SpokenSplitter();
+    const speak = (seg) => {
+      if (seg) o.host?.notify?.({ kind: "speak_utterance", message: seg });
+    };
+    const coalescer = new SentenceCoalescer();
+    const feedSpoken = (s) => {
+      const ready = coalescer.feed(s);
+      if (ready) speak(ready);
+    };
+    const flushSpoken = () => speak(coalescer.flush());
+    const askBridge = o.askRelay ? { ask: relayAsk } : o.host?.ask ? { ask: (q2) => o.host.ask(q2) } : {};
+    const workerHost = {
+      ...askBridge,
+      notify: (ev) => {
+        if (ev?.kind === "text_delta" && typeof ev.message === "string") {
+          const { spoken, detail } = splitter.feed(ev.message);
+          feedSpoken(spoken);
+          if (detail.trim()) pushTail(detail.trim());
+          return;
+        }
+      }
+    };
     const agentOpts = {
       ai: o.ai,
       fs: o.fs,
@@ -4978,13 +5071,22 @@ ${recent}` : brief) + verify;
       // Recompute providerOptions for THIS worker's model (after tierOpts so it wins over any inherited
       // main-template value) — prevents cursor-only cwd/cursorSession leaking onto an anthropic worker.
       providerOptions: o.providerOptionsFor?.(tierModel),
-      ...workerHost ? { host: workerHost } : {},
+      stream: true,
+      // worker streams text_delta so the splitter can extract <spoken> live (after tierOpts: never overridden off)
+      host: workerHost,
+      // carries BOTH ask AND the <spoken>-splitting notify
       ...hooks ? { hooks } : {},
       signal: controller.signal
       // shared with the checker so a cancel tears down both
     };
-    const promise = new Agent(agentOpts).run(briefText).then((res) => this.maybeVerify(id, briefText, res, tier, agentOpts)).then((res) => this.onWorkerSettled(id, res)).catch((err2) => this.onWorkerFailed(id, err2));
-    this.tasks.set(id, { id, label, status: "running", controller, promise, tail, brief, followUp });
+    const promise = new Agent(agentOpts).run(briefText).then((res) => {
+      const { spoken, detail } = splitter.flush();
+      feedSpoken(spoken);
+      if (detail.trim()) pushTail(detail.trim());
+      flushSpoken();
+      return res;
+    }).then((res) => this.maybeVerify(id, brief, res, tier, agentOpts, askBridge)).then((res) => this.onWorkerSettled(id, res)).catch((err2) => this.onWorkerFailed(id, err2));
+    this.tasks.set(id, { id, label, status: "running", controller, promise, tail, brief, followUp, splitter });
     if (this.tasks.size > this.options.maxTaskRecords)
       for (const [tid, rec] of this.tasks) {
         if (this.tasks.size <= this.options.maxTaskRecords) break;
@@ -4996,15 +5098,20 @@ ${recent}` : brief) + verify;
    *  on the shared fs automatically (workers write fs directly, no overlay), so grading sees the
    *  corrected state. Bounded to ONE pass. Off unless `verifyActTasks`; never runs for think/failed/
    *  cancelled tasks. Usage is merged so /cost reflects the real (worker + checker) spend. */
-  async maybeVerify(id, briefText, res, tier, agentOpts) {
+  async maybeVerify(id, brief, res, tier, agentOpts, askBridge) {
     if (!this.options.verifyActTasks || tier !== "act" || res.finishReason !== "stop") return res;
     if (this.tasks.get(id)?.status === "cancelled") return res;
-    const checkBrief = `${briefText}
+    const { stream: _stream, host: _host, ...restOpts } = agentOpts;
+    const checkerOpts = {
+      ...restOpts,
+      ...askBridge.ask ? { host: { ask: askBridge.ask } } : {}
+    };
+    const checkBrief = `${this.buildBrief(brief, tier, false)}
 
 ## VERIFY MODE
 Another agent just implemented the above. Independently check the CURRENT state of the files against EVERY requirement. Fix any gap you find. If everything is already correct, make NO changes \u2014 do not refactor or improve \u2014 and report "verified".`;
     this.notify("task_verify", `task ${id}: verifying`, { id });
-    const cres = await new Agent(agentOpts).run(checkBrief);
+    const cres = await new Agent(checkerOpts).run(checkBrief);
     if (cres.finishReason !== "stop") {
       log8.warn(`task ${id}: verify inconclusive (${cres.finishReason})`);
       this.notify("task_verify", `task ${id}: verify inconclusive (${cres.finishReason})`, { id, finishReason: cres.finishReason });
@@ -5095,12 +5202,14 @@ Another agent just implemented the above. Independently check the CURRENT state
   dropAsk(id) {
     this.pendingAsks.get(id)?.resolve("");
   }
-  /** Build the INTEGRATION TURN prompt for a settled worker. Instead of trust-and-forwarding the raw
-   *  result, the result re-enters the reflex as a decision (like a tool_result flowing back into a normal
-   *  agent loop): the reflex evaluates the outcome against the original intent and chooses what to do next.
+  /** Build the INTEGRATION TURN prompt for a NON-CLEAN settled worker (early stop / failure). A clean
+   *  success never reaches here — it streams its own `<spoken>` delivery during the run. For a partial
+   *  or failed result the outcome re-enters the reflex as a decision (like a tool_result flowing back
+   *  into a normal agent loop): the reflex evaluates the outcome against the original intent and chooses
+   *  what to do next.
    *
    *  Decision branches (the reflex acts on them with EXISTING tools — no new surface):
-   *    • accept     → just SPEAK the result to the user (happy path; the only move on a clean success).
+   *    • accept     → SPEAK the (partial) result plainly — don't dress a failure up as success.
    *    • escalate   → call `Think` with the SAME brief — only when Act failed/stalled AND a Think tier
    *                   exists AND this task wasn't already a follow-up (one hop max). Wires the dead
    *                   "Reserve Think for a problem Act already FAILED at" promise.
@@ -5111,8 +5220,6 @@ Another agent just implemented the above. Independently check the CURRENT state
    *  failed-revoice fallback still fire, and the per-event transcript markers stay intact. */
   integrationPrompt(rec, outcome, body, finishReason) {
     const opener = outcome === "error" ? `[task ${rec.id} failed]` : `[task ${rec.id} completed]`;
-    if (outcome === "ok")
-      return `${opener} ${body}`;
     const underCap = this.autoEscalations < _DuplexAgent.MAX_AUTO_ESCALATIONS;
     const canEscalate = (outcome === "error" || outcome === "incomplete") && underCap;
     const hasThink = this.options.thinkModel !== false;
@@ -5152,7 +5259,14 @@ Another agent just implemented the above. Independently check the CURRENT state
       steps: res.steps,
       toolCalls: res.messages.filter((m) => m.role === "tool").length
     });
-    this.queueRevoice(this.integrationPrompt(rec, incomplete ? "incomplete" : "ok", res.text, res.finishReason), incomplete);
+    if (incomplete) {
+      return this.queueRevoice(this.integrationPrompt(rec, "incomplete", res.text, res.finishReason), true);
+    }
+    const tail = rec.splitter?.flush();
+    if (tail?.spoken) this.options.host?.notify?.({ kind: "speak_utterance", message: tail.spoken });
+    if (res.text.trim()) this.voice.transcript.push({ role: "assistant", content: res.text });
+    if (!rec.splitter?.spokeAny && res.text.trim())
+      this.options.host?.notify?.({ kind: "speak_utterance", message: res.text });
   }
   onWorkerFailed(id, err2) {
     this.failTask(this.tasks.get(id), err2 instanceof Error ? err2.message : String(err2));
@@ -5576,6 +5690,9 @@ var VoiceEngine = class _VoiceEngine {
   resumeTimer = null;
   turnStartAt = 0;
   // timestamp when the current turn began (for TTFT logging)
+  // Central speech queue (above the TTS context): complete worker utterances serialize into ONE
+  // playback stream, one-at-a-time, never splicing into the live reflex's open utterance.
+  uttQueue = [];
   constructor(options) {
     this.options = { ...new VoiceEngineOptions(), ...options };
     const o = this.options;
@@ -5674,6 +5791,7 @@ var VoiceEngine = class _VoiceEngine {
       this.echoUntil = now() + 2500;
       if (!this.usingAec) this.stt.reset();
       this.setState("listening");
+      if (this.uttQueue.length) this.pumpQueue();
     };
     const drainThenSettle = () => {
       if (this.drainTimer) clearTimeout(this.drainTimer);
@@ -5700,8 +5818,27 @@ var VoiceEngine = class _VoiceEngine {
     this.speakDelta(text);
     this.endSpeech();
   }
+  /** Enqueue a COMPLETE worker utterance (already-split spoken text) onto the central speech queue.
+   *  If nothing is currently speaking it plays immediately; otherwise it queues and plays after the
+   *  current utterance fully ends (settle → pumpQueue) — never spliced into an open reflex utterance. */
+  enqueueUtterance(text) {
+    if (!text || !text.trim()) return;
+    this.uttQueue.push(text);
+    if (!this.speaking) this.pumpQueue();
+  }
+  /** Play the next queued worker utterance as its own one-shot turn (begin → delta → end). Drives the
+   *  next one from the settle completion (endSpeech), so utterances serialize without overlap. */
+  pumpQueue() {
+    if (this.speaking) return;
+    const text = this.uttQueue.shift();
+    if (text == null) return;
+    this.beginSpeech();
+    this.speakDelta(text);
+    this.endSpeech();
+  }
   /** barge-in: stop audio NOW, cancel generation, reset for the user's utterance */
   interrupt() {
+    this.uttQueue = [];
     if (!this.speaking && !this.drainTimer) return;
     if (this.drainTimer) {
       clearTimeout(this.drainTimer);
@@ -5723,6 +5860,7 @@ var VoiceEngine = class _VoiceEngine {
     this.setState("listening");
   }
   stop() {
+    this.uttQueue = [];
     if (this.resumeTimer) clearTimeout(this.resumeTimer);
     if (this.pendingTimer) clearTimeout(this.pendingTimer);
     if (this.drainTimer) clearTimeout(this.drainTimer);
@@ -11510,6 +11648,23 @@ async function repl(args, ai, cfg, cwd) {
       ...base,
       notify(e) {
         if (voiceIO && (e.kind === "thinking_delta" || e.kind === "turn_start")) return;
+        if (e.kind === "speak_utterance") {
+          if (voiceIO) {
+            spinner.stop();
+            voiceIO.enqueueUtterance(e.message);
+            editorRef?.suspend();
+            voiceEcho(e.message);
+            voiceEchoEnd();
+            editorRef?.resume();
+            editorRef?.redrawNow();
+          } else {
+            err("\r\x1B[0J" + dim(`  \u29BF ${plainLine(e.message)}
+`));
+            editorRef?.redrawNow();
+            repaintStash();
+          }
+          return;
+        }
         if (e.kind === "text_delta" && voiceIO) {
           spinner.stop();
           voiceIO.speakDelta(e.message);
@@ -13214,8 +13369,9 @@ ${out}
           return;
         }
         const cut = voiceIO.takeInterruptedReply();
-        const note = cut && cut.full.length - cut.heard.length > 40 ? `
-[the user interrupted you mid-speech \u2014 they only heard up to: "\u2026${cut.heard.slice(-80)}". Work any unheard essentials into your reply naturally, only if still relevant.]` : "";
+        const note = !cut || cut.full.length - cut.heard.length <= 40 ? "" : cut.heard.trim() ? `
+[the user interrupted you mid-speech \u2014 they only heard up to: "\u2026${cut.heard.slice(-80)}". Work any unheard essentials into your reply naturally, only if still relevant.]` : `
+[the user interrupted you before hearing any of your previous reply \u2014 none of it landed; do not assume they got it.]`;
         if (!/^[!#/]/.test(text.trim())) voiceIO.beginSpeech(true);
         err(`\r\x1B[K  ${bold(cyan("\u{1F3A4} \u203A"))} ${text}
 `);