Hermes "No module named 'hermes_cli'" after update
This means hermes update failed mid Git pull and corrupted the repo, leaving the venv broken - even re-running install.sh fails with a fatal 'bad object' error because the objects can't self-repair. Back up config.yaml and MEMORY.md, delete ~/.hermes/hermes-agent, then re-run the official installer for a clean checkout and restore your config.
Likely cause
hermes update failed mid Git pull and corrupted the repo, leaving the virtualenv broken. Even re-running install.sh fails with a fatal 'bad object' Git error, because the local objects are corrupted and can't self-repair.
The fix
- 1 Back up config.yaml and MEMORY.md first.
- 2 Delete the corrupted install: rm -rf ~/.hermes/hermes-agent.
- 3 Re-run the official install script for a clean checkout, then restore your config.
rm -rf ~/.hermes/hermes-agentHit a different error?
Paste any agent error and get the cause and fix in seconds.
Frequently asked questions
Can't I just run hermes update again to fix it?
No. Once the Git objects are corrupted the repo can't self-repair, so update and install.sh both fail with 'bad object'. A clean delete-and-reinstall is the only reliable fix.
Will I lose my config and memory?
Not if you back them up first. config.yaml and MEMORY.md live in ~/.hermes - copy them somewhere safe before deleting hermes-agent, then drop them back after the clean reinstall.
How do I stop this happening on the next update?
Run updates when the machine is stable (not low on disk, not mid-reboot) so the Git pull completes. If an update is interrupted, reinstall cleanly rather than retrying on a half-pulled repo.
Stop firefighting agent errors
Decoding errors one at a time is the manual version of what BetterClaw automates. Run your OpenClaw agents hosted with managed models, retries and config validation built in.
$19/month per agent · BYOK · 7-day money-back guarantee