Hermes Agent’s Slack integration is designed to provide an efficient, isolated, and customizable interaction environment. To precisely summon the AI in a multi-person collaboration channel without disturbing others, it’s essential to understand its interaction logic and configuration options.

Core Interaction Rules

1. Explicit Invocation (@mention)

In Slack channels, Hermes defaults to a “passive response” mode. Plain text messages are ignored — you must explicitly invoke the bot with an @mention (e.g. @Hermes).

This design prevents the AI from causing unnecessary noise in high-traffic discussion channels, ensuring it only joins a conversation when a user explicitly needs it.

2. Threads as Context Isolation Units

Slack Threads are the core mechanism Hermes uses to manage context:

• Context inheritance: when you @mention Hermes inside an existing thread, it inherits that thread’s history and replies within it.
• Independent sessions: context is completely isolated between different threads.
• Parallel users: even in the same channel, different users’ conversation histories with Hermes stay separate, as long as each happens in its own thread.

High-Frequency Usage Tips

Task Isolation: One Task per Thread

To avoid context confusion, the most effective practice is binding each independent task to its own thread.

• Workflow:

1. Start a new task → create a new message and @mention Hermes → open a new thread.
2. Follow up or iterate → reply within that thread.

• Advantage: when you need to handle multiple tasks in parallel (e.g. doing “code review” and “document writing” at the same time), you can switch contexts quickly by switching threads, without re-explaining background to the AI.

Structured First Instruction

To improve response quality, it’s recommended that the first instruction include:

• Task goal: clearly state the problem to solve.
• Constraints: output format, forbidden items, or specific reference materials.
• Expected result: the form of the final deliverable you want.

Deep Dive into Configuration Options

Hermes’s Slack behavior can be fine-tuned via ~/.hermes/config.yaml.

1. Thread Reply Behavior (reply_in_thread)

• Path: platforms.slack.extra.reply_in_thread
• Default: true
• Behavior:
• true: the first instruction in a channel replies in a new thread.
• false: the first instruction in a channel replies directly in the main channel feed.
• Boundary: regardless of this setting, messages already inside a thread always reply within the thread.

2. Response Trigger Mechanism (require_mention)

• Path: require_mention
• Default: true
• Behavior: determines whether the bot can only be activated via @mention. In multi-person collaboration channels, keeping it true is recommended to avoid accidental triggers.

3. Custom Trigger Patterns (mention_patterns)

Beyond the standard @mention, you can configure custom trigger phrases via mention_patterns.

Example config:

• Use case: simplifies invocation in specific workflows without typing @ repeatedly.

4. Allowed Users Whitelist (SLACK_ALLOWED_USERS)

Hermes also supports restricting which users can talk to the bot via Slack Member IDs.

• How to configure: set the environment variable SLACK_ALLOWED_USERS
• Value type: a list of Slack Member IDs, not usernames or display names
• Safety behavior: if this whitelist isn’t set, the gateway rejects all messages by default as a security measure
• Use cases:
• Only allow specific members to call the bot
• Prevent unrelated members in the channel from triggering it accidentally
• Restrict usage scope in test environments

Recommended Configuration Combos

Depending on the scenario, these configuration strategies are recommended:

Scenario A: Multi-person Collaboration / Enterprise Channel (recommended)

Goal: maximum stability, zero interference.

• require_mention: true
• reply_in_thread: true
• mention_patterns: keep minimal or empty.

Scenario B: Personal / Small-Scale Fast-Iteration Channel

Goal: instant invocation, low friction.

• require_mention: false (use with caution) or a rich set of mention_patterns.
• reply_in_thread: true (still recommended to maintain context isolation).

Summary: The Slack Cheat Phrase

Mention in the channel first; one thread per task; start a new thread when changing topics; parallel users never cross lines.

Sources

• Hermes Slack Docs
• Configuration Options