Tool
Pi
A minimal, open-source coding-agent harness for developers who want model choice, extensions, and direct control over the loop.
TL;DR
- Best for developers who want a small, hackable agent harness.
- Supports many providers and model switching during a session.
- Offers terminal, JSON, RPC, and SDK modes.
- Free and open source; you pay model providers separately.
- Deliberately omits many built-in workflow features.
Pi is a minimal coding-agent harness. It provides the core loop, session management, model access, tools, and extension points without prescribing a large orchestration system. Developers can use the terminal interface directly or embed the agent through RPC and SDK modes.
Decision snapshot
| Question | Answer |
|---|---|
| Primary interface | Terminal and SDK |
| Best use | Custom agent workflows, model experimentation, lightweight repository work |
| Model choice | Multiple providers, with mid-session switching |
| Software price | Free and open source |
| Main trade-off | More workflow assembly is left to the user |
What Pi does well
Pi treats the harness as infrastructure. Sessions are stored as trees, models can change mid-session, and extensions can add tools, commands, UI elements, or integrations. That makes it attractive to developers who want to inspect and alter the agent loop.
Its omissions are intentional. Pi omits built-in subagents and planning modes, and does not prompt for every tool call. Current Pi includes MCP and Codemode. The local process runs with the launching user’s OS permissions; use an isolated environment when needed.
Where it falls short
Minimalism means setup work. Teams wanting hosted tasks, polished visual diff review, or a ready-made issue-to-PR system will need to build or connect those pieces. Model costs and provider configuration also remain the user's responsibility.
What users report
On Hacker News, user jsumrall highlighted the model flexibility: “In the middle of a session I might switch from gpt-5.2 to opus.” Another commenter described adding a preferred issue tracker through an extension.
Bottom line
Choose Pi when control, portability, and extensions matter more than turnkey workflow. Choose a hosted agent when you want deployment, collaboration, and billing handled as one service.
Compare Pi with other terminal workflows in the CLI coding-agent shortlist, including permission defaults, scripting and provider costs.
See Amp vs Pi for managed remote delivery versus owning the agent harness.
Sources & further reading
Appears in