Pi

One command adds the OpenCode Console extension to Pi on your computer and connects it to a workspace. You keep running pi as before, with these changes:

• /model lists the workspace's models, including ones from other providers, and new sessions start on the newest Claude Sonnet the workspace offers. Requests go through Console, so the workspace's model rules and budgets apply.
• The workspace's Providers rules apply in Pi. A provider they block shows no models, and requests to it are stopped, including ones that use your own API key.
• Every tool call, every !command and every /skill:name is checked against the workspace's policies first.
• The workspace's MCP servers are added, with OpenCode Web Search when the workspace offers it.
• The workspace's Library skills are added to Pi, so you can run each one as /skill:name. Its Library instructions are added to Pi's system prompt.

Pi picks up changes in Console as you use it, once its copy is more than a minute old.

• An OpenCode Console workspace you're a member of.
• Pi (setup was tested with 1.5.0).
• Node.js 22 or later, for npx.

1. Run this in a terminal:
   npx @opencode/console setup pi
2. Your browser opens Console. Check that the code matches the one in your terminal, approve the sign-in and pick the workspace.
3. Setup prints the models, policies, MCP servers and Library items it set up. Run pi to start.

Run the command again any time to update the setup. If the workspace offers no models, Pi keeps its own providers and still gets the workspace's policies, MCP servers and Library.

The extension is also a Pi package. To install it with Pi instead, run these, then start Pi:

To see who you're signed in as, the workspace, and how many policies and models it has, run:

To undo setup, run:

It takes the extension out of Pi's settings, puts back your default model unless you've changed it since, and deletes the workspace's skills. If you installed it with pi install, run pi remove npm:@opencode/console instead. You stay signed in until you run npx @opencode/console logout.

• Policies are checked by the extension inside Pi, so they hold only while it's loaded. Console enforces model rules, budgets and MCP tool rules itself, on every request that goes through it.
• Until Pi has the workspace's policies, it blocks every tool call. A check that fails blocks the call too. If Console can't be reached, the policies it last fetched stay in place.
• If you already have an MCP server with the same name as one of the workspace's, Pi keeps yours.

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays). The support page covers data requests, security reports and more.