$ cat ~/map/pion.md
Pion
RPC-backed Electron desktop GUI — streaming chat, session fork, git worktree review loop, and a bounded multi-agent flow.
tools✓ Sep 9
Facts
- repository
- github.com/NiST0001/Pion ↗
- GitHub Stars
- ★ 5
- Forks
- 1
- license
- MIT
- npm / mo
- —
- last push
- Oct 12, 2026
install
./dev.sh## TL;DR
A local Electron and React desktop GUI for the pi coding agent: it drives pi as an RPC subprocess and adds streaming chat, session history with fork points, a git worktree review loop, auto-verified build commands, and a permission-bounded multi-agent workflow.
## Key points
- $Drives the pi coding agent as an --mode rpc subprocess from the Electron main process, with one RpcClient per session; credentials stay in ~/.pi/agent/auth.json and never reach the renderer.
- $Streaming chat with collapsible thinking, GFM markdown and code highlighting, clipboard image paste and @ references, plus slash commands for pi built-ins and Pion's own /plan, /verify, /agents, and /yolo.
- $Session history loads lazily from ~/.pi/agent/sessions/ with favorites and hover previews; conversations fork from any user message, and git branches render as a worktree tree.
- $Review loop: hunk/line-level staging, commits with hooks, merge/rebase/cherry-pick conflict resolution, snapshot-guarded operations, and auto-discovered typecheck/lint/test/build commands that can feed failure diagnostics back to the agent.
- $Bounded multi-agent flow: /agents runs Planner → Implementer → Reviewer → Tester with read-only planner and reviewer, a worktree-confined implementer, and an ff-only merge that requires review plus verification to pass.
- $Embeds the official pi.dev package store for extensions and skills, enforces project-level tool policies (allow/ask/deny, with --no-approve until a project is trusted), and tracks per-turn token, cost, duration, and compaction metrics.
## FAQ
Q Is Pion an official pi client?
No — it is a community Electron app that launches pi as an --mode rpc subprocess; model credentials and the default provider or model still come from pi's own auth.json and settings.json.
Q What are the system requirements?
Node 22.12 or newer (developed on Node 24) and a local pi installation; a NODE_ENV=production shell needs NODE_ENV=development npm install --include=dev for the first install.
## References
## Related entries
$ Pi Client
Flutter client for pi — one codebase reaching Android, iOS, macOS, Windows, Linux, and Web.
$ Pi Desktop
Open-source macOS client driving a local pi over JSONL RPC — projects, streaming conversations, commands, extensions.
$ pi-gui
Community Electron desktop GUI for Pi with a threaded timeline, git worktree isolation, integrated terminal, and inline diff viewer.
## Guides
Last updated: Sep 9, 2026