#TUI Broke
1 messages · Page 1 of 1 (latest)
cc @silver hound
That CPR warning usually means the terminal/SSH layer is not answering cursor-position requests correctly. By itself that warning is not always fatal, but Enter doing nothing means Hermes is probably not receiving normal key input from that terminal session.
Please try one clean repro from a normal terminal first, ideally Windows Terminal or a direct VS Code integrated terminal, not Git Bash over SSH:
hermes update
hermes --tui
If Enter still does nothing, please send:
hermes debug share
and also paste the output of:
echo "$TERM"
echo "$TERM_PROGRAM"
stty -a
Also please confirm the exact command you launched with: hermes, hermes --tui, or HERMES_TUI=1 hermes.
For now, I would avoid Git Bash-over-SSH for the TUI test. That path often changes terminal/input behavior enough that interactive TUIs can break even when the remote Hermes install is fine.
I believe this should help address this: https://github.com/NousResearch/hermes-agent/pull/20896
I solved it: had to do with a docker create hermes chat and docker start on two separate calls - might be user error versus just doing a single docker run command