What it does
6 features
Pi · Terminal coding agent
Product and access
Pi is an open-source toolkit from Earendil with a command-line coding agent. The former repository badlogic/pi-mono redirects to earendil-works/pi.
Core features
6 features from provider sources · checked on 5 November 2026. Availability and limits are directly below.
Extensions and packages
TypeScript extensions add tools, commands, events and interface parts. Packages can be shared via npm or Git.
Source 1Four modes
Interactive terminal interface, print or JSON output, RPC over standard streams and an SDK for embedding.
Source 1Tree-structured sessions
Sessions are stored as a tree, so you can jump to earlier points and continue from there.
Source 4Many model providers
Pi connects through a subscription, an API key or a local model; /model switches the model.
Source 2Control your context
AGENTS.md, automatic compaction, skills and prompt templates determine what the model sees.
Source 1MCP and Codemode
According to the website, MCP is built in, and Codemode lets agents compose tool calls in JavaScript.
Source 1
Usable AI models
Open choice
Pi supports about 40 providers with API keys and sign-in through subscriptions, such as the ZAI Coding Plan or Kimi For Coding. OpenRouter and other gateways give you further models. You add your own endpoints in models.json, which according to the docs covers most Ollama, LM Studio and vLLM setups.
Model families named
- Anthropic (Claude)
- OpenAI (GPT)
- Google (Gemini)
- Mistral
- xAI (Grok)
- Z.ai (GLM)
- Moonshot (Kimi)
- Other models can be connected freely
- Model choice
- You choose
- Your own API key
- Yes
- Router or custom endpoint
- Yes
- Local models
- Yes
The rating covers the generally available main access. Documented · Sources accessed on
Does it fit my task?
2 practical tasks · 5 requirements and limits
A good fit if …
- you work in the terminal and want to adapt the agent with your own extensions
- you want to choose freely between model providers, a subscription, an API key or a local model
- you want to build the agent into your own workflows through print, RPC or SDK access
Less suitable if …
- you expect a built-in sandbox or approval before every tool call
- you need sub-agents and plan mode without additional packages
- you need central team and admin management
Editorial assessment based on provider documentation. Not a product test.
Practical tasks
Editorial examples based on documented features. No product tests performed.
Code change with your own rules
- Your input
- A repository with AGENTS.md and a limited change.
- Possible result
- The agent edits files and runs commands with your permissions.
- What to check
- Check the diff and test results, ideally working in a container.
Embed the agent in your own tools
- Your input
- A script that calls Pi in print or RPC mode.
- Possible result
- Machine-readable output for the next step.
- What to check
- Cover permissions, model costs and failure cases in the script.
Set up Pi for your terminal workflow.
Your possible prompt
Read the project rules. Investigate [error], propose a small change, and run the relevant checks. Show me the diff and any remaining uncertainties.
Adjust the task, data and permissions.
Requirements and limits
Requirement
Model access required
You need access to a model through a supported provider: a subscription, an API key or a local model.
Source 2Limitation
No built-in sandbox
Pi runs with the permissions of the account that started it. The security page explicitly notes the lack of a built-in sandbox and assigns isolation to containers or virtual machines.
Source 3Limitation
No approval per tool call
Pi does not ask before every tool call. Approvals can be added through extensions.
Source 3Limitation
Sub-agents and plan mode not built in
Pi leaves these out on purpose. You build them yourself or install a package.
Source 1Not yet confirmed
Team and admin features
The reviewed pages describe no central administration for teams.
Source 3
Can I use it?
Availability still unclear
Europe & regional availability
Website, security and settings pages reviewed. They name no country release or data regions.
Reviewed scope: Local software; model providers separately
Reviewed on:
Availability still unclear
Europe: no provider statement
Pi runs locally on your machine. The reviewed pages say nothing about Europe. Check model providers and their data regions separately. Anonymous install reporting is on by default and can be turned off.
Region, reason and source
Region covered: EU/EEA, United Kingdom and Switzerland
Documented reason: The reviewed sources name no country release for this.
Accounts & permissions
Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.
Configuration covered: Local coding agent with your own model access
Sources reviewed:
Show all 3 points
Documented
Account used
After /login, Pi stores model provider access in auth.json, as an API key or OAuth token.
EvidenceOpen in reviewed sources
Admin approval
The reviewed pages name no approval or restriction by an organisation’s administrators.
EvidenceDocumented
Data access & team sharing
Pi acts with the permissions of the account that started it and does not ask before every tool call. You achieve isolation through containers, virtual machines or sandboxes.
Evidence
Memory and conversation continuity
2 of 6 criteria documented
Sessions are stored locally and can be resumed; the pages document no memory across sessions.
Local session files of the coding agent
Sources accessed:
Documentation by criterion
StorageDocumented
Storage and scope
Sessions are stored by default under ~/.pi/agent/sessions/, grouped by working directory. The location can be changed.
SelectionPartly documented
Selection and timing
Sessions are saved automatically unless --no-session is used. No selection mechanism for lasting memories is described.
Edit & deletePartly documented
Inspect, edit and delete
The session picker can search, rename and delete. The file format is documented.
Access boundariesPartly documented
Agent and channel boundaries
Sessions are grouped by working directory. The reviewed pages describe no boundaries between agents or channels.
RetrievalPartly documented
Retrieval
Resume with --continue, --resume and /resume. No content search across earlier sessions for automatic retrieval is described.
New conversationsDocumented
Session reset and compaction
/new starts afresh. Compaction is on by default and controlled through settings.
Cost and effort
1 plan · Prices as of 5 November 2026
Prices and included usage
Pricing checked
Pi is available under the MIT licence; the reviewed pages name no price for the tool. Costs of model access depend on the chosen provider.
| Plan | Price | Included |
|---|---|---|
| Pi | No software fee stated | Coding agent with your own model access. |
- Terms for the optional Radius service were not reviewed.
Setup
Install by script or npm, then connect a model provider with /login.
Operation & oversight
Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.
Deployment covered: Local operation in the terminal
Sources reviewed:
Editorial assessment
You are responsible for isolation and control yourself, as Pi works with your permissions and without asking per tool call. Plan for containers or your own approvals.
Show all 6 points
Documented
Files and working state
Sessions persist by default under ~/.pi/agent/sessions/, grouped by working directory.
EvidenceDocumented with conditions
Sign-ins
Access depends on the provider: an API key or OAuth through /login, stored in auth.json. How long access lasts is up to the provider; the reviewed pages name no time limits.
EvidenceDocumented
Starting further runs
You start Pi interactively or from scripts in print, JSON or RPC mode. The reviewed pages describe no built-in schedules.
EvidenceDocumented
Human intervention
Pi does not ask before every tool call. If you want approvals, add them through extensions.
EvidenceDocumented with conditions
Detecting errors
For transient failures, Pi retries automatically, by default up to three times. The setting can be changed. The reviewed pages do not say how other failures become visible.
EvidenceDocumented
Resuming after failures
You continue interrupted work in the saved session with --continue, --resume or /resume.
Evidence
Evidence and open questions
8 sources · 2 open points
Open points
The reviewed sources contain no reliable information on these points. A gap says nothing about the product.
Europe: Availability still unclear
Requirements and limits: not yet confirmed
Sources and evidence
Official website, documentation and repository reviewed. Feature descriptions come from the provider; example tasks are editorial. Hands-on tests are still pending.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
Provider
Earendil Inc. and contributors maintain Pi as an open-source project under the MIT licence.
- Operator
- Earendil Inc.
- Organization
- Provider
- Website
- pi.dev
- Repository
- earendil-works/pi
- GitHub stars
- 120.243 · Reviewed
- License
- MIT
Changes to this profile 1
The open-source terminal coding agent with extensions, many model providers and tree-structured sessions.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.