scout is not found / bun: scheme error

Check scout on PATH and its installed runtime. The cursor-scout installer can probe the local command and repair a stale Node-backed shim. From a clone of oscout/cursor-scout, preview the write with bun run install:global -- --dry-run, then run bun run install:global -- --force to replace a stale entry (bun run install:project targets one project).

Remote connection cannot reach the machine

Use the MCP guide bridge checks. A successful OAuth login does not prove the local bridge is online, and OAuth does not create a bridge. If no operator has provisioned one for you, stop.

A Scout-launched Cursor run stops at a tool approval

Expected: broker-owned Cursor runs use safe-reject permissions and decline tool calls that need approval. Use them for read-only review, or run the edit in your own Cursor session.

Scout + Cursor● Cursor asks an agent○ an agent hands Cursor work

Your editor.Your agent network.

Cursor's agent can reach every other agent, and Scout can run Cursor's agent on a project.

Cursor → Scout: local MCP available · hosted HTTP invite-only (operator provisions your bridge) · Scout → Cursor: available (cursor_acp, safe-reject)

Use supported agents you have installed, authenticated and connected.

Set it up Let your agent do itCursor reads the setup for you

retry.ts — app

Agent

Ask @codex through Scout for a second opinion on this function.src/retry.ts

Called MCP tool askworking…flight accepted
Called MCP tool invocations_waitworking…completed

Codex replied with one suggestion:

retryDelay() cap the backoff; after 8 retries it grows past a minute.

Add a follow-up

Agent

Cursor calls Scout

Available

MCP (local), MCP (hosted) · pilot

Ask from Cursor (local MCP) ↓

Scout runs Cursor

Available

cursor_acp

Launch Cursor through Scout ↓

Replies reach your open session

Not documented

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

Start here

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 →
02 · Try
Your first useful task
From Cursor’s chat, ask a coding agent to review the change you are working on without editing it.
Name the project and keep the request small. Asking for no edits describes the task; it does not restrict the agent’s permissions.
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.

Set it up

Fastest

Give this to Cursor

Connect yourself to Scout for me. Read openscout.app/cursor/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.

reads agents.md
checks prerequisites
asks before any credential
runs the verification

You need

OpenScout installed, scout on PATH, and scout doctor passing.
For local setup, Cursor must run on the Scout machine.
For remote setup, all hosted-bridge requirements apply, including an operator-provisioned bridge; see /mcp. Hosted access is invite-only.
To launch Cursor from Scout: the cursor-agent CLI on PATH, signed in with cursor-agent login or CURSOR_API_KEY.

calls Scout

Ask from Cursor (local MCP)

Start here

01
Configure local MCP
Merge this entry into .cursor/mcp.json for the project, or ~/.cursor/mcp.json for your user. Preserve other MCP servers. Replace the project path with an absolute path on this machine.
```
{
  "mcpServers": {
    "scout": {
      "command": "scout",
      "args": [
        "mcp",
        "--context-root",
        "/absolute/path/to/project"
      ]
    }
  }
}
```
02
Reload and confirm tools
Open Cursor MCP settings / Customize, enable Scout, and refresh the tool list. Call whoami and confirm the intended project context.
03
Ask for a small review
Use Scout ask with the project path and a supported harness. Keep the returned handle and inspect completion before declaring the review finished.
```
{"projectPath":"/absolute/path/on/scout-machine","harness":"claude","body":"Review the latest changes and report findings. Do not edit files.","replyMode":"notify"}
```

calls Scout

Hosted HTTP (invite-only)

Scout runs it

Launch Cursor through Scout

01
Or launch Cursor through Scout
This is the other direction: Scout runs cursor-agent acp (cursor_acp) as a fresh session it owns. No --model flag: the runtime uses your Cursor plan's model, and the catalog lists no Cursor models. Broker-launched Cursor runs use safe-reject permissions, so tool calls that need approval are declined.
```
cursor-agent login
scout runtimes --json
scout ask --project /absolute/path/to/project --harness cursor --notify "Review the latest changes; do not edit files."
```

Done when

Success means Scout tools are visible, whoami returns the intended identity, and a small ask produces a durable invocation/flight handle.
A handle proves acceptance; inspect the flight for the eventual result.

If it breaks

scout is not found / bun: scheme error: Check scout on PATH and its installed runtime. The cursor-scout installer can probe the local command and repair a stale Node-backed shim. From a clone of oscout/cursor-scout, preview the write with bun run install:global -- --dry-run, then run bun run install:global -- --force to replace a stale entry (bun run install:project targets one project).
Remote connection cannot reach the machine: Use the MCP guide bridge checks. A successful OAuth login does not prove the local bridge is online, and OAuth does not create a bridge. If no operator has provisioned one for you, stop.
A Scout-launched Cursor run stops at a tool approval: Expected: broker-owned Cursor runs use safe-reject permissions and decline tool calls that need approval. Use them for read-only review, or run the edit in your own Cursor session.

Where it stops

Cursor local MCP and the hosted Grok Bot connector are separate setup paths.
Hosted HTTP access is invite-only: it needs a bridge your operator provisions. There is no self-serve sign-up.
Broker-launched Cursor runs use safe-reject permissions. Tool calls that need approval are declined, so use them for read-only review unless you attach an approval consumer.
Cursor's ACP mode does not load team-level MCP servers configured in the Cursor dashboard.
Marketplace submission is not marketplace approval.
High-trust local developer pilots. Connection traffic may contain project paths, instructions, messages, and agent results. Data and privacy.

For agents

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

Your editor.Your agent network.

Start here

Get one route working

Your first useful task

Wait for the answer

Before your next ask

Set it up

Configure local MCP

Reload and confirm tools

Ask for a small review

Or launch Cursor through Scout

Done when

If it breaks

Where it stops

For agents