The pi coding agent, ported 1:1 to Rust.
A drop-in replacement for pi. It reads your ~/.pi/agent setup and runs your extensions, skills, and packages as they are, from one binary with no Node.js.
macOS
curl -fsSL https://pi-rust.com/install.sh | shOr with Homebrew:
Linux
curl -fsSL https://pi-rust.com/install.sh | shOr with Homebrew:
Windows
irm https://pi-rust.com/install.ps1 | iexA drop-in replacement for pi
Install pi-rust, run pi, and keep working the way you do now.
Your setup carries over
pi-rust reads
Configuration files~/.pi/agent: logins, settings, models, key bindings, MCP servers, and sessions. Session files and RPC events match pi byte for byte, so you can switch between the two.Your extensions keep working
TypeScript extensions, skills, prompt templates, themes, and pi packages work as they are. Extensions run on a built-in QuickJS engine with the Node built-in modules, or on Node 22 if you set
Extension runtimeextensionRuntime.1:1 parity, checked daily
A workflow compares pi-rust with upstream pi every day. In the latest report, pi-rust has:
- CLI flags
- All of pi's
- Slash commands
- All of pi's
- Built-in tools
- All of pi's
- Extension API
- All of pi's
Memory with 20 sessions at once
20 pi-rust sessions running at once on a 16 GB Mac peaked at 680 MiB in total. Node Pi 0.73.1 used 3,431 MiB and Codex CLI 0.162.1 used 3,275 MiB.
- Pi Rust 0.1.9
- 680 MiB
- Node Pi 0.73.1
- 3,431 MiB
- Codex CLI 0.162.1
- 3,275 MiB
Each pi-rust process peaked at 33.52–35.66 MiB. Batch time: Pi Rust 0.1.9 13.12 s, Node Pi 0.73.1 17.94 s, Codex CLI 0.162.1 15.1 s.
Start in the folder you work in
Run pi in a project and talk to it. Use print mode for one answer, JSON or RPC mode when another program drives pi, and -c to pick up the last session.
pi # talk to pi in this folder
pi -p "Summarize src/main.rs" # one answer, then exit
pi --mode json -p "List the TODOs" # one JSON event per line
pi --mode rpc # JSON-RPC over stdio
pi -c # continue the last session here
pi --model openai/gpt-5.5 --thinking high
cat error.log | pi -p "Explain this error"What pi-rust adds to pi
Everything in pi, plus:
- /diff, /review, /undo, and /retrySlash commands upstream pi doesn't have, plus /init and /context.
- pi doctor, pi sessions, and pi statsCheck your setup, list and delete sessions from the shell, and see your usage.
- Run limits and structured outputStop a run at --max-turns or --max-cost, or hold the answer to a JSON schema with --output-schema.
- ACP mode for Zedpi --mode acp runs pi as an agent inside Zed and other ACP editors. Upstream pi needs a separate adapter.
- Subscription usage limits/usage shows the 5-hour and weekly windows of your Claude, ChatGPT, Cursor, SuperGrok, and Antigravity logins.
- Native extensions and a marketplaceAn extension can be a native program that talks JSON-RPC over stdio, installed from a signed index.
Providers, MCP, and editors
Every provider pi supports, plus Cursor and Google Antigravity subscriptions. Log in with /login or an API key. MCP servers connect over stdio and HTTP, and pi runs inside Zed through ACP.
- Anthropic
- OpenAI
- OpenAI Codex
- Google Gemini
- Google Vertex AI
- Amazon Bedrock
- Azure OpenAI
- Mistral
- xAI
- GitHub Copilot
- OpenRouter
- Kimi
- Cursor
- Google Antigravity
- llama.cpp
Who makes pi-rust
Ryan Yannelli, a software engineer in New York, builds and maintains pi-rust. It's a 1:1 Rust port of pi, checked against upstream every day.