From 2b226be8e3c7f2190f6810b4c275fffd55fa764c Mon Sep 17 00:00:00 2001 From: navahc09 Date: Sun, 14 Jun 2026 00:09:59 +0530 Subject: [PATCH] docs(messaging): document the '!' prefix for Slack thread commands MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Salvaged from #45765 by @navahc09 — kept the PR's callout structure and placement, rewrote the content to match current behavior: Slack blocks native slash commands in threads and never delivers them, so Hermes recognises a leading '!' as an alternate command prefix. Post-C3 command fixes the bang form also works behind a mention (@Hermes !cmd) and with leading whitespace; unknown '!' tokens pass through to the agent unchanged. Cross-linked the detailed slack.md section. --- website/docs/reference/slash-commands.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/docs/reference/slash-commands.md b/website/docs/reference/slash-commands.md index bd81a5107624..1b621aeea1a7 100644 --- a/website/docs/reference/slash-commands.md +++ b/website/docs/reference/slash-commands.md @@ -201,6 +201,9 @@ Commands support prefix matching: typing `/h` resolves to `/help`, `/mod` resolv ## Messaging slash commands +> **Slack thread commands (`!` prefix):** +> Slack itself blocks native slash commands inside message threads ("/queue is not supported in threads. Sorry!") and never delivers them to Hermes. Inside a Slack thread, use the `!` prefix instead — `!stop`, `!new`, `!status` — and the gateway dispatches it exactly like the slash form. `@Hermes !stop` and `@Hermes /stop` work in threads too. Only the first token is checked against the known command list, so messages like `!nice work` pass through to the agent unchanged. See [Using commands inside threads](/user-guide/messaging/slack#using-commands-inside-threads-the-cmd-prefix) for details. + The messaging gateway supports the following built-in commands inside Telegram, Discord, Slack, WhatsApp, Signal, Email, Home Assistant, and Teams chats: | Command | Description |