Zouroboros Swarm Executor Bridge for Hermes

How to use

This layer isn't for people happy with Hermes as their primary agent; it suits those who want:

A higher-level orchestrator making routing decisions across multiple coding CLIs.

Cost-sensitive routing — trivial work on cheap local models, hard work on Claude Opus or equivalent.

Cascade failover — executor A fails, the swarm reroutes to B automatically.

Third-party ecosystem project: not Nous Research, not Fly, not Anthropic. Evaluate the orchestrator code before running it against real workloads.

The executor bridges repo is archived. Don't start from the archived standalone repo — the active code path is in the Zouroboros monorepo.

What It Does

Input:   bash hermes-bridge.sh "prompt" [workdir]
Output:  plain text on stdout
Errors:  stderr + non-zero exit code

The original standalone marlandoj/zouroboros-swarm-executors repo is archived; the code has migrated to the Zouroboros monorepo under packages/swarm/src/executor/. Use the monorepo for new installs.

1. Install Zouroboros:

   git clone https://github.com/marlandoj/zouroboros.git
   cd zouroboros
   pnpm install
   pnpm run build
   zouroboros init
   zouroboros doctor    # checks executor availability

2. Ensure Hermes is installed and on your PATH. The bridge shells out to hermes directly; no extra config on the Hermes side is required for basic use.
3. Test the Hermes bridge in isolation:

   bash packages/swarm/src/executor/bridges/hermes-bridge.sh \
     "write a hello world in python" \
     /tmp/hermes-test

4. Register Hermes with the orchestrator via its executor registry. The orchestrator reads registry/executor-registry.json (or the monorepo equivalent) to know which executors are available and their capabilities.

If you're running a single-agent workflow, use Hermes directly and skip this layer.

Links

• Paperclip adapter