Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Bug]: Slack setup doesn't work: bot never responds. [1 participants]

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…
GitHub stats
NousResearch/hermes-agent#16744•Fetched 2026-04-28 06:51:05
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
YevhDrYevhDr
Participants
YevhDrYevhDr
Timeline (top)
labeled ×4

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

cat ~/.hermes/.env
HERMES_MAX_ITERATIONS=90
SLACK_BOT_TOKEN=xoxb-5XXX
SLACK_APP_TOKEN=xapp-XXX
SLACK_ALLOWED_USERS=*
TELEGRAM_BOT_TOKEN=XXX:XXX
TELEGRAM_ALLOWED_USERS=1234566798
TELEGRAM_HOME_CHANNEL=1234566798

---

cat ~/.hermes/config.yaml 
...
whatsapp: {}
telegram:
  channel_prompts: {}
slack:
  enabled: true
  channel_prompts: {}
mattermost:
...

---

Report       https://paste.rs/CKq1A
  agent.log    https://paste.rs/DrfMr
  gateway.log  https://paste.rs/kpfLg

---
RAW_BUFFERClick to expand / collapse

Bug Description

Problem Description: Bot responds correctly in terminal and in Telegram, but does not react to messages in Slack at all.

Environment: VPS Server (Contabo) Ubuntu, systemd user service

cat ~/.hermes/.env
HERMES_MAX_ITERATIONS=90
SLACK_BOT_TOKEN=xoxb-5XXX
SLACK_APP_TOKEN=xapp-XXX
SLACK_ALLOWED_USERS=*
TELEGRAM_BOT_TOKEN=XXX:XXX
TELEGRAM_ALLOWED_USERS=1234566798
TELEGRAM_HOME_CHANNEL=1234566798
cat ~/.hermes/config.yaml 
...
whatsapp: {}
telegram:
  channel_prompts: {}
slack:
  enabled: true
  channel_prompts: {}
mattermost:
...

History Slack was configured and working for several days before. Today it stopped working after I ran "hermes update" command. Attempted full reinstall from scratch using the official install script — issue persists.

Slack API side No issues on the Slack API side — both app-token and bot-token are verified working via curl. Problem Gateway starts but logs No messaging platforms enabled and never attempts to connect Slack, even though:

SLACK_BOT_TOKEN and SLACK_APP_TOKEN are set in /root/.hermes/.env hermes setup shows Slack as (configured) gateway_state.json shows only Telegram in platforms, Slack is absent entirely

Fresh install via official install script with Slack tokens in .env Run hermes setup → Slack shows as configured Start gateway → No messaging platforms enabled Restart gateway → same result, Slack still absent from gateway_state.json

Steps to Reproduce

VPS server curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash hermes setup slack

Expected Behavior

Bot works in Slack after slack gateway setup

Actual Behavior

Bot responds correctly in terminal and in Telegram, but does not react to messages in Slack at all.

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

Slack

Debug Report

Report       https://paste.rs/CKq1A
  agent.log    https://paste.rs/DrfMr
  gateway.log  https://paste.rs/kpfLg

Operating System

Ubuntu 24.04

Python Version

3.11.15

Hermes Version

0.11.0

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

extent analysis

TL;DR

The issue is likely due to the Slack configuration not being properly loaded by the gateway, despite being set in the .env file and appearing as configured in hermes setup.

Guidance

  • Verify that the SLACK_BOT_TOKEN and SLACK_APP_TOKEN are correctly set in the .env file and that the file is being read by the gateway.
  • Check the gateway.log for any errors related to loading the Slack configuration.
  • Try manually adding the Slack configuration to the gateway_state.json file to see if the gateway will then connect to Slack.
  • Review the hermes setup process to ensure that it is correctly configuring the Slack integration.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The fact that the Slack tokens are verified working via curl and that the issue started after running hermes update suggests that the problem may be related to the update process or the way the gateway loads configurations.

Recommendation

Apply workaround: manually add the Slack configuration to the gateway_state.json file and restart the gateway to see if it resolves the issue. This will help determine if the problem is with the configuration loading process or with the gateway itself.

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…
#api#API rate limit#retriever error#indexing error#inference speed

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]: Slack setup doesn't work: bot never responds. [1 participants]