Hermes on Telegram
The operator configures one shared Hermes bot. Link your own Telegram account once so direct messages use this Keycloak account's isolated Hermes tenant.
After linking, you can send text or photos for analysis. Images Hermes creates or revises are returned directly in the same private chat.
Account-link commands go only to the private chat with the Hermes bot—not to Hermes WebUI and not to BotFather.
Checking Telegram…
Activate the shared bot (operator, once)
- Open @BotFather and send
/newbot. - Choose the bot's display name and a username ending in
bot, then copy the token BotFather returns. - On a trusted administrator computer with the Vault CLI, sign in to Atlas Vault and store the token at
kv/atlas/hermes/chat-telegramunderbot_token.
export VAULT_ADDR=https://secret.bstein.dev vault login -method=oidc vault kv patch -mount=kv atlas/hermes/chat-telegram bot_token='<BOTFATHER_TOKEN>'
vault kv patch changes only bot_token, so it preserves the existing relay_key. Do not paste the token into Hermes, a browser form, Git, or a message.
After the token is saved, ask the Hermes operator to apply the tracked router rollout. Then return here: the account-link button will appear and each Keycloak user can privately link their own Telegram account.
Codes expire after 10 minutes. Only direct messages are accepted; group messages are ignored.