Skip to main content
A command is @Claude followed immediately by one of a few exact words starting with !. Claude matches the message against that word and runs a fixed action instead of starting a normal turn. !help, !restart, !mute, and !unmute must stand alone: adding extra words, as in !restart with words tacked on, makes the message an ordinary prompt instead. !feedback, !routines, and !fork accept text after the command, covered below.

​
See the commands available to you

Claude 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.

​
Restart a stuck or wrong-context session

Use 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. Every 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, the channel’s session is the one replying. Where you run !restart picks which session gets replaced:
  • In a thread, !restart replaces that thread’s session. The fresh session rereads the thread, so it keeps what’s in the messages and drops everything else the old one was carrying.
  • At a channel’s top level, !restart replaces the channel’s session. The fresh session picks up from where the old one left off.
Claude confirms once the replacement session is ready. If the restart can’t complete, Claude tells you and you can run !restart again. You need the same access to run !restart that you’d need to message the session directly; someone who can only observe a thread can’t restart it.

​
Mute or unmute a thread

Run !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 posts, and service notices are unaffected. There’s no channel-level mute. If you run !mute at a channel’s top level, Claude posts this hint:
To quiet unprompted replies across a whole channel, save a mention-only instruction to channel memory. Unmute the same way:
A muted thread also unmutes on any direct @Claude mention, so you don’t need !unmute before asking something new. You need the same access to mute or unmute a thread that you’d need to message Claude there.

​
Send feedback

Opens a form in Slack for sending feedback on Claude Tag to the team that builds it, along with a note on what the report includes. Add words after !feedback and Claude carries them into the form as a starting draft, which you can still edit before submitting:

​
List the routines in a channel

Claude replies in the thread with the routines 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.
  • For the current channel, run !routines in that channel.
  • 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.
If the single word after !routines isn’t a channel mention or ID, Claude replies with how to use the command. Adding two or more words makes the message an ordinary prompt that starts a normal turn instead.

​
Continue a thread in another channel

Run !fork from inside a thread Claude is part of, and Claude continues that conversation in a new thread in the channel you name. Use it when a discussion outgrows its home channel: a bug thread that turns out to belong in the owning team’s channel, or a side question that deserves its own audience. The fork starts a new thread in Slack and links the two threads together:
  • In the channel you name, Claude posts a new top-level message that links back to the original thread and carries your prompt, then continues in the replies under it. The new conversation starts with the original thread as background, so nobody has to re-explain.
  • Back in the original thread, Claude replies with a link to the new thread, so anyone following along can see where the conversation continued.
The prompt is required, and it kicks off the new thread: Claude starts working on it there right away. Pick the channel from Slack’s # autocomplete so it arrives as a channel mention. The channel must be public, and both you and Claude must be members of it; invite Claude with /invite @Claude first if it isn’t there yet. On Enterprise Grid, a public channel in another workspace of your grid also works when that workspace is paired to the same Claude organization, but a channel shared across workspaces doesn’t. !fork works from threads in public channels only. Threads in private channels, DMs, and group DMs can’t be forked, since forking would carry the conversation to a different audience. If the fork can’t be set up, Claude replies with a note only you can see, and nothing is posted in either channel.