During installation you were prompted for the Chatto connection details, and
your answers were written to ~/.hermes/.env. Next steps: review that
configuration, restart the gateway so the bot comes online, then bring it into
a room and try it out.
Review your ~/.hermes/.env or config.yaml. Secrets (passwords, tokens)
belong in ~/.hermes/.env only — never in config.yaml; non-secret settings
can live in either file. Environment variables take precedence over
config.yaml entries.
Make sure either an existing bearer token:
CHATTO_TOKEN=your-token
…or login plus password is set:
CHATTO_LOGIN=your-username
CHATTO_PASSWORD=your-password
Without CHATTO_BASE_URL the plugin connects to the public ChattoHQ server
(https://chat.chatto.run). To use your own server:
CHATTO_BASE_URL=https://chat.example.com
Where cron job output and notifications get delivered when there is no
conversation context to reply into — the default outbound target, nothing
more. With CHATTO_RESPOND_ROOMS set, list it too if the bot should also
converse there. If unset (the usual case — the installer only asks when
you enter one), the first joined room is used:
CHATTO_HOME_CHANNEL=ROOM_ID_HERE
The bot comes online here — the steps below need it running:
hermes gateway restart
The bot sees only rooms its account has joined — membership lives on the Chatto server, survives gateway restarts, and nothing is joined silently on startup. Invite the bot account natively in Chatto, or DM it:
/join ROOM_ID_HERE
Send any message in a room the bot has joined. By default it answers every
room message; only with CHATTO_REQUIRE_MENTION=true do channel-kind rooms
wait for an @mention (group rooms and DMs answer regardless).
Editing works as a correction: fix a typo in your sent message within
5 minutes and Hermes restarts his answer with the corrected text. If he had
ignored the message because an @mention was missing, editing the mention
in makes him answer after all.