Slack

5.3. Slack — Sessions per Thread, Not per User

The core difference from Telegram/Discord

This is the most important thing about Slack in the Hermes ecosystem: Slack sessions are keyed by thread, not by user — meaning multiple people participating in the same thread share one conversation context, exactly opposite to the default “one session per person” behavior on the other platforms.

The “is thinking…” status — can be annoying

Slack displays an “is thinking…” status via the Assistant API while the agent is processing — some users find it annoying because it also temporarily locks the message composition box while it is displayed. Turn it off via configuration:

gateway:
  platforms:
    slack:
      typing_indicator: false

Notes

• If you need a group conversation that shares one context (for example, a team brainstorming with the agent together), choose Slack over Discord/Telegram — it is the only platform that supports this session style out of the box without special configuration.
• Turn off typing_indicator if the team finds the “is thinking…” status annoying — this only affects the display, not message sending or any other functionality.
• For multi-OAuth workspaces (multiple Slack teams sharing one bot), note that the gateway tracks permissions separately per workspace — permissions on one workspace do not automatically apply to another.