error-handling

To surface structured tool errors to an LLM, wrap tool calls in try-catch blocks and throw typed errors. The framework translates these into clean, readable messages, providing actionable feedback for tool result interpretation.

Handling ENOENT errors involves converting them into user-facing context. The framework transforms common file or subprocess errors into helpful, actionable prompts, ensuring failures are reported with clear guidance for resolution.

Propagating AbortError involves throwing the typed error during tool execution. The framework catches it to signal a clean cancellation, preventing raw stack traces from surfacing to the LLM or user interface.

Yes, typed error propagation works with shell errors. You can throw typed ShellError objects from tools, and the formatError function translates them into clean LLM messages, maintaining structured error context.

Raw stack traces appear because typed errors are not being propagated or formatted correctly. By enforcing typed error propagation and using formatError, the system ensures failures are reported with context instead of raw traces.