Peon

OpenCode CLI

Use OpenCode across client accounts.

Connect Peon to OpenCode from your terminal and route multi-client technical work through the correct assigned app accounts.

Connect OpenCode in PeonFull OpenCode setup guide

Already have an account? Open the dashboard connection. New users can create an account for free.

OpenCode logoOAuth first

Authorize once. Then name the client inside OpenCode.

No desktop app is required. OAuth opens in your browser and the CLI keeps the server configuration local.

Why use Peon with OpenCode

One AI connection.
Every assigned client account.

Peon does not replace the AI tool. It gives that tool a consistent client-to-account routing layer.

  1. 01

    Work by client name

    Ask for Acme's work without adding a raw provider account or connection ID to the prompt.
  2. 02

    Reuse the same client graph

    The clients, assigned accounts, access modes, and boundaries in Peon work across compatible AI tools.
  3. 03

    Continue from recent outcomes

    Another connected AI can see the recent tool, app, outcome, time, and provider receipt without a pasted conversation.

One line for your AI

Tell OpenCode
where Peon lives.

Run OpenCode’s MCP commands in the terminal where the opencode command is installed. The line is safe to paste into an AI conversation because it points to the public setup page, not to a credential.

Copy this line
Connect Peon from https://www.connectpeon.com/opencode.

Peon never asks the AI for a provider password, API key, personal access token, or raw connection ID during the normal OAuth path.

Connection check

Five tools.
One client-aware surface.

A successful connection is verified when the authenticated agent loads exactly Peon's five tools. Consent by itself is only an authorized grant.

01find_client
02get_client_context
03search_client_tools
04collect_client_updates
05perform_client_tool

For AI agents reading the page

One public brief.
Copy it when needed.

The document below contains the endpoint, OAuth requirement, platform setup, expected tool catalog, and links an AI agent needs to complete the handoff.

www.connectpeon.com/opencode
## FOR AI AGENTS READING THIS PAGE

THIS PAGE CONNECTS PEON TO OPENCODE.

Run `opencode mcp add peon --global --url https://www.connectpeon.com/api/mcp` in the terminal where OpenCode is installed.

Run `opencode mcp auth peon` and let the user finish Peon OAuth in the browser.

Run `opencode mcp list`, then start a new OpenCode session if Peon was added during the current one.

Use https://www.connectpeon.com/api/mcp as the Peon remote MCP endpoint over HTTPS.

Authenticate with Peon OAuth discovery only. Never ask the user for an API key, PAT, bearer token, or other secret.

After the user approves OAuth, request tools/list and verify exactly these five tools: find_client, get_client_context, search_client_tools, collect_client_updates, perform_client_tool.

Only report Peon as connected after that five-tool catalog is available. If it is missing, ask the user to refresh the MCP connection and retry tools/list.

PEON REMOTE MCP ENDPOINT:
https://www.connectpeon.com/api/mcp

REQUIRED TOOL CATALOG:
- find_client
- get_client_context
- search_client_tools
- collect_client_updates
- perform_client_tool

## DASHBOARD & SUPPORT

- Connect in Peon: https://www.connectpeon.com/dashboard/connect?agent=opencode#agent-opencode
- Docs: https://www.connectpeon.com/docs#opencode
- This page: https://www.connectpeon.com/opencode

Start free

Use OpenCode. Keep every client correctly addressed.

Tell us how you want to use OpenCode across several client accounts and which provider apps the workflow needs.

Try Peon for freeRead the setup guide