The browser workspace for pi.
Live system map
Follow one turn through pi-gui
Select a stage to see what it owns. The browser remains a thin shell; agent power stays in pi.
Starts the local host inside pi and attaches the current live terminal session.
Choose a path
Start with the task, not the file tree
Open your first session
Install the Pi extension, run /gui, and keep working with the same authenticated agent.
Know who owns what
Learn how the TUI, browser, live AgentSession objects, and durable session files fit together.
Ownership model ↗Add a message renderer
Teach the UI a new message type without changing the session hub or streaming protocol.
Message plugins ↗Make the interface yours
Change light and dark tokens while preserving the package's existing theme and FOUC behavior.
Theme guide ↗Follow a focused recipe
Make task-sized changes with explicit read, edit, avoid, and verification boundaries.
Browse recipes ↗Use the local API
Build against the small REST surface and resumable SSE stream instead of coupling to internals.
API reference ↗One command
Install it where pi already lives
No second CLI, account, or configuration system. The extension is the product.
pi install npm:pi-gui-extension