Signals

2026-10-24 / Hermes Agent

Hermes keeps classic CLI work running after terminal detach

Edited by Michael Ruescher

Stable Hermes 0.22.5's classic chat, chat -q and top-level -z paths attach to gateway-owned execution. EOF or detach leaves the job running; an explicit remote failure does not silently start a local agent. Released revocation repairs synchronize saved allowlist removals with cached permanent allows and check disabled plugins on HTTP requests, new websocket handshakes and other served paths.

What this changes for operators

  • CLI wrapper and bot operators: use stable 0.22.5, follow the persisted session identity and completion status, and stop treating terminal exit as cancellation. A continuing gateway can replace a wrapper kept alive only to supervise the chat process.
  • Configure agent.run_budget_seconds rather than --run-budget on this path; -z does not itself bypass approvals. Use the documented alternative surfaces for unsupported worktree and image invocations. Record the serving gateway, home and profile alongside the client version.
  • Detach from a harmless job, reconnect, cancel it deliberately and remove a saved permanent allow. Separately disable a plugin, then test HTTP requests and new websocket handshakes under each served profile. These checks do not establish termination of an already-open socket. Completion and refusal traces would settle the deployed lifetime and consent behavior. Saved terminal supervision may become gateway administration; no net orchestration saving was measured.

Signal metadata

Source findings

Featured in

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-24-hermes-agent-gateway-work-outlives-terminal

Research evidence and publication history are open in the repository.