The data is still pi’s
Keeps reading and writing sessions, models and credentials under ~/.pi/agent; stop pi-star and continue with the pi CLI or pi-web.
pi-star puts pi's sessions, agents, files, Git, terminals and model settings into a local web workbench. The UI comes from pi-web, the server is rebuilt in Rust + Axum, and your data stays in ~/.pi/agent.
MIT · No private edition · Optional QuadHub Token
Sessions
Add health check
working · quick
Fix build failure
idle · rpc
Review PR #42
waiting · quick
Add a health check to the Axum router.
I'll add an /api/health handler and a test.
router.rs · +18 −2
1
Rust binary
2
agent backends
0
extra servers to deploy
WHY LOCAL
Keeps reading and writing sessions, models and credentials under ~/.pi/agent; stop pi-star and continue with the pi CLI or pi-web.
Release builds put the pi-web UI inside the Rust binary and serve it through Axum.
Run it entirely on its own, or connect to QuadHub Tokens when you want unified model quotas.
CAPABILITIES
Sessions, file tree, chat, model selection, terminal and settings in one interface.
Keeps reading JSONL sessions and settings under ~/.pi/agent; stop pi-star and continue with the pi CLI or pi-web.
Standard PI runs through Node's pi --mode rpc; QuickPI runs in-process, switchable per session.
Release builds embed the UI and serve it through Axum; the server needs no Node runtime.
A Tauri 2 shell handles launch, supervision, tray and login items; installers bundle Node and pi.
Build it from source; optionally connect model calls to QuadHub Tokens for quota.
ARCHITECTURE
The browser talks to pi-star on the machine; the agent runs behind it and data stays in pi’s directory.
Browser
Web UI
pi-web interface · Vite build
Rust binary
pi-star
Axum · agent loop · tools
Files are the source
~/.pi/agent
JSONL · models · auth
QUICK START
cd ui && npm install && npm run build
cd ..
cargo build --release
./target/release/pi-star --port 30151Open http://127.0.0.1:30151, or install the Linux / macOS / Windows desktop build from Releases.
QUADHUB
optionalpi-star runs on its own, or can send model requests through QuadHub's Token service for unified metering and quotas. Without QuadHub, keep using your own providers and keys.
Read the integration noteMANUAL
Installation, architecture, CLI reference and the optional QuadHub Token integration.
Overview
Quick start
Architecture
QuadHub Tokens
Reference
LOCAL AGENT WORKBENCH
Local by default, with your own data and model configuration.