Tiny Agent Cores Make Self-Rewriting Tools Possible

articleaiagentspiopenclawagent-toolsextensionstuimcp

Pi’s tiny-core plus stateful-extension model maps to joelclaw’s gateway and skill stack: keep the agent core small, make capabilities inspectable, writable, and disposable.

Armin Ronacher writes up Pi as the tiny coding agent sitting under OpenClaw: short system prompt, four basic tools, and an extension system that can persist state into sessions. The interesting move is restraint. Instead of stuffing the agent with every possible tool, Pi keeps the permanent surface small: Read, Write, Edit, Bash.

That minimal core is what makes the rest feel alive. Pi can write an extension, hot reload it, test it, and keep looping until the tool works. Sessions are trees, so a side quest can fix a broken tool without trashing the main thread. That’s a sharp pattern for agentic programming: the agent doesn’t just use software, it repairs and reshapes the software it uses.

The anti-MCP stance is the spicy part. Armin is not saying external tools are useless. He’s saying loading giant tool surfaces into context is often the wrong default. Use mcporter if you need MCP, but don’t make the core depend on it. For joelclaw, that points toward a clean split: tiny agent core, durable session state, local skills, extension UIs, and capabilities the agent can read and rewrite instead of mystical black-box bullshit.

Key Ideas

  • Pi is framed as a minimal coding agent with only four built-in tools: Read, Write, Edit, and Bash.
  • OpenClaw builds on Pi to connect an agent to chat-style communication channels that can run code.
  • Stateful Pi extensions let tools persist information into sessions instead of forcing everything through model-visible context.
  • Tree-shaped sessions make it possible to branch into side quests, fix tools, summarize what happened, and return to the main session.
  • Armin Ronacher argues that MCP does not belong in Pi core because large tool surfaces are hard to reload cleanly inside model context.
  • Pi TUI extensions can render terminal components like spinners, progress bars, file pickers, tables, preview panes, and dashboards.
  • The deeper pattern is software building its own working environment, not a marketplace of preinstalled tools.