🎯 What Pi Is
Pi is a minimal, lightweight coding agent harness — it wraps an LLM (OpenAI, OpenCode, or open-source providers) and ships core tools like read, write, edit, and bash. What it doesn't ship: subagents and MCP. Both are add-ons via community extensions. 0:00
🤝 Subagents Extension
ZazenCodes picks tintinweb/py-subagents (~1k stars) — his choice because it gives Claude Code-style subagents, which he's used to. 2:26
tintinweb/py-subagents, and \agents becomes an available setting to manage them. Subagents are how he keeps his main context clean — the detailed "nitty-gritty" work happens inside subagents, and only the summary comes back.🔬 Demo: Parallel Exploration
The hands-on test: explore an open-source repo's source folder using subagents. 3:07
explore source 10), 10 agents spin up in parallel, and you watch checkmarks appear as each finishes.⚙️ Configuring Subagent Models
The surprising default — and how to override it. 7:32
explore agent type defaults to Claude Haiku and falls back to "inherit" — not the parent model. ZazenCodes expected it to inherit Terra (his main), but it was running Haiku 4.5 through OpenCode.\agents → agent types → "eject personal settings" → open the config file → change the model override. He set OpenAI/GPT-5.6-Luna (the cheap small model) as his exploration model, keeping the expensive Terra as main. "Using Luna as a cheap exploration model is exactly what I'd want."🔌 MCP Extension
Installing MCP support via the Pim-MCP adapter (~1k stars, on Pi's official site). 11:44
/mcp → scaffold mcp.json in the project (or configure globally) → add a streamable HTTP server URL. Each MCP server can be project-local or global, and the \mcp view gives observability — he saw 55 tools exposed by one server, individually enable/disable-able.🚀 Demo: Building Apps with MCP
The end-to-end test: build a working app through the MCP server (Floot — today's sponsor). 14:51
floot_get_guides, floot_list_files, floot_apply_patch, floot_edit_file — and Pi called them through the adapter.catilian-floot.app — a Postgres-backed feedback form (name, message, mood) with a pixel character, published with one click. The database showed the submitted entries ("Jim — steady vibe").💡 Key Takeaways
- Pi is minimal by design — subagents and MCP aren't missing, they're community extensions.
- Subagents keep the main context clean — 300k tokens of exploration stayed in 10 subagents; main context held ~20k (10%).
- The explore agent defaults to Haiku, not the parent model — eject settings to override it with a cheap model (GPT-5.6 Luna).
- Right-size the swarm — 4 subagents often beat 10; there's spin-up overhead.
- MCP comes via the Pim-MCP adapter —
/mcpscaffolds config, project-local or global, with per-tool enable/disable. - Auth is manual in Pi — an OAuth copy-paste dance that Claude/Codex smooth over.
- Skills vs MCP — for simple logic (random numbers), a skill is cleaner; MCP is for real external tool servers (databases, deployment).