Control when Claude Tag responds changedclaude-tag/users/when-claude-responds
Nearest release: v2.1.318, published 3 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 4 Nov 2026 00:58 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 4 Nov 2026 01:07 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−5removed
From line
32
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits27to this page, all time
The whole hunk
from line 32, old and new numbered
/
from line 32
3232
3333* **Nothing.** This is the usual outcome, especially in a channel where nobody has told Claude which kinds of messages to answer.
3434* **An offer to help.** When a thread leaves a concrete next step Claude could take for someone, Claude may offer in that thread to take it. The offer is either a one-line reply everyone can see or a [private suggestion](#private-suggestions-from-claude) only that person can see.
35* **A short reply in a thread under the message.** Claude replies on its own only when it already has the answer, from the channel's history or its memory, and the answer fits in one message. Replies of this kind carry the plain name **Claude**; see [The name on a reply](#the-name-on-a-reply).
35* **A short reply in a thread under the message.** Claude may reply on its own when it already has the answer, from the channel's history or its memory, and the answer fits in one message. Replies of this kind carry the plain name **Claude**; see [The name on a reply](#the-name-on-a-reply).
3636* **A working session in the message's thread.** When a message needs investigation, tools, or a longer exchange, Claude starts a working session there and posts the work in that thread. For an untagged message, Claude does this only when someone in the channel has told it to pick up that kind of work, as described below the list.
3737* **A hand-off to work already in progress.** When a message adds to something Claude is already working on in another thread, for example a new detail about a bug it's investigating, Claude passes the message to that working session instead of replying. Claude posts nothing in the channel when it does this; anything the new information changes, it reports in the thread where the work is happening.
3838
from line 85
8585A bot's `@Claude` at the channel's top level gets a reply in a thread under that message, unless any of these is true:
8686
8787* The channel's [**Respond automatically**](#turn-automatic-replies-on-or-off) setting is off.
88* Claude has [stopped reading the channel](#when-claude-stops-reading-a-channel) because of message volume.
8988* The channel is a [Slack Connect channel](https://claude.com/docs/claude-tag/admins/restrict-access.md#when-claude-does-not-answer-in-a-slack-connect-channel), shared with another company. Claude reads what apps, bots, and workflows post there as context but doesn't reply to them.
9089
9190A person's mention reaches Claude in each of these cases.
from line 148
149148* **Message volume.** Claude counts the messages posted in the channel since it last posted there itself, and stops reading when the count gets high enough.
150149* **Inactivity.** When more than 10 days pass without anyone @-mentioning Claude in the channel and without Claude posting there, Claude stops reading.
151150
152While Claude isn't reading a channel, it doesn't reply there unprompted. Claude posts no notice when it stops.
151Claude posts no notice when it stops.
153152
154To start Claude reading again, mention `@Claude` in the channel. A mention from a person reaches Claude in both situations, and once Claude posts its reply, it reads the channel's messages again. A mention inside another app's or bot's message starts Claude reading again only after an inactivity stop.
153To start Claude reading again, mention `@Claude` in the channel. A mention from a person reaches Claude in both situations, and once Claude posts its reply, it reads the channel's messages again. A mention inside another app's or bot's message works the same way, except in the [cases that block a bot's reply](#messages-from-other-apps-and-bots).
155154
156155If unprompted replies don't come back after Claude answers a mention, check **How Claude participates** on the channel's [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). Answering a mention doesn't change the setting, so if the page shows **Only when @-mentioned**, change it to **Respond automatically** in one of the three places listed in [Turn automatic replies on or off](#turn-automatic-replies-on-or-off).
157156
from line 163
164163* **Channels shared across workspaces connected to different Claude organizations.** Every workspace where Claude runs is connected to a Claude organization, the account a company sets up for Claude. When a channel is shared across workspaces connected to different Claude organizations, Claude won't reply there and posts a refusal message instead. You can't tell from Slack how a workspace is connected; the refusal message itself is the signal. Use a channel that belongs to one workspace, or send Claude a DM.
165164* **Slack Connect channels.** By default, Claude is off in [channels shared with another company](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), and a mention there gets no reply and no notice. An Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan to change [**How should Claude work in channels with guests**](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels).
166165
167When the workspaces sharing a channel all belong to one Claude organization, Claude replies there, but with only your organization's default access and settings. The repositories, instructions, and memory set up for that channel or its workspaces don't apply, and Claude posts a notice in the thread explaining this from time to time. The guest check above still applies first where guest access is restricted.
166When the workspaces sharing a channel all belong to one Claude organization and an admin hasn't turned Claude off for these channels, Claude replies there, but with only your organization's default access and settings. The repositories, instructions, and memory set up for that channel or its workspaces don't apply, and Claude posts a notice in the thread explaining this from time to time. The guest check above still applies first where guest access is restricted.
168167
169168To confirm a channel's setting, check **How Claude participates** on its [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). To confirm an instruction Claude saved, ask `@Claude what do you remember about responding in this channel?`, and see [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) for where instructions are stored and how to change them.
170169
No line in this hunk matches that.