Gateway setup skips Telegram configuration and exits without prompting for required fields

[indigo garden]

Summary:
When running Hermes gateway setup and selecting Telegram, the wizard immediately skip with “Skipped (keeping current)” and then exit with “No platforms configured,” instead of prompting for the Telegram bot token, allowed user IDs, and home channel.

Observed behavior:
- Hermes gateway setup opens normally in a PTY.
- Navigating to the platform selection menu and choosing Telegram does not enter the expected Telegram prompt flow.
- The flow exits cleanly with:
  - “Skipped (keeping current)”
  - “No platforms configured. Run 'hermes gateway setup' when ready.”
- No hard crash is emitted; the issue is a premature skip/early return.

Relevant log evidence:
From ~/.hermes/logs/gateway.log:
- WARNING gateway.run: No user allowlists configured. All unauthorized users will be denied.
- WARNING gateway.run: No messaging platforms enabled.
- INFO gateway.run: Channel directory built: 0 target(s)

From ~/.hermes/logs/gateway.error.log:
- Repeated warnings:
  - No user allowlists configured. All unauthorized users will be denied. Set GATEWAY_ALLOW_ALL_USERS=true in ~/.hermes/.env to allow open access, or configure platform allowlists (e.g., TELEGRAM_ALLOWED_USERS=your_id).
  - No messaging platforms enabled.
- Shutdowns are signal-based (SIGTERM) and do not show a fatal traceback.

System environment:
- OS: macOS 26.5
- Kernel: Darwin 25.5.0
- CPU architecture reported by uname -a: x86_64
- Python: 3.10.9 from shell, Hermes reports Python 3.11.4
- Hermes Agent: v0.15.1 (2026.5.29)
- Hermes project path: /Users/alessandro/.hermes/hermes-agent

Config state before repro:
- ~/.hermes/config.yaml was reverted so Telegram is disabled and the token field is cleared.
- Relevant state includes Telegram being disabled in gateway config and no active messaging platform enabled.

[topaz python]

Thanks, this looks like the setup wizard is skipping before it actually enters the Telegram configuration flow.

The log lines about “No platforms enabled” and “No user allowlists configured” look like downstream symptoms: Telegram never got saved, so the gateway starts with no configured messaging platform.

For now, you can bypass the wizard by editing:

~/.hermes/.env

and adding these values manually:

TELEGRAM_BOT_TOKEN=your_botfather_token
TELEGRAM_ALLOWED_USERS=your_numeric_telegram_user_id
TELEGRAM_HOME_CHANNEL=your_numeric_telegram_user_id

For a Telegram DM setup, TELEGRAM_ALLOWED_USERS and TELEGRAM_HOME_CHANNEL are usually the same numeric user ID from @userinfobot.

Then try:

hermes gateway start

One thing that would help us pin the wizard bug: when you selected Telegram, did you use arrow keys + Enter, type a number, press Space, or just press Enter? Also, what terminal app were you using and what does this print?

echo $TERM

[indigo garden]

I used arrows + enter.

Now my hermes gateway setup is missing Telegram. Seems like curses/UI has removed it even though I've removed all tokens and put telegram disabled in config.yaml. Hermes itself could not find the source issue why Telegram is missing now from the setup UI.

[topaz python]

Telegram should not disappear from hermes gateway setup just because the token was removed or Telegram is disabled in config; it is still in the built-in platform list.

First run:

cd /Users/alessandro/.hermes/hermes-agent

Then run this and paste the output:

./venv/bin/python -c "from hermes_cli.gateway import _all_platforms; print([p['key'] for p in _all_platforms()]); import hermes_cli.gateway as g; print(g.__file__)"

Also please paste the exact command you are running to open setup, since hermes gateway setup and the broader setup wizard use different selection flows.

[indigo garden]

['telegram', 'slack', 'matrix', 'mattermost', 'whatsapp', 'signal', 'email', 'sms', 'dingtalk', 'feishu', 'wecom', 'wecom_callback', 'weixin', 'bluebubbles', 'qqbot', 'yuanbao', 'discord', 'google_chat', 'irc', 'line', 'ntfy', 'simplex', 'teams']

Yup. Hermes (gpt-5.4-mini) tells me telegram is indeed present but its not being rendered in the setup UI.

[topaz python]

what are you running and what does it look like? this is hermes gateway setup on current main. also, you mentioned adding disabled to your config. What is your goal? Setting up telegram or disabling it? have you tried what I recommended by adding the key values manually? Removing the keys and setting it disabled is the opposite direction. I'm confused on what your desired outcome is from this.

are you having 5.4 mini run this stuff? if so, please run /quit and do this manually

[topaz python]

Please do this one manually outside Hermes: run /quit if you are having Hermes run commands for you, then in your terminal run cd /Users/alessandro/.hermes/hermes-agent and hermes gateway setup yourself.

Telegram is present in the built-in platform list; your _all_platforms() output confirms that. If the manual setup UI still does not show Telegram, please paste the exact command you ran, your terminal app, echo $TERM, and a screenshot or text capture of the platform menu.

If your goal is to set up Telegram, do not keep platforms.telegram.enabled: false as the test state. Either use the manual .env workaround from above (TELEGRAM_BOT_TOKEN, TELEGRAM_ALLOWED_USERS, TELEGRAM_HOME_CHANNEL) or let the setup prompts write those values.

[indigo garden]

Sorry for the delay! And thanks a lot for your support! I will do and reply with info!

[indigo garden]

Hey. Thank you very much for all the support! Hardcoding the envs did the trick.
I hope my first post help the improvement of the fast config for Mac OS machines (if that is the problem) so config doens't bypass the gateway config for Telegram
Cheers!