Claude in Slack moved to Claude Tag on August 3, 2026. The current service is in beta for Team and Enterprise organizations. Older instructions for the previous Slack app may describe different behavior. Current Claude Tag overview, checked October 24, 2026.
Identify where the unwanted response starts
Imagine a fictional workshop-operations channel. People use it to discuss room changes and delivery times. They want Claude to help only when explicitly asked. An existing logistics thread already includes Claude, and a separate morning digest appears on a schedule.
Those are three different sources of activity. Record one example of each before changing settings: the top-level message, the followed thread, and the scheduled digest. This helps you check the actual scope of a change.
| Activity | Control to inspect |
|---|---|
| Unprompted responses to channel messages | Channel Respond automatically |
| Continued replies inside an existing thread | That thread's response or mute state |
| A currently running investigation | Stop on its working indicator |
| A digest arriving at a set time | Its routine schedule |
Do not change all four at once if you only need to quiet one discussion. Choose the activity you intend to change, then check that result.
Make the channel mention-only
Where channel edits are permitted, send this explicit request in the channel:
@Claude only respond in this channel when someone @-mentions you directly.
Alternatively, open Configure in a Claude channel reply's footer, switch off Respond automatically, and select Save. An Owner or Claude Tag admin can use the channel's General tab under Organization settings > Claude Tag. The setting is per channel. Channel controls and permissions
For the workshop example, inspect the setting for the workshop channel itself. A confirmation about another channel does not settle this channel's behavior. Avoid sending a stream of test messages to colleagues; one agreed, harmless check is enough to verify the intended setting in context.
If the channel is locked against member edits, ask the Owner or Claude Tag admin to make the change. Include the channel and the behavior you want, such as “keep explicit requests available, turn off unsolicited channel replies.”
Quiet the already-followed thread
In the logistics thread, ask Claude to respond only when mentioned. For a complete thread mute, use @Claude !mute. These controls affect that thread rather than every channel discussion. @Claude !unmute, or a mention carrying a request, can reactivate a muted thread. Thread controls
After making the change, read the confirmation in the same thread. Keep the thread and channel checks separate in your own note. Otherwise, a quiet top-level channel can hide an active thread that still receives every reply.
If Claude is actively working on an unwanted task, select Stop on the thread's working indicator. That interrupts the running task; it is a different action from deciding how future messages should trigger responses. Working-task indicator
Check scheduled activity and access separately
A morning digest that arrives without a new message may be a routine. Inspect that routine before assuming the channel response setting failed. If the digest remains useful, retain it and make the intended delivery clear to the channel. If its purpose has ended, have the responsible person update or stop that specific routine.
Mention-only behavior does not remove Claude's reading access. If the requirement is to end its presence in the channel, use /remove @Claude where your Slack permissions allow it, or ask the administrator. Reading access and removal
For a broader question about choosing between a connected search and an assistant inside Slack, the ChatGPT Slack guide explains those two surfaces for that product. Here, finish with the workshop channel's intended state recorded: mention-only channel replies, the logistics thread quieted, and a deliberate decision about the morning routine.