Control when Claude Tag responds changedclaude-tag/users/when-claude-responds
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 9 Oct 2026 19:37 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−1removed
From line
137
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 137, old and new numbered
/
from line 137
137137* **Editing a message to add the mention.** An edit doesn't trigger a response. Delete the message and send a new one with `@Claude` included.
138138* **Channels with guest accounts.** By default, Claude is off in channels that include guests; 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, or send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels).
139139* **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.
140* **Slack Connect channels.** Claude doesn't answer in [channels shared with another company](/docs/claude-tag/admins/restrict-access#slack-connect-channels). A mention there gets a notice saying Claude isn't turned on for Slack Connect channels, and no admin setting changes that.
140* **Slack Connect channels.** By default, Claude is off in [channels shared with another company](/docs/claude-tag/admins/restrict-access#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**](/docs/claude-tag/admins/restrict-access#slack-connect-channels).
141141
142142When 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.
143143
No line in this hunk matches that.