Extensions for pi that we wrote and publish on npm.
Paste in a terminalSay to Claude Code or pi
pi-provider-guardOur pi extensions
what
Keeps pi off the pay-per-token Anthropic provider. If a session selects it, the guard switches back to a safe model and tells you. It can also add your own standing rules to every turn.
why
Picking the metered provider by mistake bills each turn by the token. The guard prevents that unless you turn it off on purpose.
Gives a session a way to schedule its own check-in: after a delay, a message is delivered back into the session, and a countdown shows while it waits.
why
An agent waiting on a build inside a command locks the session until it ends. With a wakeup it stays free to talk to you and picks the job back up on time.
Connects a pi session to tmux, the program that keeps terminal sessions running in the background: a status line with the model and how full its context is, a bell on that pane when the agent needs you, and its registration on muster.
why
It lets a pi session show up in tmux the way a harnessed coding session should, so you can see from the status bar which session wants you.
Copies one part of the agent's last answer so it pastes cleanly: a code block exactly as written, a quoted message on its own, or the prose as plain text. You press alt+c, or pick the part from a list.
why
Copying the whole answer brings its markdown marks along, and copying from the screen brings line wraps and borders. pi-copy reads the answer's source instead.
Shows each shell command the agent runs as two calm lines: the command, and ok or error with a line count. ctrl+o expands everything back to the full view.
why
pi's full view of every command is useful when debugging and noisy during routine work. The agent still receives the full output either way.
Connects each pi session to hail on your machine, so a paired phone can watch the session and send it a prompt. It does nothing while hail isn't running.
why
It is the pi side of hail, which is in design and not released yet.
Connects pi sessions to casebook. It records the git and GitHub commands each session runs, gives the session a short briefing on the state of its repository at the start, and keeps casebook in sync in the background.
why
The agent knows the state of your repository without you having to ask, and casebook knows which session did what.
Reloads a pi session by itself, when it is idle, after the installed pi packages change on disk, for example after kempt brings them up to date.
why
A running session keeps the code it loaded at startup, so after an update it can run a mix of old and new code until reloaded. That is easy to miss with several sessions open.
Connects pi to TypeSafe's Jev, a model that answers typed questions about a piece of code with structured answers rather than free text. It stores the TypeSafe key and gives other extensions a small client.
why
It is the shared base for features built on Jev; cull uses Jev to judge tests.
ask
(works by itself once installed; cull asks for the key the first time)
Other people's pi packages that we patch and republish under the @subaud-tools name on npm. When we need a change before upstream merges it, we fork, patch and republish, so we're never blocked waiting on an upstream fix. Each fork follows upstream every day.
pi-claude-bridgeForks we keep
what
Runs Claude models inside pi through Claude Code, on your Claude subscription. Our fork adds an accounts panel, /claude-account: each session uses one Claude account, two sessions can use different ones, and one key switches every open session at once. Upstream is by Eli Dickinson.
why
We work across more than one Claude subscription. Switching used to mean signing in again; upstream had a different approach waiting in review, so we built the panel in our fork.
ask
(a panel you open in pi; see "Switching Claude accounts" under Habits)
Shows how much of each provider's usage budget is left, and when it resets, in pi's footer. Our fork adds a usage cache shared by every session on the machine. Upstream is by Sreetej510.
why
With many sessions open, each one asking the provider for usage on its own adds up. The shared cache lets them all read one answer.
Scheduled work for pi agents: a prompt, a shell check or a reminder that fires every so often or at a set time. Our fork sends each job's turn to the session that created it. Upstream is by pungggi.
why
With several sessions open on one project, a scheduled prompt used to land in whichever session got there first, in the middle of unrelated work.
ask
Say to your agent
Every morning at nine, check whether last night's build passed.
Rules for what an agent may do: allow, ask or deny, for each tool, shell command and file pattern, with a prompt when a rule says ask. Our fork adds a hook that lets hail answer those prompts from your phone. Upstream is by Chris Lasher (gotgenes).
why
It keeps risky commands behind your yes. hail needs the fork's hook to mirror the same prompt to your phone.
Other people's pi packages that we use as they are, credited to their authors.
pi-subagentsPackages we rely on
what
Lets a session hand work to subagents, separate agents that each run with their own instructions and model: an implementer, a reviewer, a broad search. They run in the background, and you can steer them mid-run. By tintinweb.
why
Long work runs elsewhere, so the main session stays free to talk with you.
ask
Say to your agent
Have a worker build this plan, and a reviewer from the other provider check it.
Connects pi to MCP servers, programs that offer an agent extra tools such as a browser or a database, through one small proxy tool. Servers start only when the agent uses them. By Nico Bailon.
why
Each MCP server's tool list can take thousands of tokens of the agent's context before you've used it. The adapter lets the agent look up the tools it needs when it needs them.
ask
Say to your agent
Which MCP servers can you reach, and what tools do they have?