Commands Claude Tag understands changedclaude-tag/users/commands
Nearest release: v2.1.296, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 9 Oct 2026 19:07 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+13added
Lines−13removed
From line
18
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits14to this page, all time
The whole hunk
from line 18, old and new numbered
/
from line 18
1818
1919Claude replies with the commands it understands in your workspace. The list can differ by workspace, since a command can be enabled for some workspaces and not others.
2020
21In a [Slack Connect channel](/docs/claude-tag/admins/restrict-access#slack-connect-channels), one shared with another company, only `!help`, `!mute`, `!unmute`, `!restart`, and `!fast` work, and people from the other company can use only `!help`.
21In a [Slack Connect channel](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), one shared with another company, only `!help`, `!mute`, `!unmute`, `!restart`, and `!fast` work, and people from the other company can use only `!help`.
2222
2323## Get the link to configure a channel
2424
from line 26
2626@Claude !configure
2727```
2828
29Run `!configure` in a channel, and Claude replies in the thread with a link to that channel's Configure page on claude.ai. On that page you [tailor how Claude works in the channel](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), for example by editing its channel instructions, and it's the same page the **Configure** link in the footer of any Claude reply opens. In a DM with Claude there are no per-channel settings, so Claude replies there with a link to [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag) instead.
29Run `!configure` in a channel, and Claude replies in the thread with a link to that channel's Configure page on claude.ai. On that page you [tailor how Claude works in the channel](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel), for example by editing its channel instructions, and it's the same page the **Configure** link in the footer of any Claude reply opens. In a DM with Claude there are no per-channel settings, so Claude replies there with a link to [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag) instead.
3030
3131## Restart a stuck or wrong-context session
3232
from line 36
3636
3737Use this when a session is stuck, or when it's carrying context you don't want the next reply to build on. Claude archives the current session and starts a fresh one in its place.
3838
39Every thread Claude takes part in runs a session of its own, holding that one conversation. Some channels have one more session on top of the per-thread ones. That session belongs to the channel itself, and it's the session Claude works from at the channel's top level, outside any thread. When Claude [replies to a top-level message no one mentioned it in](/docs/claude-tag/users/when-claude-responds), the channel's session is the one replying.
39Every thread Claude takes part in runs a session of its own, holding that one conversation. Some channels have one more session on top of the per-thread ones. That session belongs to the channel itself, and it's the session Claude works from at the channel's top level, outside any thread. When Claude [replies to a top-level message no one mentioned it in](/docs/claude-tag/users/when-claude-responds.md), the channel's session is the one replying.
4040
4141Where you run `!restart` picks which session gets replaced:
4242
from line 69
6969@Claude !mute
7070```
7171
72Run `!mute` in a thread Claude is part of, and Claude stops replying there. Muting is per thread by design. Other threads, the channel's top level, [routine](/docs/claude-tag/users/proactivity) posts, and service notices are unaffected.
72Run `!mute` in a thread Claude is part of, and Claude stops replying there. Muting is per thread by design. Other threads, the channel's top level, [routine](/docs/claude-tag/users/proactivity.md) posts, and service notices are unaffected.
7373
7474There's no channel-level mute. If you run `!mute` at a channel's top level, Claude posts this hint:
7575
from line 77
7777:mute: Muting works per thread — reply `@Claude !mute` (or `!unmute`) inside the thread you mean.
7878```
7979
80To quiet unprompted replies across a whole channel, turn the channel's [**Respond automatically** setting](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) off.
80To quiet unprompted replies across a whole channel, turn the channel's [**Respond automatically** setting](/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) off.
8181
8282Unmute the same way:
8383
from line 106
106106@Claude !fast off
107107```
108108
109`!fast` turns on [fast mode](/docs/claude-tag/users/models#run-a-thread-in-fast-mode), which gives faster output at a higher cost per token. `!fast on` does the same, and `!fast off` returns to standard speed. Any other text after `!fast` makes the message an ordinary prompt.
109`!fast` turns on [fast mode](/docs/claude-tag/users/models.md#run-a-thread-in-fast-mode), which gives faster output at a higher cost per token. `!fast on` does the same, and `!fast off` returns to standard speed. Any other text after `!fast` makes the message an ordinary prompt.
110110
111111Fast mode runs on Opus models, so `!fast` can change the session's model as well as its speed. The footer of each Claude reply names the model the session is on.
112112
113113* **If the session is on an Opus model**, it stays on that model
114* **If the session is on another model, such as Sonnet**, Claude switches it to the newest Opus model [you can use](/docs/claude-tag/users/models#which-models-you-can-use). The session stays on that model after `!fast off`. To go back, [ask Claude to switch models](/docs/claude-tag/users/models#switch-the-model-in-a-thread).
114* **If the session is on another model, such as Sonnet**, Claude switches it to the newest Opus model [you can use](/docs/claude-tag/users/models.md#which-models-you-can-use). The session stays on that model after `!fast off`. To go back, [ask Claude to switch models](/docs/claude-tag/users/models.md#switch-the-model-in-a-thread).
115115
116116In both cases, replies speed up only if that Opus version [supports fast mode](https://code.claude.com/docs/en/fast-mode).
117117
118The command changes a different [session](/docs/claude-tag/concepts/glossary#session) depending on where you send it:
118The command changes a different [session](/docs/claude-tag/concepts/glossary.md#session) depending on where you send it:
119119
120120* **In a thread**, it changes that thread's session. In a channel thread Claude isn't part of yet, `!fast` starts the thread's session in fast mode and switches its model the same way, so your next request there runs fast from the start.
121121* **At a channel's top level**, it changes the channel's own session, the one Claude works from outside any thread. Thread sessions keep their speed. Claude's confirmation appears as a reply under your command. To turn fast mode off again, send `!fast off` at the top level, not in that reply thread.
from line 133
133133
134134| Claude replies | What to do |
135135| :- | :- |
136| `Fast mode isn't turned on for this organization. An organization owner can turn it on.` | Ask an Owner to [allow fast mode](/docs/claude-tag/admins/customize#allow-fast-mode) |
136| `Fast mode isn't turned on for this organization. An organization owner can turn it on.` | Ask an Owner to [allow fast mode](/docs/claude-tag/admins/customize.md#allow-fast-mode) |
137137| `Fast mode can't be changed for organizations with restricted compliance settings.` | Work at standard speed. Your organization's compliance settings don't allow fast mode. |
138138| `Fast mode isn't available for this session.` | Run the command in a new thread. If Claude gives the same reply there, fast mode isn't available in this channel. |
139139| `Only a workspace member who can use Claude here can change fast mode.` | Ask a full member of the workspace who can message Claude in this channel to run the command |
from line 159
159159@Claude !routines
160160```
161161
162Claude replies in the thread with the [routines](/docs/claude-tag/users/proactivity) set up in the channel: the scheduled jobs, watched channels, and other standing work it runs there. The list covers only that channel's routines.
162Claude replies in the thread with the [routines](/docs/claude-tag/users/proactivity.md) set up in the channel: the scheduled jobs, watched channels, and other standing work it runs there. The list covers only that channel's routines.
163163
164164* **For the current channel**, run `!routines` in that channel.
165165* **For another channel**, add the channel mention or its ID, as in `@Claude !routines #other-channel`. You need to be a member of that channel, and it must belong to your organization. Claude sends the list in a reply only you can see, so that channel's routines aren't posted for everyone in the channel where you asked.
from line 190
190190
191191## Related resources
192192
193* [Set up routines](/docs/claude-tag/users/proactivity): the standing work `!routines` lists, and how to create, edit, or disable it
194* [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds): what makes Claude reply without any command or mention at all
195* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access): the admin controls that decide who can message Claude at all, including its commands
193* [Set up routines](/docs/claude-tag/users/proactivity.md): the standing work `!routines` lists, and how to create, edit, or disable it
194* [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without any command or mention at all
195* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access.md): the admin controls that decide who can message Claude at all, including its commands
196196
No line in this hunk matches that.