antechamber 1.0.25 → 1.0.26

package/CHANGELOG.md

@@ -7,6 +7,15 @@ and this project uses [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.0.26] - 2026-10-28
+
+### Fixed
+
+- Stop showing "Opencode failed to send message" for a provider error that OmO retries on its own, such as
+  Anthropic's 400 for a `web_search` tool use with no `web_search_tool_result`, which OmO retries without web search
+  replay data. The errored reply now waits for OmO's retry decision: a retried step completes without the error and
+  v2 no longer reports `session.step.failed`. An error that is not retried still fails the message, step and run.
+
 ## [1.0.25] - 2026-10-27
 
 ### Added

package/dist/pi-event-translation.d.ts

@@ -57,6 +57,11 @@ export declare class PiEventTranslator {
     private services;
     /** Ended assistant messages whose completion waits on their tools. */
     private awaitingTools;
+    /**
+     * Errored assistant messages held open until agent_end says whether OmO retries them. OpenChamber prints a
+     * completed message's error as "failed to send message", and v2 cannot retract a `session.step.failed`.
+     */
+    private heldFailures;
     constructor(services: PiEventServices);
     /** Close dead-runtime UI state before an error or idle event can reach the client. */
     finishInterruptedRun(s: ManagedSession, error: NonNullable<OCAssistantMessage["error"]>): void;
@@ -93,6 +98,8 @@ export declare class PiEventTranslator {
     private completeSettled;
     /** Tool parts that never received a result (abort, crash) must not spin forever. */
     private finalizeDanglingTools;
+    /** Complete held errored messages: with their error when the run failed, without it when OmO retries the step. */
+    private completeHeldFailures;
     /** Complete every ended message of this session still waiting on its tools. */
     private completeAwaitingTools;
 }

package/dist/pi-event-translation.js

@@ -168,6 +168,11 @@ export class PiEventTranslator {
     services;
     /** Ended assistant messages whose completion waits on their tools. */
     awaitingTools = new WeakSet();
+    /**
+     * Errored assistant messages held open until agent_end says whether OmO retries them. OpenChamber prints a
+     * completed message's error as "failed to send message", and v2 cannot retract a `session.step.failed`.
+     */
+    heldFailures = new WeakMap();
     constructor(services) {
         this.services = services;
     }
@@ -394,8 +399,11 @@ export class PiEventTranslator {
                 this.setStatus(s, { type: "busy" });
                 return;
             case "agent_end":
-                if (ev.willRetry === true)
-                    return; // auto-retry keeps the session busy
+                if (ev.willRetry === true) {
+                    // auto-retry keeps the session busy, and the failed step it retries is not a failure to report.
+                    this.completeHeldFailures(s, false);
+                    return;
+                }
                 if (s.interruptRequested)
                     this.finishInterruptedRun(s, { name: "MessageAbortedError", data: { message: "Cancelled" } });
                 s.approvals?.finishTurn();
@@ -599,15 +607,19 @@ export class PiEventTranslator {
                     s.streaming.message.modelID = s.model.modelID;
                 }
                 applyUsage(s.streaming.message, ended.usage);
-                Object.assign(s.streaming.message, piStopReason(ended.stopReason, ended.errorMessage));
+                const stop = piStopReason(ended.stopReason, ended.errorMessage);
+                if (ended.stopReason === "error")
+                    this.heldFailures.set(s.streaming.message, stop);
+                else
+                    Object.assign(s.streaming.message, stop);
                 // OpenCode completes an assistant message only after its tools settle, and
                 // OpenChamber marks active tools under a completed message as Interrupted.
                 // pi ends a toolUse message before executing its tool calls, so defer its
                 // completion to the last tool result (applyToolResults), the next step, or
-                // the run end. Errored/aborted messages never run their tools.
+                // the run end. Errored/aborted messages never run their tools; an errored one completes at agent_end.
                 if (ended.stopReason === "toolUse" && hasActiveTools(s, s.streaming.message.id))
                     this.awaitingTools.add(s.streaming.message);
-                else
+                else if (ended.stopReason !== "error")
                     s.streaming.message.time.completed = Date.now();
                 this.services.emit(s.info.directory, { type: "message.updated", properties: { info: s.streaming.message } });
                 this.finishStreaming(s);
@@ -968,8 +980,23 @@ export class PiEventTranslator {
         s.toolByCallId.clear();
         this.completeAwaitingTools(s); // the run is over
     }
+    /** Complete held errored messages: with their error when the run failed, without it when OmO retries the step. */
+    completeHeldFailures(s, failed) {
+        const now = Date.now();
+        for (const { info } of s.messages ?? []) {
+            const stop = this.heldFailures.get(info);
+            if (stop === undefined || info.role !== "assistant")
+                continue;
+            this.heldFailures.delete(info);
+            if (failed)
+                Object.assign(info, stop);
+            info.time.completed = now;
+            this.services.emit(s.info.directory, { type: "message.updated", properties: { info } });
+        }
+    }
     /** Complete every ended message of this session still waiting on its tools. */
     completeAwaitingTools(s) {
+        this.completeHeldFailures(s, true);
         const now = Date.now();
         for (const { info } of s.messages ?? []) {
             if (!this.awaitingTools.has(info) || info.role !== "assistant")

package/extensions/omo-compat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-compat",
-  "version": "1.0.25",
+  "version": "1.0.26",
   "description": "OpenChamber extension: displays OmO tool calls the way OmO means them when OpenChamber runs on antechamber",
   "private": true,
   "type": "module",

package/extensions/omo-dag/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-graph",
-  "version": "1.0.25",
+  "version": "1.0.26",
   "description": "OpenChamber extension: live, interactive graph of the OmO sub-agents behind the current session",
   "private": true,
   "type": "module",

package/extensions/omo-work/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-work",
-  "version": "1.0.25",
+  "version": "1.0.26",
   "description": "OpenChamber 2.x Work Status section: OmO todo phases, monitors, eval cells and background work of the current session",
   "private": true,
   "type": "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber",
-  "version": "1.0.25",
+  "version": "1.0.26",
   "description": "OpenCode-compatible HTTP/SSE server that lets OpenChamber drive the pi coding agent (and OmO) over RPC",
   "type": "module",
   "license": "MIT",