no menu in choosing models in telegram. update failed
Debug report uploaded:
Report https://paste.rs/slDri
agent.log https://dpaste.com/82K2RXBS9
gateway.log https://dpaste.com/FF5YJY8LT
#no menu in choosing models in telegram. update failed
lost relic
spiral cypress
Yep, that update failure is the blocker.
The updater is trying to autostash local changes, but git replies No local changes to save, then Hermes still tries to resolve refs/stash and exits. That leaves you on the old Hermes version, so Telegram keeps using the old /model behavior.
Use a clean source checkout reinstall instead of hermes update. This should preserve your Hermes config/data because we are only moving the code checkout, not ~/.hermes/config.yaml, ~/.hermes/.env, sessions, cron jobs, skills, or logs.
Run this on the VPS:
hermes gateway stop
If that does not stop it, use:
systemctl --user stop hermes-gateway
Then run:
mv ~/.hermes/hermes-agent ~/.hermes/hermes-agent.broken-update-$(date +%Y%m%d-%H%M%S)
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
hermes version
hermes gateway restart
After hermes version shows the new build, try /model in Telegram again.
Do not delete the moved hermes-agent.broken-update-* folder until the new install is working. If the clean installer fails too, paste the full installer output.
lost relic
I fked up gille
I by mistake asked for chatgpt help and unintentionally i pasted a command which fking deleted my hermes lmao
I reinstalled it but all API key r gonr
😑
spiral cypress
oh fun!
well... time to go get new keys i guess. but yeah, you were still on 0.12.0 and had something weird going on that caused your update to break.
lost relic
So yeah its saying nothing is deleted permanently
Idk files r there
But hermes isnt getting the
Them*
I hate chatgpt
🫠
spiral cypress
ok... have you folllowed my advice above at all?
lost relic
Man i have a backup hwo do i restore backup in hermes?
spiral cypress
if not. stop what ur doing and do that
lost relic
ok... have you folllowed my advice above at all?
Not yet
I m bringing stuff back 🥺
lost relic
if not. stop what ur doing and do that
Okay
spiral cypress
because can't undelete things for you if you go off script. the first thing i wanted was for you to backup stuff.
lost relic
so its not latest yet?
spiral cypress
it probably is
lost relic
ubuntu@openclaw-server:~$ hermes update
⚕ Updating Hermes Agent...
→ Fetching updates...
✓ Already up to date!
ubuntu@openclaw-server:~$
okay cool
now help restore backup please
spiral cypress
k sec
spiral cypress
Okay, good news: v0.13.0 is installed now, so stop running hermes update for the moment. The remaining problem is just restoring the old Hermes data/keys.
Do not paste your .env contents here.
First, find where the backup has the Hermes config files:
cd ~
find ~/hermes-backup-repo -maxdepth 6 -type f \( -name ".env" -o -name "config.yaml" -o -name "auth.json" \) -print 2>/dev/null
Also check the tar backup without extracting it over anything:
tar -tzf backup-2026-05-07.tar.gz | grep -E '(^|/)(\.env|config.yaml|auth.json)$'
If that shows .env, config.yaml, or auth.json, extract the backup into a temporary folder only:
mkdir -p ~/hermes-restore-check
tar -xzf backup-2026-05-07.tar.gz -C ~/hermes-restore-check
Then find the extracted files:
find ~/hermes-restore-check -maxdepth 8 -type f \( -name ".env" -o -name "config.yaml" -o -name "auth.json" \) -print
Once you see the real paths, back up the current fresh install config first:
mkdir -p ~/hermes-current-config-backup
cp ~/.hermes/.env ~/hermes-current-config-backup/.env 2>/dev/null || true
cp ~/.hermes/config.yaml ~/hermes-current-config-backup/config.yaml 2>/dev/null || true
cp ~/.hermes/auth.json ~/hermes-current-config-backup/auth.json 2>/dev/null || true
Then copy the old files back. Replace <OLD_ENV_PATH> and <OLD_CONFIG_PATH> with the paths printed by find:
cp <OLD_ENV_PATH> ~/.hermes/.env
cp <OLD_CONFIG_PATH> ~/.hermes/config.yaml
If the backup also has auth.json, restore it too:
cp <OLD_AUTH_JSON_PATH> ~/.hermes/auth.json
Then lock down the secret files and restart:
chmod 600 ~/.hermes/.env ~/.hermes/auth.json 2>/dev/null || true
hermes gateway restart
hermes doctor
After that, test /model in Telegram again.
If you are not sure which file path is the right one, paste only the output of the find ... -print commands. Do not paste the contents of .env or auth.json.
lost relic
find ~/hermes-backup-repo -maxdepth 6 -type f \( -name ".env" -o -name "config.yaml" -o -name "auth.json" \) -print 2>/dev/null wont show anything
u sure i need to do that? i know where the file is in folder i can cd to it
spiral cypress
then that's prob just a backup of the repo and not the /.hermes folder that contains your actual data.
the repo is the agent and can be replaced with updates. the folder above it is where you store all the goodies.
like the config and .env.... these don't live in the repo
they live one dir above the repo in ~/.hermes typically
if you deleted that without a backup. then i'd start just collecting your api keys again... no fun
lost relic
i will backup
spiral cypress
out of curiosity, what did chatgpt tell you and what did you do?
spiral cypress
it's all good. just took this thread in a new direction. hehe
so yeah, at this point, if you don't have the backup of that dir above the hermes-agent repo... then you just need to walk back through the setup and put all the keys back in and probably set up something to back that up in the future so this doesnt happen again
I'll leave the thread open for a bit for any questions might have during that process, but let me know when you're back up and running and we can close this thread out as hard lessons learned.
lost relic
Done
backup cron job i made is sooo useful
It backsup my agent dailt at 3am
Thanks alooooot
spiral cypress
Awesome! Yeah. we may have some scars from this one, but at least we're learning. Glad you're back up and rrunning!