privateer-agent 0.12.33 → 0.12.34

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "privateer-agent",
-  "version": "0.12.33",
+  "version": "0.12.34",
   "description": "Privacy-first terminal coding agent — bring your own model across 20 providers (Anthropic, OpenAI, OpenRouter, Google, local Ollama…). Safe-by-default permissions, MCP, sub-agents, workflows, and verifiable TEE inference. Built on the Pi toolkit.",
   "type": "module",
   "license": "MIT",

package/src/cli/chat.ts

@@ -329,6 +329,15 @@ async function main() {
   async function runTurn(text: string, remote: boolean, echo = true): Promise<void> {
     if (turnActive) {
       console.log(`\n${DIM}(busy — a turn is already running)${RESET}`);
+      // Say it to the DRIVER too, not just to this terminal's own console. An
+      // app-driven prompt refused here used to vanish: the app had already echoed
+      // the message into its feed and lit the thinking pill (submit() in
+      // RemoteDriveContext does both before transmitting), and the only trace of
+      // the refusal was a dim line on a terminal nobody was looking at. The driver
+      // saw their own message sit under a spinner forever. A notice does not close
+      // their turn, and must not — a turn IS running, and it is the one they are
+      // watching — but it tells them this message was not added to it.
+      if (remote) relay?.sendNotice("Not sent — this terminal is already running a turn. Wait for it to finish, or press Stop.");
       return;
     }
     turnActive = true;

package/src/engine/events.ts

@@ -36,7 +36,20 @@ export type EngineEvent =
   | { type: "retrying"; attempt: number; max: number; delayMs: number; reason: string }
   // `error` is the short user-facing message; `hint` is an optional actionable
   // next step rendered dim beneath it. Both are already secret-redacted.
-  | { type: "error"; error: string; hint?: string; retryable?: boolean };
+  | { type: "error"; error: string; hint?: string; retryable?: boolean }
+  // The turn is still running and has produced nothing for `sinceMs`. Emitted by a
+  // HOST that supervises turns (today: the desktop's turnSupervisor), never by the
+  // engine — the engine has no clock and no view of the turn as a whole.
+  //
+  // It exists because silence is ambiguous and the app cannot resolve it: a tool
+  // call emits at its start and its end and nothing in between, so a fifteen-minute
+  // build, a stalled model socket and a dead agent all look identical from the far
+  // side of the relay. This is the frame that says which. `tool`/`toolMs` name what
+  // is being waited on when something is.
+  //
+  // It is NOT turn activity: it must not reset a "silent for 4m" clock, or it would
+  // erase the very thing it was sent to report.
+  | { type: "still-working"; sinceMs: number; tool?: string; toolMs?: number };
 
 export const emptyUsage = (): UsageTotals => ({
   inputTokens: 0,

package/src/remote/relayClient.ts

@@ -373,6 +373,11 @@ function projectEvent(ev: EngineEvent): Record<string, unknown> {
       return { type: "aborted" };
     case "step-finish":
       return { type: "step-finish" };
+    // Fields, not just the tag: the default below would drop sinceMs/tool and the
+    // frame would arrive saying "something is happening" without saying what or
+    // for how long, which is the whole of its content.
+    case "still-working":
+      return { type: "still-working", sinceMs: ev.sinceMs, tool: ev.tool, toolMs: ev.toolMs };
     default:
       // text/reasoning are coalesced in sendEvent and never reach here.
       return { type: ev.type };