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

Grok, meetyour Scout agents.

Scout can run the Grok CLI on your project, and Grok can call your other agents.

Scout → Grok CLI: available (grok-acp) · Grok CLI → Scout: local MCP · Grok Bot → Scout: invite-only pilot (see /grokbot)

Use supported agents you have installed, authenticated and connected.

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

~/dev/app $ scout ask --project ~/dev/app --harness grok-acp --notify "Review the latest changes."

working…accepted · ref 9d02

~/dev/app $ scout wait 9d02

working…completed · 1m 10s

grok (grok-acp) replied:

  1. Latest changes look correct. One suggestion: add a test for the empty-ref path.

executionResolution: grok-acp · ~/dev/app

~/dev/app $

Grok calls Scout

Available

MCP (local), MCP (hosted) · pilot

Let the Grok CLI call Scout ↓

Scout runs Grok

Available

grok_acp

Run Grok from Scout ↓

Replies reach your open session

Not documented

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

Looking for the hosted connector? Go directly to Grok Bot setup

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

    Ask Scout to run Grok on a specific project and explain one small piece of code without changing it.

    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 Grok

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

  • For local execution: a healthy Scout broker and the grok CLI on PATH (grok --version), authenticated with xAI. Check scout runtimes --json for grok-acp.
  • For Grok CLI calling Scout: scout on PATH on the same machine.
  • For Grok Bot: an operator-provisioned, online MCP bridge (invite-only). Open the dedicated Grok Bot guide.
  • Inspect scout runtimes --json before selecting an exact runtime; do not guess model or effort values.
Scout runs it

Run Grok from Scout

Start here
  1. 01

    Launching Grok from Scout?

    Check broker health and confirm grok-acp is ready. Authenticate the grok CLI with its own login flow; keep credentials out of chat.

    grok --version
scout doctor
scout runtimes --json
  2. 02

    Launch a small Grok review

    The exact form names the listed runtime grok-acp and a catalog model. --profile grok and --harness grok are accepted aliases of grok-acp. The project path belongs to the Scout machine. If grok-acp is not ready, stop and finish its setup.

    scout ask --project /absolute/path/to/project --harness grok-acp --model grok-4.6 --notify "Review the latest changes and report findings. Do not edit files."
# Short form, same runtime:
scout ask --project /absolute/path/to/project --profile grok --notify "Review the latest changes and report findings. Do not edit files."
calls Scout

Let the Grok CLI call Scout

03

Done when

  • For Grok Bot, verify whoami through the connector.
  • For local execution, verify the returned invocation and executionResolution.

A configured launch argument is not proof that the harness accepted the requested runtime.

04

If it breaks

Unsure which Grok integration to install
If Grok Bot is calling Scout tools, use /grokbot. If the grok CLI on your machine is calling Scout, use grok mcp add. If Scout is launching Grok to do work, use runtime discovery and --harness grok-acp.
Profile unavailable or authentication rejected
Inspect scout runtimes --json and the local runtime configuration. Ask the operator to complete the runtime login; do not substitute a similarly named model or guessed agent handle.
05

Where it stops

  • Grok Bot hosted access and Grok CLI execution are not interchangeable. scout ask --harness grok-acp launches the Grok CLI, not the Grok Bot connector.
  • grok is an unlisted alias; the runtime catalog lists grok-acp. Both run over the same grok_acp transport.
  • Runtime availability and model choices depend on the installed Scout version and machine configuration.
  • 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.