vestal rose
In fact at that point I can't really input anything
#Can't confirm ([o]nce | [s]ession | [a]lways | [d]eny) in ssh to hermes host
woeful tinsel
eh... you pasted a screengrab of your firecrawl key... please read https://discord.com/channels/1053877538025386074/1496283715083567256 and please go revoke that key and make a new one.
Yes, this is a real bug, and your screenshot matches it very closely.
What’s happening there is Hermes is falling back to the old text approval prompt:
[o]nce | [s]ession | [a]lways | [d]eny
but in the classic CLI that fallback can become effectively unusable, especially over SSH. The result is exactly what you described: keypresses do nothing, Ctrl+C doesn’t help, and it eventually times out and denies the command.
There is already a fix for this in the codebase. The classic CLI approval callback was being registered on the wrong thread, so the agent thread couldn’t see it and dropped back to the broken stdin/input path. That was fixed on 2026-04-21.
So the right move here is:
update Hermes first
If you update and still see the plain [o]nce | [s]ession ... prompt in classic CLI, that means you’re still hitting the wrong path and we’d want your exact:
hermes --version
One extra detail: on the fixed prompt_toolkit approval UI, the normal interaction is arrow keys or number keys plus Enter, not literal o/s/a/d letter input. But your screenshot is not the fixed UI anyway, so the main thing is updating to pick up the approval-thread fix.