Skip to main content
Claude Tag is Claude working in your Slack workspace. You hand it work by writing a message where Claude is, and Claude carries it out in that thread. An @Claude mention guarantees a response in a channel, but it isn’t required everywhere. DMs and threads Claude is already in reach it without one. There’s nothing for you to install or configure; if @Claude is in your channel, you can use it (unless your admin has restricted who can invoke Claude).

​
When to tag Claude in a channel versus a DM

Where you tag Claude decides whose tools it uses and who sees the result.
  • Channel for shared team work. The work happens in the open, so anything Claude does in the thread, including its checklist and results, is visible to everyone in the channel, and anyone can reply to steer the work. An admin sets what Claude can reach in each channel, and everyone who asks there gets the same access. By default you don’t need a Claude account to tag Claude in a channel; the work bills to the organization. An admin can restrict who can invoke Claude.
    • Example: @Claude where are we on the launch checklist? Pull what's still open from this channel and #design-review.
  • DM for personal tasks. A DM runs on your own claude.ai account with your own connectors. Every DM message reaches Claude without an @-mention. DMs are one-to-one only; group DMs aren’t supported.
    • Example: Pull my afternoon meetings from my calendar and draft a one-line prep note for each.
See team channels and personal DMs for the full comparison. If your workspace previously used the earlier Claude in Slack app, see how Claude Tag differs for what has changed.

​
Add Claude to a channel

Claude only works in channels it’s been added to. To add it, anyone in the channel can run:
Run the command in the channel’s message box. Slack rejects /invite sent from inside a thread. Or mention @Claude in a message; Slack will prompt you to add it.

​
Check that Claude is working

Mention @Claude in any channel where it’s been added. In the Slack message box, send:
A reply means it’s running there, and the answer tells you what it can reach.

​
What you see when Claude first joins a channel

When a person first invites Claude to a channel, it posts a short intro on its own: it reads the channel’s history and suggests a few tasks it could pick up. The intro doesn’t post when a bot adds Claude, in org-shared channels, or in channels that already have memory. Each reply ends with a footer showing an Open session in Claude link (the full record of that task), a Configure link (opens a page where you can tailor how Claude works in this channel), and which model handled the reply. You can choose a different model yourself, and admins set the default model for each channel.

​
Hand Claude a task

Every interaction has the same shape. You mention @Claude with a task, Claude works on it in the thread, and Claude posts the result there.
An “is thinking…” line appears at the bottom of the thread when Claude picks the task up, and it replies with results; a multi-step task also gets a checklist it updates as it works. A quiet thread after the “is thinking…” line means Claude is working, not stuck; long tasks can take a minute or more before the first reply. Once Claude is in a thread, you don’t need to @-mention it again; it reads every reply in that thread. Read Claude’s work before you use it, in proportion to what’s at stake. A summary you can skim; something going to a customer or changing a system gets a careful read. If a result needs checking, ask it to show its work in the same thread. The work runs on Anthropic’s servers, so it continues after you close Slack. Replies in the thread reach Claude without re-mentioning. If the thread looks idle, Claude is usually still working; see how to read its progress.

​
What Claude can see

After you’ve handed Claude a task, the first question is what it has to work with. The short version: it reads the thread you tagged it in, it can search your workspace’s public channels, and anything beyond Slack depends on what your admin connected. The fastest way to find out for your channel is to ask: @Claude can you read the doc I just linked? gets you a yes or a “that site isn’t allowed here.”
Slack doesn’t expose personal account settings (your sidebar, notification preferences, channel membership, or DMs between you and other people) to apps. If you want help organizing channels, paste or screenshot the list and Claude can propose a scheme you apply yourself.

​
Which messages Claude reads

  • An @-mention guarantees a response. Claude may also respond to a message that doesn’t mention it when it judges a reply is warranted; include the mention to guarantee one. It receives the thread’s root message and earlier replies for context when you mention it mid-thread; for details on the window, refer to what Claude sees when you mention it.
  • Once mentioned in a thread, Claude follows the rest of that thread and may reply without another mention.
  • While working on a task, Claude can search the workspace’s public channels by keyword, the same way a person searches Slack. It can’t read a channel’s full history unless it’s been added there.
To quiet Claude in a thread or remove it from a channel, see Control when Claude Tag responds.

​
Give Claude standing instructions

Set instructions for a channel by telling Claude there, the way you’d ask anyone on the team:
The instruction saves to channel memory and applies to everyone’s threads. Public-channel memory is also shared across your workspace. Verify with “what do you remember about this channel?”
  • Use case library: every shape of work, each with the prompts to paste
  • Good habits: how to write tasks that finish
  • Set up routines: once a task works, have Claude run it on its own schedule
  • Commands: exact words starting with ! that run a fixed action, like !restart for a stuck session