Kamran Imam All free guides
TAG

Claude Tag: the Slack teammate setup most teams get wrong on day one

A free guide by Kamran ImamInstagram · TikTok · YouTube

Anthropic launched Claude Tag on June 23, 2026 — an @Claude that joins your Slack channels as a shared, always-on teammate. This is the 5-minute setup, plus the one scoping detail that is your entire security model. No signup.

What Claude Tag actually is

Claude Tag lets you add @Claude to a Slack channel as a team member. You grant it access to selected channels and connect the tools, data, and even codebases you choose. Anyone in the channel can tag @Claude with a task in plain language; it breaks the task into stages, works through them using its tools, and replies in the thread with what it created.

Crucially, it is multiplayer — there is ONE shared Claude per channel that everyone interacts with, so anyone can see what it’s doing and pick up where the last person left off. It runs on Opus 4.8 and replaces the older “Claude in Slack” app.

Setup in 4 steps

  1. Pair Claude Tag with your Slack workspace — Enterprise/Team admin settings → Claude in Slack.
  2. Give Claude access only to the tools and data a given channel needs. Don’t grant broad access by default — scope it to what that channel’s work actually requires.
  3. Set a monthly spend limit for the org and per channel so there are no billing surprises.
  4. Test it in a private channel first to confirm permissions and behavior before opening it up to the team.

The detail the launch posts skipped

Memory is scoped per channel. Anthropic models this as separate Claude identities — a Claude set up for sales work will not pass its memories to a Claude set up for engineering, and engineers won’t get access to sales data or tools.

Claude can learn from other channels and data sources only if granted permission, and it will not report from private channels. Admins can also view a full log of everything @Claude has done and who requested each task.

The takeaway: define the channel boundaries and access scopes first, then start handing it tasks. That ordering is the whole security model — get it backwards and you’ve created a context leak.

Why it matters now

This is not a demo. Anthropic says 65% of its product team’s code is already created by their internal version of Claude Tag, and the pattern has spread beyond engineering to chasing product metrics, working support tickets, and root-causing bugs.

@Claude works asynchronously — you delegate a task and move on while it works, and it can even schedule its own tasks and pursue a project autonomously over hours or days. With “ambient” mode enabled, it proactively flags relevant info and follows up on threads that have gone quiet.

How to think about it

Stop opening a fresh chat and re-pasting context every morning. You’re not prompting a chatbot — you’re adding a teammate to the channel that remembers the work, takes initiative, and runs while you sleep.

Delegation, not prompting.

Here’s what a real task looks like in the channel:

@Claude pull last week's signups from Stripe, compare to the prior week, and post the deltas in this thread.

That’s it. Claude goes off, does the work, and posts back in the thread. Anyone in the channel can see the result, ask follow-up questions, or pick up the thread and take it further.

“You don’t open a chat with it. You add it to the team.”

Found this useful? Follow along for new guides.

New breakdowns drop every week across TikTok, Instagram, and YouTube.

← All free guides