v0.23.2

Hermes Agent v0.23.2


Overview

v0.23.2 — The Rollup Tag. Released November 16, 2026. Since v0.23.1: ~1,989 merged PRs · 7,918 non-merge commits · 5,211 changed files (+239,733 / −22,788) · 940 closed issues, measured at commit ae2a81ccc00.

This is not a feature release. It is a stable tag that rolls the window up for the GitHub release (CLI and installers), the Microsoft Store app, Docker and Hermes Cloud. The notes are explicit about the rest: most of what landed in this window is undocumented here on purpose, and the full curated notes ship with v0.24.0, covering everything from v0.23.0 onward — nothing in the window is skipped.

So this page does two things: it states the fixes the release documents, and it pulls out four capabilities from the window that the notes only mention in passing but that are verifiable in the code.


Highlights

1. Settings ▸ Backup & Transfer on the desktop

Settings has a new built-in section (not a plugin), right after Sessions, with the deep link /settings?tab=backup. Two cards:

  • Back up this agent runs hermes backup and hands you a zip containing every profile, settings, memory, skills, schedules, chats, .env and auth.json.
  • Transfer to Hermes Cloud installs that backup into a cloud agent you pick, using an ordinary hermes backup plus hermes import --keep-host — there is no separate migration format.

The safety design is the story here: the target agent is fully backed up first as the undo point; the confirm panel requires ticking “I understand this replaces <agent>”; and a restore that fails part-way names the files it could not restore and offers Undo (back to before the transfer) and Retry. The transfer passes --messaging-off, so messaging bots in the backup arrive switched off and the machine they came from keeps answering — two machines cannot fight over one bot token.

2. hermes fallback check

Your fallback chain can now be examined without starting an agent session. By default the check is static: whether each provider is known, whether usable credentials exist, and what endpoint and wire protocol the entry resolves to. With --live it sends one minimal request per statically ready entry (Reply with exactly: OK, at most 512 tokens, SDK retries disabled, entries probed in parallel), which catches exhausted quota, retired models, 502s behind an endpoint, and the quiet substitution where a provider answers with a different model than the one you asked for.

Any entry that is not ready makes the command exit 1, so cron and CI can gate on it. --json gives structured output, with credentials redacted from error text.

3. Durable subagents and automatic resume

Every subagent keeps a row in the profile’s state.db (the resumable_subagents table): start, heartbeat checkpoints, the stop reason, and a recovery marker when the owning process died. A child that did not complete and was not stopped by a person keeps its worktree pinned for 48 hours by default (delegation.resumable_ttl_hours), for at most 32 records per profile (delegation.max_resumable).

The record’s resume_mode says what kind of resumable it is: AUTO_AT (limited, wait for the reset), AUTO_ON_BOOT (gateway shutdown or hard kill), ON_FIX (credits, auth, model access), REPAIR_THEN_CONTINUE (the transcript or a request part needs repair), HANDOFF (a safety refusal; use another model). Continue by hand with delegate_task(action='continue'), or opt in to delegation.auto_resume (default off) and let the gateway resume due children every 15 seconds.

4. Per-job cron delivery switches

wrap_response can now be overridden per job: --wrap-response / --no-wrap-response / --inherit-wrap-response force the Cronjob Response: <name> header and the closing note on, force them off, or delete the override so the job follows the global cron.wrap_response again.

Combined with continuable delivery (--attach-to-session, or global cron.mirror_delivery), a brief becomes a conversation you can reply into; a job created inside a Telegram topic can get a fresh thread per run with platforms.telegram.extra.cron_fresh_thread_per_run: true. The same release makes catch_up, grace_minutes and timezone per-job settings.

Fixed in the Release Candidate

  • Desktop chats created by an August build with a bare custom provider can send again after updating (#156545).
  • A Desktop or TUI reply that streamed beside a todo or memory call now settles instead of leaving the Stop button up (#156553).
  • A crash mid-stream on Telegram and other edit-streaming chats no longer shows a duplicate “Recovered reply”; a word holding a key prefix mid-word (program_id) is shown on time again (#156546).
  • Desktop no longer loses or scrambles what you type while it starts and resumes your last chat (#156615, #156642).
  • After a reconnect mid-reply, Desktop shows the reply once and in full, attachments included (#156611).
  • In the Webapp, opening Hermes Cloud agents while this install is not signed in to Nous Portal now tells you to sign in to Nous Portal instead of sending you to the Webapp login (#156652).
  • Exiting the CLI while its startup update check is waiting on GitHub no longer leaves git running (#156616).

Also in This Window

The notes list these in one paragraph (the curated v0.24.0 notes will document them): durable subagents that survive a gateway restart or crash and can be continued on their own conversation, one prompt-cache clock per session, hermes fallback check, hermes update --force to stop gateways at once instead of draining, one-time browser_vault codes entered from Telegram and Discord, opt-in shared Telegram DM threads, the Gemini Interactions API by default for Gemini 3 and later plus Gemini 4 Carbon, fast mode for Claude Mythos 5.2, per-job cron options (wrap_response, a fresh thread per run), new plugin APIs (ctx.fork_session, ctx.redact_text(), ctx.register_idle_task), compatibility shims so updates work across module moves, a slimmer macOS bundle that installs Chromium on first use, and a large batch of new plugin-catalog entries.

Upgrade

  • Microsoft Store app: updates through the Store.
  • Desktop installed from the installer (.exe / .dmg): no change in this release; it updates with the next bundled release.
  • CLI: hermes update, or re-run the installer one-liner.
  • Docker / Hermes Cloud: nousresearch/hermes-agent:stable (or :latest).

Full changelog: v0.23.1…v0.23.2

← Hermes Agent Changelog