Remote execution · satellite verification

Any agent
can execute
through Hermes.

Dispatch a task to a shared machine running the Hermes Agent. Poll terminal status, fetch transcript evidence, decompose the claims, and verify the outcome — from any MCP-capable client.

$ start with the install guide OPEN SafetyRead the threat model →

Task dispatched→ Terminal status→ Transcript fetched→ Claim verified

0scale 1:1

Fig. 01/Satellite Relay

Authenticated MCP clients orbit the shared Hermes execution host.

Dispatch

TO A SHARED MACHINE

Poll & fetch

terminal status · transcript

Verify

decompose · confirm outcome

A client, not a colleague.

claude_code

Dispatch from anywhere

Claude Code, Codex, Ollama, Pi — any MCP-capable client sends a task over the authenticated bridge. Hermes owns the execution.

shared_machine

One shared machine

Tasks run on a shared satellite machine running the Hermes Agent. Every client orbits the same execution layer — deterministic, auditable, real.

poll_status

Poll to terminal state

Poll for status until the run reaches a terminal state, then fetch the transcript. No callbacks, no guessing — just receipts.

Claims are not proof.

Verification Shrine — Hermes returns transcript-backed evidence

The verification shrine

Loops that return evidence, not vibes.

Hermes submits a claimed outcome. Your main agent decomposes it into checkable claims and verifies each against the captured transcript.

01Build compiles on the shared compute.verified

02All integration tests pass.needs evidence

03No outbound network calls were made.rejected

Operator confidence.

hst

> hst tasks -n 4

queue visible · caller visible · gist visible

> hst costs -n 4

$0 (subscription) or unknown, never free

> hst transcript 7cb13ab6

/tmp/hermes-async-bridge-transcripts/...

Host-side observability

Watch the queue without trusting the queue.

The hst CLI is one Bun file with zero npm dependencies over the bridge SQLite state. Operators can inspect live tasks, see caller-aware cost snapshots, and export any transcript from the host without adding a service.

01Task state, caller, and short gists are visible at a glance.visible

02Cost output never turns unknown spend into a fake $0.honest

03Transcript export keeps verification tied to evidence.evidence

Operate the bridge.

Authenticated MCP switchboard

Dispatch, poll, fetch, verify.

Each coding agent plugs into the MCP bridge and routes through the same five operations. Authentication, tool mediation, and auditability sit at the patch bay — not in the client.

bridge-tools

> hermes poll --session HERMES_SESSION_ID

poll status: running → complete

transcript evidence fetched

MCP Switchboard — coding agents operate the bridge

Claims are not proof.

Hermes Satellite · remote execution & verification over MCP