[Bug]: Bots in a room (group chat) hang on 'thinking' then report 'out of Nous credits' — bots don't use Nous and work fine in DMs

### Bug Description When we attempt to use a **room** (group chat) with our bots, nothing happens. One of the bots just shows as "thinking" and never responds. Then, immediately, we get a message saying we are **out of Nous credits**. The problem: **our bots do not use Nous for credits at all.** No Nous API key is configured on our Hermes instance — the bots run on their own configured providers (Ollama Cloud, Grok, etc.). The bots work perfectly fine via **DM**, but refuse to work via a **room**. This looks like the room/group-chat path is routing the bot's messages to the wrong provider (Nous / the default provider) instead of the bot's configured provider, and the "out of Nous credits" error is a misleading symptom of that misrouting. ### Steps to Reproduce 1. Run the latest version of Hermes Desktop, connected to our remote Hermes instance (latest Hermes Agent, v0.20.4). 2. Create/join a room (group chat) that includes our bots. 3. Send a message to the room. 4. Observe: nothing happens — one bot shows as "thinking" and never produces a response. 5. Immediately after, we receive a message that we are out of Nous credits. ### Expected Behavior - Bots in a room should respond using their own configured providers, exactly as they do in DMs. - No Nous credit error should appear, since the bots do not use Nous. ### Actual Behavior - Room messages are silently dropped / the bot hangs in a "thinking" state. - A spurious "out of Nous credits" message is delivered, even though no Nous API key is configured and the bots use other providers. - The same bots respond correctly in DMs. ### Affected Component - Gateway (Telegram/Discord/Slack/WhatsApp) - Agent Core (conversation loop, context compression, memory) ### Messaging Platform (if gateway-related) - Discord ### Debug Report Debug report not uploaded (would publish personal data). Happy to provide `hermes debug share` output on request. Local dump summary: - Hermes Agent v0.20.4 (2026.8.18), git install - Python 3.12.13, OpenAI SDK 2.24.0 - OS: Linux 6.8.0-137-generic x86_64 (remote host) - Gateway: running, platform: discord - `nous` API key: **not set** (bots use ollama-cloud / grok / other providers) - Accessing via Hermes Desktop (latest) against the remote Hermes instance ### Operating System Linux 6.8.0-137-generic x86_64 (remote Hermes host); Hermes Desktop (latest) on the client side ### Python Version 3.12.13 ### Hermes Version v0.20.4 (2026.8.18) ### Additional Logs / Traceback (optional) N/A yet — can provide on request. ### Root Cause Analysis (optional) Hypothesis: the room/group-chat message path in Bot Mode does not carry the bot's per-profile provider configuration, so the message falls through to the default/Nous provider. Since no Nous key is configured, the gateway surfaces the "out of Nous credits" error instead of the real misconfiguration. This is consistent with the bot working in DMs (where the per-bot provider is honored) but failing in rooms. ### Proposed Fix (optional) Ensure room/group-chat messages are dispatched with the bot's own profile/provider configuration (same path as DMs), and never fall back to the Nous provider for bots that have an explicit provider configured. The credit error should only be shown when the provider actually being used is Nous. ### Are you willing to submit a PR for this? - [ ] I'd like to fix this myself and submit a PR