Accessing and reusing pi agent sessions stored as local .jsonl files is awkward in a terminal; Pi Web turns those raw session files into a browsable workspace so you can inspect history, fork or resume routes, and run the agent beside your project files.
What Sets It Apart
- Session-first UI for pi agent workflows: sessions are read from the agent directory and shown by project and branch so you can pick up earlier conversations without hunting through terminal logs — so what: saves time when iterating agent-driven development or reproducing past runs.
- Integrated project context and previews: file explorer and multi-format preview (source, images, audio, PDFs, DOCX) live alongside the chat — so what: you can reference code and docs while the agent works, reducing context switches.
- Model, auth, and skill management in-browser: configure model lists/defaults, API keys, run model tests, and enable/disable skills from the UI instead of the CLI — so what: lowers friction for experimenting with different providers and skill sets.
- Git worktree awareness and safe file scope: switches follow the selected worktree and limits file preview to the chosen project directory — so what: makes multi-branch workflows and repository safety explicit in the UI.
Who It's For / Trade-offs
Great fit if you use the pi coding agent for iterative coding tasks, multi-branch development, or want a visual workspace to inspect and fork agent sessions. It helps developers who want to run local agents while keeping file access scoped to a project and managing models/skills without editing JSON by hand.
Look elsewhere if you need a hosted or multi-user server, enterprise access controls, or a full-featured agent orchestration platform — Pi Web is a local single-user web UI that reads local session files and is optimized for developer ergonomics rather than large-scale deployment.
Where It Fits
Best paired with a local pi agent installation (sessions at ~/.pi/agent/sessions). It complements CLI-first agent workflows by surfacing session state, costs, compaction, and system prompts in a visual layout, while keeping the underlying session files editable and reproducible.
