Can Hermes Agent reply to a private message in Slack but not in the channel? Start by checking events, scopes, and /invite

Hermes Agent is sending normal private messages in Slack, but the channel seems to be muted, and the official documentation clearly lists these situations: usually message.channels is not subscribed, channels:history scope is not added, or the bot is not invited to the channel at all. If any of these three are missed, channel messages may not come in.

The fastest amendment

1. Check for message.channels and app_mention in the Slack app's Event Subscriptions.
2. Confirm that the channels:history is added in OAuth & Permissions.
3. After you have changed the scopes or events, you must reinstall the app to the workspace.
4. Enter the target channel to execute /invite Hermes Agent.
5. When testing in your channel, really 提及 the bot, don't just send plain text.

Why is there no problem with private messages, but not channels?

Because Slack has two sets of access conditions for DMs and channels. DMs are more direct by default, while channels require bots to have both subscription events and historical read permissions, and they must be actually in that channel.

So don't check the model first, don't check the token first. If the private message can be replied, it means that the core link is likely not broken, and the focus is on channel events, scope, and invitation status.

Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.