[Bug]: Telegram Bot not responding at all

[tanaymeh]

Bug Description

I have setup Hermes locally with Telegram, created a bot and followed all the instructions but the bot doesn't respond at all.

No matter how many messages or commands I send. I have created multiple new bots, pasted their tokens with great care but it just doesn't respond. Also ran setup multiple time and restarted the service along with my system.

If I send >1 messages in succession, it shows [Telegram] ⚡ New message while session XYZ is active - triggering interrupt but doesn't do anything else.

Steps to Reproduce

Normal setup

Expected Behavior

Bot should respond in Telegram

Actual Behavior

Bot doesn't respond

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

Telegram

Operating System

Zorin OS 18 x86_64

Python Version

3.11.14

Hermes Version

1.0.0

Relevant Logs / Traceback

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR

[ikari-pl]

does it work locally in CLI for you? Because for me, a fresh hermes install throws a 400 on every request to hermesresearch, saying it is missing the model name

[fartboner]

Same as #849

[kshitijk4poor]

Fix submitted in #856. The setup wizard was dropping provider/model metadata on final save, which could leave fresh Nous installs misconfigured after setup; the PR preserves that config and adds regression coverage for the affected setup flows.

[tanaymeh]

does it work locally in CLI for you? Because for me, a fresh hermes install throws a 400 on every request to hermesresearch, saying it is missing the model name

@ikari-pl Yes, CLI works for me, just Telegram doesn't.

[sobricius]

does it work locally in CLI for you? Because for me, a fresh hermes install throws a 400 on every request to hermesresearch, saying it is missing the model name

@ikari-pl Yes, CLI works for me, just Telegram doesn't.

Same for me

[teknium1]

Fixed in PR #856 (merged as 4525933). The root cause was the setup wizard's in-memory config dict getting stale after _update_config_for_provider() wrote directly to disk — the final save_config() call would overwrite the provider metadata (model.provider, model.base_url), leaving fresh installs misconfigured.

If you're hitting this now, re-running hermes setup with the latest version should fix it.