Troubleshoot Claude Tag in channels and DMs changedclaude-tag/users/troubleshooting
Nearest release: v2.1.288, published 5 hours after 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 2 Oct 2026 13:01 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 2 Oct 2026 13:07 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−1removed
From line
28
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits25to this page, all time
The whole hunk
from line 28, old and new numbered
/
from line 28
2828
29291. **Is the Claude app installed in this workspace?** Start typing `@Claude` in any channel. **Works**: Slack autocompletes to a Claude app with an app badge; if more than one Claude app appears, check with your admin which one to use. **Fails**: nothing autocompletes, or only a person named Claude appears. The app isn't installed; this needs your admin (send them the [setup overview](/docs/claude-tag/admins/setup-overview)).
30302. **Is Claude in this channel?** Type `/invite @Claude` in the channel's message box, not in a thread reply. Slack rejects `/invite` inside threads ("/invite is not supported in threads. Sorry!"). **Works**: Slack posts "Claude was added to #channel" (or "is already in this channel"). Mention it again. **Fails**: Slack says you can't add apps to this channel (a Slack Connect or guest-restricted channel); try an internal channel instead. If Slack says "You don't have permission to invite people to this channel", the channel or workspace limits who can add people. In Slack, open **Channel details** → **Agents & apps** (called **Integrations** in some Slack versions), select **Add**, and pick **Claude**. Or ask someone who can add people to the channel to add Claude.
313. **Is Claude Tag turned on for this channel?** Mention it again now that it's invited. **Works**: it reacts and replies. **Fails**: it replies "Claude is disabled in this channel" (Claude Tag is turned off for the channel, its workspace, or the organization), or it replies but behaves like the earlier Claude in Slack, with no channel memory and pull requests opening under your name rather than Claude's (the channel is set to **Legacy**). Either way this needs your admin (send them [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/restrict-access#migrate-from-the-earlier-claude-in-slack)).
313. **Is Claude Tag turned on for this channel?** Mention it again now that it's invited. **Works**: it reacts and replies. **Fails**: Claude replies in one of these ways, and each needs your admin:
32 * **A notice that starts "Claude isn't on in this channel yet"**: your admin hasn't finished setting up Claude Tag. Send them [Launch Claude Tag](/docs/claude-tag/admins/setup-overview#launch-claude-tag).
33 * **A notice that says "Claude is disabled in this channel"**: Claude Tag is turned off for the channel, its workspace, or the organization. Send them [Claude is disabled in this channel](/docs/claude-tag/admins/troubleshooting#claude-is-disabled-in-this-channel).
34 * **A reply that behaves like the earlier Claude in Slack**: the channel is set to **Legacy**. Replies have no channel memory, and pull requests open under your name rather than Claude's. Send them [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/restrict-access#migrate-from-the-earlier-claude-in-slack).
3235
3336If `@Claude` still gets no reaction and no reply after all three, send the [admin entries for a silent workspace](/docs/claude-tag/admins/troubleshooting#nothing-responds) to an admin. For silence in one channel, send them to your Claude admin. For silence across a whole workspace or a whole Enterprise Grid, send them to whoever administers Slack for you, because the fix usually needs a Slack admin.
3437
No line in this hunk matches that.