A file snippet for ~/.hermes/.env that keeps the Hermes gateway on deny by default and lets in only your own accounts, with the steps to test it.
You are connecting Hermes to Telegram, Discord, Slack or WhatsApp and want to be sure a stranger who finds your bot cannot use it. Saves about 15 minutes
[TELEGRAM_ID] | e.g. 123456789 (numeric user ID, not your @username) |
[DISCORD_ID] | e.g. 111222333444555666 (turn on Developer Mode, then right-click your name and copy your user ID) |
[SLACK_ID] | e.g. U01ABC123 (your member ID, shown in your Slack profile) |
[WHATSAPP_NUMBER] | e.g. 15551234567 (country code first, digits only) |
Use IDs, not usernames. A Telegram @username can be changed or taken over; the numeric ID stays with your account.
Using email instead? Add EMAIL_ALLOWED_USERS with your own addresses, comma-separated, or enter them when hermes gateway setup asks for allowed senders. The docs require a dedicated mailbox for Hermes, so never connect your personal one.
Written for Hermes Agent v0.21.x. Check commands against your version with hermes --version. This site is independent and not affiliated with Nous Research.
Get the Hermes Starter Pack: 15 recipes for setup, SOUL.md, memory, skills, scheduled jobs, Telegram and approvals.
More free recipes: Set Up Telegram With Hermes Safely · Use the Email Gateway for Forwarded Messages
Need the whole set? The Hermes Agent Cookbook has 100 recipes for $27.