Commands Claude Tag understands changedclaude-tag/users/commands
Nearest release: v2.1.287, published an hour 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 1 Oct 2026 18:45 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 1 Oct 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+3added
Lines−3removed
From line
118
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits9to this page, all time
The whole hunk
from line 118, old and new numbered
/
from line 118
118118The command changes a different [session](/docs/claude-tag/concepts/glossary#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.
121* **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.
121* **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.
122122* **In a direct message**, it works only inside a thread where Claude is already working
123123
124124Claude confirms with a reply that everyone in the conversation can see. At a channel's top level, the reply says "channel" in place of "thread". When Claude switches the model, the reply also names the new model, as in this example.
125125
126126```text wrap theme={null}
127Fast mode is on for this thread. Switched to claude-opus-4-8, since the previous model has no fast mode.
127Fast mode is on for this thread. Switched to claude-opus-5-5, since the previous model has no fast mode.
128128```
129129
130130If the session was on another model, such as Sonnet, and the reply says only `Fast mode is on for this thread.`, Claude couldn't switch the model. The session keeps its model, and replies on that model stay at standard speed. One cause is that no Opus model is among the models you can use.
from line 137
137137| `Fast mode isn't available in a channel with guests.` | Work in a channel without guests. This channel runs with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works) while a guest is present, and sessions there stay at standard speed. |
138138| `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 |
139139| `No session is running in this channel.` | Run `!fast` in a thread. You ran it at the top level of a channel that has no session of its own. |
140| `No session is running here, so there is nothing to switch.` | Nothing. You ran `!fast off` in a thread Claude isn't part of, and a new session there starts at standard speed. |
140| `No session is running here, so there is nothing to switch.` | You ran `!fast off` in a thread where Claude has no session. If you turned fast mode on at the channel's top level, send `@Claude !fast off` at the top level too, not as a reply under Claude's confirmation. Otherwise do nothing, because a new session in the thread starts at standard speed. |
141141| `Sorry, I couldn't change fast mode. Please try again.` | Run the command again |
142142
143143In a [channel shared with another company](/docs/claude-tag/users/troubleshooting#claude-never-responds-in-a-channel-shared-with-another-company), Claude doesn't answer `!fast`. Use a channel that only your organization is in.
No line in this hunk matches that.