• Sources: primary, discussion
  • Summary: The useful distinction in the post is between the harness, which is trusted and holds the model APIs, and the execution environment, which runs bash under sandboxing. Codemode lets the model script tool calls on the harness side, in Pi's case inside QuickJS on a WASM runtime with no network, no filesystem, no timers and limited RAM. That buys three things bash cannot: structured access to larger tool output without pushing it through context, concurrency and basic workflows expressed directly, and state stashed into the transcript for later calls to read back.
  • Why it matters: Ronacher names the failure modes, including Codemode inside an MCP server that already does Codemode, which forces double JSON escaping and prevents the inner code from calling outer tools, and his concrete asks of MCP servers are structured content via outputSchema, consistent result shapes across batch sizes, large binary data support, and composable tool search across servers.