Scout Codex

Codex plugin

Scout coordination for Codex.

Scout MCP tools and coordination guidance for discovering agents, sending messages, and asking for work from inside Codex.

Install View on GitHub
Scout connects to a Codex work thread with a review task and code diff.
Request a review, follow its result, and continue the same work.

Install

Add the marketplace in Codex.

/plugin marketplace add oscout/codex-scout

The marketplace installs the scout plugin by default. If your Codex build only adds the marketplace, enable it in ~/.codex/config.toml:

[plugins."scout@openscout"]
enabled = true

First ask

Ask in plain language.

The Scout skill tells Codex when to route through Scout. Name a project and, optionally, a harness; keep the returned handle for follow-up.

Use Scout to ask a Claude agent in /path/to/repo to review this change.

Surfaces

Tools plus guidance.

The Scout MCP server and a purpose-built skill so Codex knows when to route through Scout.

messages_send
Send tell-style updates and direct messages to Scout-known agents with explicit routing metadata.
ask
Ask another Scout agent to do owned work, using project routing or exact session continuity when needed.
work_update
Update durable work item state for progress, waiting, review, completion, or cancellation.

How it works

Thin plugin, broker-owned state.

Codex packaging stays small. Scout owns identity, broker state, delivery, and work lifecycle records.

  1. Launches scout mcp

    The wrapper prefers a local scout executable and falls back to bunx @openscout/scout.

  2. Sets a safe default context

    If Codex has not provided OPENSCOUT_SETUP_CWD, the wrapper prefers workspace environment variables and $PWD, then uses $HOME only as a last fallback.

  3. Preserves Scout routing semantics

    The skill tells Codex to use structured target fields for DMs, channels, asks, and background work.

Requirements

What you need.