Update Hermes Agent with Snapshots and Rollback

A Hermes update can change code, dependencies, configuration, and a running gateway in one operation. Treat it as a small release: preview the change, protect state, update, and prove the agent still works.

Operating checklist

Run hermes update --check before modifying files.
Confirm the active profile and HERMES_HOME.
Inspect unexpected local source changes.
Use hermes update --backup on high-value systems.
Plan a short gateway interruption.
Retain the snapshot until validation passes.

How the workflow works

hermes update normally creates a quick state snapshot, pulls the selected branch, validates critical startup files, installs changed dependencies, offers configuration migration, and refreshes running gateways. A syntax failure in critical startup code triggers a return to the pre-pull commit. Use --branch <name> only for an intentional QA or release-candidate channel. For unattended updates, keep the default policy that stashes and restores local edits unless the machine is explicitly managed as a clean, disposable checkout.

Common pitfalls

Skipping the preview and discovering a branch change during maintenance.
Assuming a successful pull proves provider, config, and gateway health.
Forcing Windows updates while Desktop or a gateway locks the environment.
Ignoring a dirty tree restored on top of the new version.

Verification steps

Run hermes doctor and resolve new findings.
Run hermes version and confirm the intended build.
Complete a normal chat and one harmless tool call.
Check hermes gateway status and send a controlled test message.
Keep the snapshot through the next normal operating cycle.

Use the official Hermes documentation for the current source of truth.