sscoble/pi-mono
1
0
Fork 0
mirror of https://github.com/badlogic/pi-mono.git synced 2026-11-05 23:37:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

feat(agent): let tools return error results without throwing

Browse source 
AgentToolResult.isError marks a result as failed while keeping details and structuredContent, so partial output and structured failures (such as MCP isError results) reach the UI and nested callers.
This commit is contained in:
Armin Ronacher 2026-09-27 18:00:25 +02:00
parent 4ccdc212e7
commit f2270cdb63
2 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
packages/agent/src/agent-loop.ts
View file

@ -936,7 +936,7 @@ async function executePreparedToolCall(
);
acceptingUpdates = false;
await Promise.all(updateEvents);
return { result, isError: false };
return { result, isError: result.isError === true };
} catch (error) {
acceptingUpdates = false;
await Promise.all(updateEvents);

9
packages/agent/src/types.ts
View file

@ -447,6 +447,12 @@ export interface AgentToolResult<T = JsonValue | undefined> {
structuredContent?: JsonValue;
/** Usage from the final tool execution itself, if available. Not used for main LLM context accounting. */
usage?: Usage;
/**
* Report a failure without throwing. The model sees `content` as an error result, like a thrown
* error, but `details` and `structuredContent` are kept, so the UI and programmatic callers can
* still read partial output or a structured failure (for example an MCP result with `isError`).
*/
isError?: boolean;
/**
* Hint that the agent should stop after the current tool batch.
* Early termination only happens when every finalized tool result in the batch sets this to true.
@ -511,7 +517,8 @@ export interface AgentTool<TParameters extends TSchema = TSchema, TDetails = any
*/
outputSchema?: TSchema;
/**
* Execute the tool call. Throw on failure instead of encoding errors in `content`.
* Execute the tool call. Throw on failure, or return a result with `isError: true`; do not only
* describe the failure in `content`.
* `context` is provided by the agent loop and absent when the tool is called directly.
*/
execute: (