Pi

Pi gets a skill and an auto-discovered extension. The extension rewrites the search command with the session, the call, the assistant text that led to the search and the compaction count, all read back from the session Pi saved, so a resumed session keeps its place in the trace.

Install

Setup finds Pi when pi is on PATH.

jevlin setup                      # sets up every agent it finds
jevlin setup -with pi             # found or not
jevlin agents install -client pi  # later, without the rest of setup

Restart Pi if it was already open.

What is written

path	what
~/.pi/agent/skills/jevlin/	The skill, rendered for your OS and shell.
~/.pi/agent/extensions/jevlin.ts	The extension. Pi discovers it on its own.

Use it

Ask Pi anything that needs the web, or be explicit:

/jevlin what changed in Vite 7's rollup migration

/jevlin off, /jevlin on, /jevlin status and /jevlin tier <band> work as in every agent with the skill. Pi runs Bash everywhere, Git Bash on Windows. See Search from your agent.

What to know

A resumed session keeps its place. The extension reads the session branch Pi persisted, not an in-memory counter, so the compaction count and the assistant text are right after a resume, a restart or a fork.

Observer, never an authority. The extension only attaches a trace to a command Pi has already decided to run. Any failure leaves the command untouched and the search runs with its per-shell trace instead.

At a session's start the extension also starts the flush and the daily release check, as Claude Code's session-start hook does. It pipes nothing to that process and reads nothing back. See Upgrading.

Known limits

• No turn end yet. Pi's searches carry no turn id, and no finished turn is reported, because Pi exposes no persisted turn identifier an extension can read. Searches and their trace are complete; what the turn concluded is not sent. Tracked at jevlin-go #101.

Remove

jevlin agents uninstall -client pi

Removes the skill and the extension. See Removing and coming back.