What Is Claude Tag? And How to Set It Up

Claude Tag is a new feature that puts Claude into your Slack as a shared team member. Anyone in a channel can tag @Claude to hand it a task, everyone can see what it's doing, and it remembers the channel's work over time. Unlike a normal AI chat, it's multiplayer, it works around the clock, and the whole team shares one Claude rather than each person starting from scratch in their own window. This guide explains what Claude Tag is, the four things that make it different, and exactly how to set it up.

Up to now, AI at work has mostly been single player. You open a chat, you get your answer, and the context lives in your history. The moment a teammate needs the same thing, they start over from zero. Claude Tag closes that gap by moving Claude into the place your team already works.

We train business teams on tools like this every week, so this is the practical version: what it does, where it's most useful, and the setup steps that'll make the difference for you.

What Claude Tag is

Claude Tag is Claude living inside Slack as a proper member of your workspace. You add it to a channel, tag it like you'd tag a colleague, and hand it a task in plain language. It reacts to show it's seen the message, posts a short plan for anything substantial, works through a visible checklist, and reports back in the thread where everyone can follow along.

Because it sits in the thread, the whole team shares the same Claude and the same context. Hand it a messy planning thread and it can turn the decisions into tasks in your project tool, assigned to the right people with the right due dates. It also connects to your business apps, so the work lands where it's meant to, not in a chat you then copy and paste from.

The four things that make Claude Tag different

It's multiplayer

Everyone in a channel works with the same Claude. In any Slack channel, you add Claude Tag and start collaborating, and because the thread is shared, nobody re-explains the context. One person can ask Claude to draft an email in your marketing tool using details from the thread, and anyone else can reply to refine it without briefing Claude from scratch. This is the real shift: AI stops being a private window and becomes a shared teammate.

It already knows your work

Claude Tag reads a channel's history. Add it to a channel and the first thing it does is catch up on what's been said, then tell you what it can help with. Point it at a channel where sign-ups, tickets or feedback land, and it can run analysis on the existing messages and even chart the result. The uses write themselves: a channel of customer complaints becomes a live read on your most critical issues, and a strategy channel gets a summary of everything agreed each week.

It learns and improves over time

The longer Claude Tag follows a channel, the more context it builds, so your team explains less over time. Teaching it a preference is a single message. If it handles a case wrong, you tell it the rule once, in plain language, and ask it to remember, and it saves that for the channel going forward. Every rule it learns is visible and editable in the Claude admin panel, organised per channel, so the memory is transparent rather than a black box.

It works asynchronously

This is the one with the most potential. Claude Tag works around the clock, and unlike Claude Cowork or Claude Code, you don't need to be at your laptop for it to run. It can also schedule work for itself. Drop in a sentence asking it to run a report every Monday at 8am comparing last week to the week before, and it sets up the schedule and confirms the first run. What used to take hours to configure in an automation tool, choosing what to sum, average and aggregate, is now a plain-language request you can adjust by talking to it. A useful habit is to ask for a test run, so you see the output before it goes live.

How to set up Claude Tag

Setup matters here, so it's worth doing properly. You need two permissions before you start: someone who is an owner in your Claude account, and someone who is a Slack admin. One person can hold both.

1. Enable Claude Tag in your Claude account

Everything you use happens in Slack, but you switch it on from Claude. Go to Settings, then Organisation settings, then Products, where you'll find Claude Tag in beta. It's currently available on Team and Enterprise plans only, so an individual plan won't see it. Open the Claude Tag settings and enable it for your organisation.

2. Connect your Slack workspace

Under "where Claude Tag works", click Connect for the full instructions. Make sure the Claude app is installed in the right Slack workspace and on the latest version, then from any channel or a direct message to the app, type "@Claude connect". Claude returns a one-time pairing code that expires in 15 minutes. Copy it back into your Claude admin settings. You then choose where Claude Tag lives, a single channel or the whole workspace. Even if you pick the whole workspace, you still add it to each channel where you actually want it.

