nikiforovall/pi-inspect

pi-inspect is a dashboard that shows what a coding-agent session has actually loaded into itself. It is built for an AI coding tool called pi, made by pi.dev, and it answers a question that is easy to ask but hard to check from the chat window: which tools, slash commands, skills, and system-prompt text are present in this particular session right now? Installation is one command typed inside pi: 'pi install npm:pi-inspect'. After that, the user controls the dashboard with a slash command also typed inside pi, '/inspect'. The README lists the variants: '/inspect' opens the dashboard for the current session in a local browser window, '/inspect <sessionId>' opens it pinned to a specific past session, '/inspect snapshot' re-captures the session state right now, '/inspect list' prints every captured session id in the terminal, and a small set of subcommands manages the local server that backs the dashboard, with start, stop, restart, and status. The dashboard itself runs on localhost, by default on port 5462, and the current session id is carried in the URL query string so a refresh or a copy-paste of the URL keeps the view pinned. There is also a Share button in the top bar that builds a self-contained link of the current snapshot. The snapshot is compressed and base64-encoded into the part of the URL after the hash mark, which means the recipient does not have to upload anything anywhere; the snapshot lives entirely inside the link. The recipient opens the link on a static page hosted at nikiforovall.blog/pi-inspect and sees the same tools, commands, skills, and system prompt as the sender. The README warns that, since the link includes the system prompt and the working directory, the user should not share secrets they would not paste into a chat window. The captured contents for each snapshot are: every tool with its name, description, parameter schema, and source; every slash command with its name and source; the full system prompt text, split into the system part, the user-level AGENTS.md, and the project-level AGENTS.md; and session metadata, including the working directory, the model, the session id and name, and the timestamp of capture. Snapshots are stored on disk under '~/.pi/agent/inspect/snapshots/' as JSON files named by session id.