hermes - 💡(How to fix) Fix [Bug]: Discord gateway adapter not registered/discovered for non-default profile

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

set -a
source ~/.hermes/profiles/newprofile/.env
set +a

---

WARNING gateway.run: No adapter available for discord

---

┌─────────────────────────────────────────────────────────┐
│           ⚕ Hermes Gateway Starting...├─────────────────────────────────────────────────────────┤
Messaging platforms + cron scheduler                    │
Press Ctrl+C to stop                                   │
└─────────────────────────────────────────────────────────┘

WARNING gateway.run: No adapter available for discord
WARNING gateway.run: No adapter could be created for any of the 1 configured platform(s). 
Check that required dependencies are installed and credentials are set. Gateway will continue for cron job execution.

---

Report       https://paste.rs/PHZk9
  agent.log    https://paste.rs/qLAwJ
  gateway.log  https://paste.rs/XNQpB

---
RAW_BUFFERClick to expand / collapse

Bug Description

After updating to the newest commit via hermes update, the default profile is accessible from discord, but a non-default profile's discord gateway does not work.

I've seen https://github.com/NousResearch/hermes-agent/issues/34511 and the behavior is similar:

  • discord bot appears online, but does not reply to messages
  • does not reply in channels and threads
  • hermes -p newprofile setup gateway does not list Discord as an available platform
  • log shows No adapter available for discord

Steps to Reproduce

Might need to have a different profile created before updated to 0.15.1

  1. Update Hermes from PyPI using pipx.
  2. Confirm version is hermes-agent 0.15.1.
  3. Have an existing Discord gateway configuration with DISCORD_BOT_TOKEN configured in a profile other than default: ~/.hermes/profiles/newprofile/.env.
  4. Stop the gateway service
  5. Load the Hermes environment manually:
set -a
source ~/.hermes/profiles/newprofile/.env
set +a
  1. Confirm the Discord token exists in the shell.
  2. Run the gateway manually: hermes gateway run
  3. Observe:
WARNING gateway.run: No adapter available for discord
  1. Also run the below and see that Discord is not listed as an available messaging platform: hermes setup gateway

Expected Behavior

Since:

  • DISCORD_BOT_TOKEN is configured
  • Discord dependencies are installed
  • plugins.platforms.discord.adapter imports successfully
  • DISCORD_AVAILABLE=True

Hermes should discover/register the Discord adapter and connect the Discord gateway.

hermes setup gateway should list Discord as an available platform.

hermes gateway run should create the Discord adapter and bring the bot online.

Actual Behavior

Running the gateway manually with the environment loaded.

Output:

┌─────────────────────────────────────────────────────────┐
│           ⚕ Hermes Gateway Starting...                 │
├─────────────────────────────────────────────────────────┤
│  Messaging platforms + cron scheduler                    │
│  Press Ctrl+C to stop                                   │
└─────────────────────────────────────────────────────────┘

WARNING gateway.run: No adapter available for discord
WARNING gateway.run: No adapter could be created for any of the 1 configured platform(s). 
Check that required dependencies are installed and credentials are set. Gateway will continue for cron job execution.

The same warning appears in the systemd user service logs.

hermes setup gateway also does not list Discord as an available platform.

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

Discord

Debug Report

Report       https://paste.rs/PHZk9
  agent.log    https://paste.rs/qLAwJ
  gateway.log  https://paste.rs/XNQpB

Operating System

Ubuntu 26.04

Python Version

3.11.15

Hermes Version

0.15.1

Additional Logs / Traceback (optional)

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

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Bug]: Discord gateway adapter not registered/discovered for non-default profile