Scout
DocsBlogToolsContact
Scout + OpenCode● OpenCode asks an agent○ an agent hands OpenCode work

Any model OpenCode runs,working with your agents.

Whatever model OpenCode is running can ask your other agents, and Scout can run OpenCode on a project.

OpenCode → Scout: available (local MCP) · Scout → OpenCode: available (opencode_acp)

Use supported agents you have installed, authenticated and connected.

Set it upLet your agent do itOpenCode reads the setup for you
opencode — ~/dev/app

OpenCode · ~/dev/app · scout tools loaded

> Use scout to ask @codex whether this migration is safe.

● scout.ask(to: "codex")

└working…queued · ref 2e77

● invocations_wait(ref: "2e77")

└working…completed · 41s

● Codex replied on ref 2e77: safe to run.

  1. It adds one nullable column and needs no backfill.
>

OpenCode calls Scout

Available

MCP (local)

Ask from OpenCode ↓

Scout runs OpenCode

Available

opencode_acp

Run OpenCode from Scout ↓

Replies reach your open session

Not documented

The guide doesn't say. Follow the returned ref.

01

Start here

  1. 01 · Connect

    Get one route working

    Check the prerequisites and access gates, then get one documented route working before asking for work.

    Follow the setup →
  2. 02 · Try

    Your first useful task

    From OpenCode, ask another agent to explain one failing test and return a suggested next step.

    Name the project and keep the request small. Asking for no edits describes the task; it does not restrict the agent’s permissions.

  3. 03 · Read

    Wait for the answer

    Keep the returned reference. Check the work’s status and read the completed response; a queued receipt is not the answer.

    Check what success looks like →

Before your next ask

Where will the reply appear?

Keep the returned reference and retrieve the completed response through your configured Scout interface. Automatic delivery into this open session is not established by this guide.

What if the answer hasn’t arrived?

Inspect the existing task before submitting another one. A wait timeout does not establish that work failed. If it needs access or input, resolve that condition before continuing.

How do I follow up?

Continue using the returned reference or exact session handle supported by this integration. Keep it with the findings so your next question follows the same work.

Can Scout run this integration, or only receive asks from it?

These are separate capabilities. Check the supported directions on this page. Connection alone does not establish that Scout can launch the integration or reach an existing session.

02

Set it up

Fastest

Give this to OpenCode

Connect yourself to Scout for me. Read openscout.app/opencode/agents.md and follow it step by step: check the prerequisites first, ask me before any step that needs a token or other credential, and finish with its verification step. Tell me what you verified.

  1. reads agents.md
  2. checks prerequisites
  3. asks before any credential
  4. runs the verification

You need

  • OpenScout installed and a healthy local broker (scout doctor).
  • OpenCode installed and authenticated on the Scout machine.
  • An authorized project path and a supported destination runtime.
calls Scout

Ask from OpenCode

Start here
  1. 01

    Configure the local MCP server

    Merge this into opencode.json without replacing other settings. OpenCode uses the mcp key and a command array; replace the project path.

    {
  "mcp": {
    "scout": {
      "type": "local",
      "command": [
        "scout",
        "mcp",
        "--context-root",
        "/absolute/path/to/project"
      ],
      "enabled": true
    }
  }
}
  2. 02

    Confirm tools and identity

    Restart or refresh OpenCode’s MCP connection. Ask it to call Scout whoami and verify that the intended project and actor are represented.

  3. 03

    Ask for a small review

    Ask the connected agent to use Scout for a review in your actual project directory. Route by project and capability, keep the returned handle, and inspect the result. Use the current tool schema instead of guessing a recipient name.

Scout runs it

Run OpenCode from Scout

03

Done when

  • OpenCode shows the scout tools after a restart.
  • whoami returns the identity you expect.
  • A small ask returns a ref, and scout wait on it reports a completed reply.
04

If it breaks

Scout is not found or cannot connect
Check scout on PATH and run scout doctor in the same environment as the client. A desktop app may have a different PATH from your terminal.
Requested runtime is unavailable
Inspect scout runtimes --json and finish that runtime’s setup. Do not silently choose a different harness or model.
OpenCode drops the Scout server at startup
OpenCode gives a local MCP server 5000 ms to start by default. If scout mcp starts slowly (cold start or a broker wake), add "timeout": 15000 to the scout entry and restart OpenCode.
05

Where it stops

  • This is a local developer pilot. Client permissions and runtime availability still apply.
  • Installing a host package does not provision hosted access.
  • High-trust local developer pilots. Connection traffic may contain project paths, instructions, messages, and agent results. Data and privacy.
06

For agents

agents.mdThe setup contract your agent follows. Same content as this page.integration.jsonDirections, gates and steps as data.