@mono-agent/agent-runtime 0.8.0 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mono-agent/agent-runtime",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "Agent runtime supporting Claude SDK/CLI, Codex, OpenCode, and Pi SDK bridges out of the box",
   "type": "module",
   "license": "GPL-3.0-only",

package/src/agent/tools/pi-bridge.js

@@ -785,6 +785,11 @@ export async function initPiMcpTools(mcpConfig, reservedNames = new Set(), {
             details: {
               server: serverName,
               tool: sourceTool.name,
+              // pi-agent-core treats a resolved execute() call as successful.
+              // Preserve the MCP protocol's explicit error bit in details so
+              // the harness after-tool hook can replace that default without
+              // throwing away the bounded content or structuredContent below.
+              ...(out?.isError === true ? { mcp_result_is_error: true } : {}),
               mcp_call_duration_ms: mcpCallDurationMs,
               result_truncated: mcpContentWasTruncated(out, { textLimit, imageInlineMaxBytes }),
               raw: compactRawMcpResult(out),

package/src/ai/providers/pi-native/turn-runner.js

@@ -191,6 +191,14 @@ export function buildTurnHarness(runState, {
     steeringMode,
     followUpMode: steeringMode,
   });
+  // MCP `CallToolResult.isError` is a successful protocol response, so pi's
+  // execute() promise resolves. The bridge records that bit in result details;
+  // this after-tool hook restores the error flag while preserving the already
+  // bounded content/details verbatim. Downstream tool_execution_end and timing
+  // events therefore report the failure accurately.
+  harness.on("tool_result", (event) => /** @type {any} */ (event?.details)?.mcp_result_is_error === true
+    ? { isError: true }
+    : undefined);
   runState.harness = harness;
 
   harness.subscribe(createStreamSubscriber(runState, { onEvent, options, toolLimits, harness }));