Hermes Agent adds --tui but does not enter the interface when running through pipelines or non-interactive environments, which is a normal design. TUI requires a real TTY; If stdin is occupied by pipelines, Hermes falls back to a single query pattern, which is good for scripting, but not for interactive interfaces.
Common triggers
echo 问题 | hermes --tuihermes --tui- There are no interactive terminals in CI, cron, and systemd
- Some remote execution tools do not have pseudo-tty assigned
How should it be used?
If you want to open the interface, enter hermes --tui directly in the terminal. If you want to script calls, don't expect a TUI and use a normal one-shot command or API Server instead. When remote SSH, confirm that the connection is assigned a TTY, for example, common ssh clients do so by default, but batch commands may not.
The way to do it is simple: don't use the TUI as long as the current environment doesn't allow you to move the cursor, scroll, and keep typing normally. TUI is an interactive interface, and automation tasks will be more stable through CLI/API.
