The earlier setup assumed Hermes workers and does not fit external OMP/Cloudflare agents. Hermes documents external Kanban lanes as integration work; its MCP guide recommends MCP or a narrow native tool for connecting external systems.

The operator clarified that the workers are external runtimes: OMP over ACP or Durable Agents in Cloudflare. My proposed planner/coder/reviewer Hermes profiles did not match that architecture.

Hermes' worker-lane reference explicitly says a non-Hermes CLI lane is not yet a paved path. Launching, mapping workspaces and reporting lifecycle outcomes remain integration work; a pluggable spawn function is not a ready OMP or Cloudflare connector.

Hermes' MCP guide recommends MCP for local or remote systems behind an RPC interface, and a narrow native tool when that is simpler. This provides an extension point for an external-agent control interface, not the implementation of that interface.

The earlier inherited-toolset explanation concerns tools exposed by Hermes child instances. It must not be used to infer the permissions of an independently configured external worker.

Sources: External Kanban worker lanes, When to use MCP.