Your coding agents.In Hermes.
Hermes can hand work to your coding agents and read their replies.
Hermes → Scout: available (plugin or MCP stdio) · Scout → Hermes: not supported
Use supported agents you have installed, authenticated and connected.
HermesAsk my Scout agents to summarise today's commits in ~/dev/app.
- Used scout_invocations_askworking…ref 1b8d
- Used scout_invocations_waitworking…done
Today's commits in ~/dev/app, from Claude Code:
- Retry loop now clears its timer.
- Wait test awaits the ref.
- Landing deps bumped.
Scout runs Hermes Agent
No
Hermes is not a Scout harness
Replies reach your open session
No
Hermes pulls results through tools
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 Hermes, ask a coding agent to review a small change, then read the completed response using its returned reference.
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 Hermes Agent
Connect yourself to Scout for me. Read openscout.app/hermes/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
- Hermes Agent with plugin support (the package documents v0.6.0+), and Python 3.9+.
- Scout installed, a healthy broker, and scout mcp available on the host PATH.
- An authorized project path on the Scout machine.
Install the Hermes plugin
Start here- 01
Install the host plugin
Install the published GitHub source through Hermes, then start a new Hermes session. Hermes plugins are opt-in, so --enable skips the confirmation prompt. For a reproducible install, add --ref with a 40-character commit SHA.
hermes plugins install arach/hermes-scout --enable - 02
Verify the bridge
List the available tools and call scout_whoami. The plugin launches scout mcp over stdio and should identify the intended broker actor.
hermes tools list - 03
Use the Hermes tool names
Request work with scout_invocations_ask using projectPath and an optional supported harness. Use scout_invocations_get or scout_invocations_wait to observe the returned request; inspect each current input schema.
Or connect over MCP
- 01
Or connect without the plugin
Hermes is a native MCP client. Register scout mcp as a stdio server instead of installing the plugin; do not do both. Tool names then come from Hermes' MCP client rather than the plugin's scout_ prefix, so list the tools after connecting and use the names shown.
hermes mcp add scout --command scout --args mcp --context-root /absolute/path/to/project hermes mcp test scout
Done when
- hermes tools list shows the scout tools.
- whoami returns the identity you expect.
- A small ask returns a ref, and Hermes reads the completed reply from it.
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.
Where it stops
- Hermes is an agent host in this integration. Do not use --harness hermes. Select an implemented Scout runtime for any delegated execution.
- Hermes is an MCP/agent host here, not a Scout execution harness. --harness hermes is rejected.
- Scout cannot launch Hermes or deliver replies into an open Hermes session today. Hermes ships hermes acp, which would make a launcher possible; it is not supported and not promised.
- Plugin tool names have a scout_ prefix and can differ from native MCP names.
- High-trust local developer pilots. Connection traffic may contain project paths, instructions, messages, and agent results. Data and privacy.