3. Set up access bundles

Next you decide what Claude can do, through what Claude calls an access bundle: the set of apps and tools it can use. The useful part for teams is that different channels can have different bundles. Your finance channel connects finance tools, your marketing channels connect your CRM and marketing stack, and each team only touches what it's allowed to. Claude offers some pre-approved apps, and you can connect anything else with its API credentials. One thing to know upfront: Claude Tag leans on API credentials rather than the connectors you may know from Cowork and Code.

4. Set a spending limit and launch

Claude Tag is billed on usage, not per seat, so set a monthly spending limit to keep it in budget before you launch. Then click Launch Claude. Once connected, open the extra settings and check two things: set the Claude Tag version to New rather than Legacy, and, under advanced settings, choose your default model per channel, since a heavier model means more spend. This is also where you can restrict guests, which matters when you work with partners in shared channels and don't want outside users controlling a Claude connected to your tools.

5. Add it to a channel and tune per channel

To add Claude to a channel, type "/invite @Claude" in that channel. By default it inherits your workspace-level access bundle. To give a channel a specific toolset, add the channel by its ID in settings, where you can also give it a description and a system prompt it reads before working there. The workspace-level bundle is inherited by every channel and can't be removed, so the sensible pattern is a tightly restricted default bundle, with extra access added per channel as needed. You can also click the Configure link on any Claude reply to add channel-specific instructions, and decide whether everyone in the channel can edit them.

Where Claude Tag still has rough edges

It's worth being honest about the current limits, because they shape how you set it up. Tool connections lean towards API keys rather than the MCP connectors used across the rest of Claude, so tools that expect an account login can be harder to wire in, and a few login-based options only cover Google Drive, Gmail and Google Calendar. Skills are the other one: you can't drop in a skill you built in Cowork or Code directly, you package it as a plugin first. So the setup that works best today is to add your apps in the credentials tab, then create dedicated plugins that teach Claude how to use each tool.

Who Claude Tag is for

Claude Tag suits teams that live in Slack and make decisions in threads: marketing, operations, customer teams, founders coordinating across functions. It's most powerful where work is repetitive and channel-based, like reporting, triage and turning decisions into tasks. Because it's on Team and Enterprise plans and billed on usage, it's an organisation-level tool rather than a solo one, which fits its whole point: a Claude the team shares.

The bottom line

Claude Tag turns Claude into a shared Slack teammate. It's multiplayer so the whole team works with one Claude, it reads a channel's history so it already knows the work, it learns your rules over time, and it runs asynchronously so it keeps working after you log off. Setup takes a Claude owner and a Slack admin, a pairing code, and some care over access bundles, the New version, a spending limit and guest restrictions. Get that right and you've moved AI into the place your team already works.

If you want your team getting real value from tools like this, our hands-on Claude training for teams takes people from their first task to shared, working AI habits.

Common questions

What is Claude Tag? A feature that adds Claude to your Slack as a shared team member. Anyone in a channel tags @Claude to hand it a task, the whole team sees the work in the thread, and Claude remembers the channel's context over time.

How is Claude Tag different from Claude Cowork or Claude Code? Claude Tag is multiplayer and asynchronous: it lives in Slack, the team shares one Claude, and it runs without you at your laptop, including on a schedule. Cowork and Code are single-user tools you drive from your own machine.

How much does Claude Tag cost? It's billed on usage rather than per seat, and you set a monthly spending limit. It's available on Team and Enterprise plans, not individual plans.

Do I need to be an admin to set up Claude Tag? Yes. You need a Claude account owner to enable it and a Slack admin to connect it. One person can be both. Adding Claude to individual channels afterwards is straightforward.

What can Claude Tag connect to? Your business apps, through access bundles set per channel, using pre-approved apps or your own API credentials. It currently favours API keys over account-login connectors, so plan your tool connections accordingly.