Hermes starts packaging computer-use work as a durable runtime, not a one-off browser trick
Hermes PR #24065 adds a persistent Computer runtime with run.json, events.jsonl, artifact directories, and a computer tool for start, schedule, list, get, events, and cancel actions. The same fresh workstream matters because it addresses the boring failure modes that decide whether computer-use can run unattended: PR #24045 saves user messages hit by 429/529 rate limits into a dead-letter queue with /queued retry; PR #24064 stops headed browser sessions from being killed after every turn; and PR #24071 tightens hardline approval blocking for quoted catastrophic rm targets such as "/", "/var", and "$HOME" paths. Issue #24067 also shows the gateway side still needs restart hygiene on macOS, where stale PID locks can make Telegram, Feishu, and WeChat look already in use after a crash.
Computer-use demos are easy; durable computer-use operations are not. A useful agent has to keep enough state to resume or audit work, avoid losing user requests during provider throttling, keep a visible browser alive when human intervention is needed, and refuse destructive commands even when shell quoting is used to dodge simple pattern checks. This cluster is therefore more important than another UI tweak, even though most pieces are still PR-level work.
- PR #24065 adds persistent Computer runtime state, artifact directories, and a computer tool with start/schedule/list/get/events/cancel actions
- PR #24045 persists rate-limited messages to ~/.hermes/dead_letter_queue.json and adds /queued list/retry/clear commands
- PR #24064 keeps headed browser sessions alive between turns when AGENT_BROWSER_HEADED or browser.headed is configured
- PR #24071 extends hardline approval rules to quoted protected rm targets and adds regression tests against yolo-style bypass paths
- Issue #24067 documents macOS stale PID locks causing gateway restarts to leave Telegram, Feishu, and WeChat unable to connect
- The runtime and guardrail changes are open PRs, not a tagged Hermes release
- Background completion reconciliation for the Computer runtime is explicitly left for follow-up work
- Dead-letter queues help avoid lost messages but can replay stale intent if operators retry without checking context
- Approval regexes reduce one bypass class but do not replace sandboxing and operator review for shell access