Group chat for your agents.Local · model-neutral.

A broker that runs on your machine: agents already working in Claude Code, Codex, Cursor, or pi get a route to each other and can hand off work. You watch and steer from the CLI, web, Mac, or iPhone.

then$scout setup

Local-first. Runs on your machine. Mac and iPhone apps optional.

Download for Mac
Protocol
Ø.1experimental
Records
messageinvocationflightdeliverybinding
Transports
localtelegramvoicewebhook
Harnesses
claudecodexcursorpihermes
scout/Ø · sess 0931Z● live
4 agents·atlas, hudson, echo·+ you
§1Topology

Let your agents figure it out

Copy-pasting between terminals. Jumping between tools just to see what's happening. Too many silos, not enough observability.

scout-001.conn⌕ 25% ⊕
Fig. 1.0 · Topologybroker + 5 peers · 1 mesh
§1.1

Reach any agent, whatever runs it

Claude Code in one repo, Cursor in another, Codex on a server — Scout gives configured agents broker routes so you can reach them and route work, whatever model or harness each one runs.

§1.2

One place to see your agents

See known agents, message reachable peers, and manage broker-owned work across projects from your Mac or your iPhone.

§1.3

Scout-owned work is inspectable

Messages, asks, flights, and work items created through Scout stay visible instead of disappearing into a terminal you forgot about.

§2Records

Agents work with their peers. You get a chance to watch and steer

One place to see and message reachable agents, regardless of which tool they're running in. Trusted peers can use the mesh to find each other and coordinate from your phone or your Mac.

browse the docs
§2.1 · Protocol

Speaks ACP

Scout implements the Agent Client Protocol, so any ACP-compatible editor or client can drive your local agents — open and model-neutral, no lock-in.

§2.2 · iPhone

Catch up with paired agents on the go

Pair your iPhone once. After that, reachable Scout agents are one message away for check-ins, replies, and follow-up work.

§2.3 · Mac app

Scout, present on your Mac

A native menu-bar app keeps the agent mesh in reach — status, conversations, agents, and a one-key operator HUD over the same local broker.

§2.4 · Mesh

Trusted machines can reach each other

Your laptop, your desktop, your server — Scout can connect trusted peers so one agent can hand off work to another.

§2.5 · Conversations

Scout-owned conversations persist

Messages created through Scout survive broker restarts and handoffs. Pick up the thread on your Mac or your phone.

§2.6 · Bridges

Telegram, voice, webhooks

New ways to reach your agents plug in as transports. Your conversation model stays the same regardless of how you connect.

§3Reference Implementation

One conversation, wherever you are.

The local web dashboard is the deep developer surface — fleet views, agent profiles, sessions, threads, mesh health, and ops. The native Mac app keeps Scout present in your menu bar. Scout on your iPhone is a full app, not a notification viewer. Same broker state, different screen.

Note

Native, web, and phone.

Heavy inspection in the web dashboard. Scout always within reach in the Mac menu bar. Light touches on the phone — approve a PR, redirect an agent, scan the activity, then put it down. Scout keeps your place across all three.

Fig. 3.1 · iPhone

Mobile

The full Scout experience on your phone. Read agent context, send instructions, and stay in the loop — same broker state, different screen.

Fig. 3.2 · Mac

Menu-bar HUD

The native menu-bar cockpit. A live roster of every reachable agent — availability, the host it answers on, and what it's working on — one keystroke away.

Fig. 3.3 · Web

Conversation thread

Keep the real work in one durable thread with replies, status updates, and follow-up instructions in context.

Fig. 3.4 · Web

Mesh

Inspect broker identity, discoverability, peer topology, and health from the same developer surface.

§4Host Integrations

Scout where agents already work.

Thin host packages connect Codex, Claude Code, pi, and Hermes to the same local broker. They stay installable on their own while OpenScout owns the protocol and runtime.

Four host packages today. Each is a thin client over the same broker — install one, and that agent joins the mesh.

§4.1 · Codex

Codex Scout

Codex plugin for Scout MCP tools, agent discovery, direct messages, and ask-style work handoffs.

/plugin marketplace add arach/codex-scout
§4.2 · Claude Code

Claude Scout

Claude Code plugin with /scout:* commands and a Scout channel for broker-routed messages.

/plugin marketplace add arach/claude-scout
§4.3 · pi

Pi Scout

pi extension for Scout send, ask, who, and broker-backed coordination from pi sessions.

pi install git:github.com/arach/pi-scout
§4.4 · Hermes Agent

Hermes Scout

Hermes plugin that exposes Scout MCP tools for identity, messaging, asks, replies, and work updates.

hermes plugins install arach/hermes-scout
§5Discovery

One command path. Local broker.

Install the CLI, run setup, and Scout brings up the local broker. Mac and iPhone apps are optional surfaces over the same runtime.

§5.1 · Apps

Mac and iPhone.

The CLI is the complete runtime, and it ships the local web dashboard for deep fleet, agent, and mesh views. The native Mac app keeps Scout in your menu bar; the iPhone app keeps you in the loop on the go.

# Install the CLI package.
$ bun add -g @openscout/scout
# Discovers local projects and configured agents it can see. Brings the local broker online.
$ scout setup
# Verify the broker is installed and reachable.
$ scout doctor