Features · Install · Recordings · Commands · Settings · leverage.computer
- Multiplayer harness: who has the session open, who is typing, and whether the owner is around. Each message shows who wrote it.
- Company computer: the session runs in Leverage, so closing Pi doesn't stop the agent.
- Steering: Enter while the agent works steers it after its current step.
- Governance: the agent asks before it runs a command. Pick Approve once or Deny.
npm install -g @earendil-works/pi-coding-agent@1.2.0
pi install git:github.com/leverage-computer/pi-plugin@v0.1.0
piThen, in Pi:
/leverage login: sign in./leverage new: start a session./leverage: open one your team started./leverage exit: go back to plain Pi.
- Above the composer: who has the session open, who is typing, and whether the owner is around. F1 shows the full list.
/leverage new, then type what you need. Your first message starts the session.- Ctrl+L picks the model and Shift+Tab its effort, as in Pi. Ctrl+V sends an image with your message.
- Edits show as diffs. Checklists, helpers and background commands get their own cards.
- A helper's card follows the helper's own conversation. Ctrl+O shows all of it.
- Enter while the agent works steers it after its current step.
- Alt+Enter queues a follow-up instead. Alt+Q takes queued follow-ups back.
- Waiting messages show as Steering or Follow-up, as in Pi's own queue.
- The question opens on its own. Pick Approve once or Deny.
- Escape approves nothing. F4 opens the question again.
- Plans to review work the same way.
/leverage, or F3 in a session, lists them. Type to filter, then Enter.- Each message shows who wrote it. Anything you send shows up for everyone.
/leverage outputs: the files the agent made. Enter reads one, Tab saves it here./leverage files: all of the session's folders./leverage changes: what changed, on which branch, and its pull request.
- Closing Pi doesn't stop the agent.
- A message Leverage hasn't confirmed goes again by itself. Leverage keeps it once.
- Pi can't run
!shell commands in a session yet. Ask the agent instead.
| Type or press | What happens |
|---|---|
/leverage login |
Sign in |
/leverage logout |
Sign out |
/leverage new |
Start a new session |
/leverage |
Find and open a session |
/leverage exit |
Go back to plain Pi |
| F1 | Pick a channel for a new session |
| Ctrl+L | Pick a model |
| Shift+Tab | Pick the reasoning effort |
| F3 | Find and open a session |
| F4 | Review what the agent wants to run |
| Enter while the agent works | Steer it after its current step |
| Alt+Enter | Queue a follow-up |
| Alt+Q | Take queued follow-ups back |
| Escape | Stop the agent |
/name <name> |
Rename the session |
/tree |
Read older messages |
/compact |
Compact the session's context |
/leverage archive |
Put the session away |
/leverage skills |
Pick a skill for your next message |
/leverage connectors |
The apps your workspace connects to |
In the session list, Tab renames or archives a session.
- The plugin uses your Leverage CLI login, or its own in
~/.pi/agent/leverage.json. /leverage loginsets it up./leverage logoutremoves it.
| To change | Use |
|---|---|
| The server | LEVERAGE_HOST |
| The workspace | pi --leverage-workspace <name> |
| The session Pi opens | pi --leverage-session <id> |
Which channels Pi shows: Leverage Settings → Integrations → What each app gets.
You need Bun 1.4.2, Python 3 and macOS or Linux. Nix
gives the shell all three, and lints each commit with Biome and nixfmt:
nix develop, or direnv allow once.
bun install --frozen-lockfile
bun run check
pi -e .MIT. See LICENSE.