When the Hermes Agent connects to Signal, it essentially makes the signal-cli work as a linked device. The official documentation gives a clear direction: prepare the Signal number and signal-cli runtime environment first, and then do the link, allowlist and home channel configuration.
Basic steps
- Install and confirm that the
signal-cliis functioning properly on the machine. - To connect Hermes to Signal according to the documentation, the common practice is to register Hermes as a linked device.
- In
~/.hermes/.envwithSIGNAL_PHONE_NUMBER,SIGNAL_ALLOWED_USERS,SIGNAL_HOME_CHANNEL. - Perform
hermes gateway installandhermes gateway startto keep the gateway online for a long time. - Use your mobile phone to send a message to the bot to confirm that the sending and receiving are normal.
Why a lot of people get stuck here
It's not that Hermes has complex logic, but that the Signal environment is heavily dependent. When Cannot reach signal-cli, daemon is not online, and messages are not coming in, check Java 17, signal-cli daemon, port 8080, and service status first. When you don't speak in a group chat, check if SIGNAL_GROUP_ALLOWED_USERS is configured.
In a word: The core of Signal is not to tune prompts, but to first configure signal-cli, allow users, and long-running gateway services.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.