Hermes v0.13 turns Kanban into the main durability story
Hermes Agent v0.13.0, “The Tenacity Release”, makes a bigger claim than a normal patch: Kanban is now positioned as a durable multi-agent board with heartbeats, reclaim, zombie detection, auto-block on incomplete exit, per-task retries, and hallucination recovery. The release also adds /goal target-locking across turns, Checkpoints v2 pruning, Gateway auto-resume after restart, cron no_agent watchdog mode, Google Chat as a 20th platform, pluggable providers, seven i18n locales, and security-default changes including redaction on by default.
The release shifts Hermes from “has a Kanban feature” toward “uses Kanban as the durable execution layer”. That is strategically important, but it also touches persistence, recovery, channel security, providers, and platform routing—the exact areas that decide whether an agent can safely keep working unattended.
- Official GitHub release v2026.5.7 / Hermes Agent v0.13.0 published 2026-05-07 16:23 UTC
- Release notes report 864 commits, 588 merged PRs, 829 files changed, 282 issues closed including 13 P0 and 36 P1, and 295 community contributors since v0.12.0
- Highlights include durable multi-agent Kanban, /goal target locking, Checkpoints v2, Gateway auto-resume after restart, cron no_agent watchdog mode, Google Chat support, pluggable providers, i18n, and security-default changes
- The release is broad, so operators should expect integration edge cases rather than treating it as a narrow fix
- Kanban, checkpoint, Gateway, cron, provider, and channel-auth paths all deserve smoke tests in the same environment where Hermes will run
- Some fresh post-release PRs are already touching Kanban triage, cron fan-out, TTS captions, and MCP channel listing, so v0.13 should be monitored closely during the first day