← Back to all free guides
A free guide by Mariah Brunner ↗ INSTAGRAM ↗ TIKTOK

Claude Just
Joined The Team

Claude Tag turns Claude from a personal assistant into a teammate that lives in your Slack. Here’s what it does, why it acts as itself instead of as you, and the three ways teams get real value out of it.

Up to now, AI at work has been private. You opened a chat, typed, got an answer, and nobody on your team ever saw it. It only knew your corner of the work.

Claude Tag flips that. You mention @Claude in a Slack channel or thread, it reads the conversation everyone already shares, and it does the work right there. Moving AI into the shared channel also forced Anthropic to answer a question most people never think about: whose access should the AI use?

What It Does

01

Reads the whole thread

Tag it like a coworker and it picks up the context, so you don’t re-explain the decision, the bug or the back-and-forth that got you here.

02

Does the task

Run the numbers, pull data and post it, turn a long thread into action items, file a ticket, or open a pull request from a bug report. It works with connected tools like GitHub, Linear, Datadog, Salesforce, Snowflake and BigQuery.

03

Keeps working without being tagged

Give it a routine, which is standing work on a schedule. It can post a weekly digest, watch other channels for a topic, follow a pull request until it merges, or tag you back when a decision needs you.

04

Remembers the channel

Say "remember for this channel" and that rule applies to everyone’s threads there. What it learns in a private channel stays in that channel.

Why It Acts As Itself

Normally, when AI does something for you, it uses your logins and permissions. That works in a private chat because there’s only one person. Drop it into a channel with five people and it breaks. Whose access does it borrow? The intern shouldn’t get the CFO’s access just because they tagged Claude in the same channel.

The Fix

Claude gets its own identity. It posts in Slack as the Claude app, opens pull requests as the Claude GitHub App, and uses its own accounts or service accounts in your other tools, with permissions an admin sets.

Every channel starts from a workspace baseline, and admins can add more per channel. Claude might have read-only access to the data warehouse in a general channel and more in the data team’s private one. Each private channel gets its own identity, and public channels share one. (Anthropic’s write-up)

Why you care even if you’re not the admin: a teammate without database access can still ask Claude for a number in a channel cleared for it, and every action is logged under Claude’s own accounts. You get help without handing out keys. Direct messages with Claude are different. Those run on your own claude.ai account.

3 Ways Teams Win

01

Work happens while you talk

The team lands on "ship the fix and post in #launches when it’s live." Claude opens the PR and reports back when it’s done. The busywork between the decision and done stops turning into three follow-up tasks nobody wants.

02

One shared brain

Even on a Team plan, everyone used to have a private Claude that only knew their slice. Now the channel shares one Claude with the full context and channel memory. That’s the difference between five separate assistants and one actual teammate.

03

It keeps going after hours

Routines run on their own schedule, so the digest still posts and the channel still gets watched when the whole team is offline. Schedules run in UTC, so name your timezone when you set one.

How To Start

Claude Tag is in public beta for Team and Enterprise plans only. It isn’t on Free, Pro, Max or Ultra. Setup needs an Owner in your Claude organization plus a Slack workspace admin. Channel work is billed by usage from your organization’s balance rather than per seat, so Team plans need usage credits loaded first. A Microsoft Teams version is on a waitlist.

  1. Owner. Go to Organization settings, then Claude Tag (claude.ai/admin-settings/claude-tag), and click Start setup.
  2. Slack admin. Install the Claude app from the Slack Marketplace. In any channel, run /invite @Claude and then send @Claude connect by itself. Paste the pairing code it returns into the setup page within 15 minutes.
  3. Launch. Pick at least one public channel and a monthly spend limit, then click Launch Claude Tag. Add it to more channels anytime with /invite @Claude.

Anthropic’s full setup guide →

Once it’s in, paste these into a Slack thread. You talk to it like a coworker, and the more specific the format, the better the reply.

Catch Me Up
@Claude catch me up on this thread. I wasn't here for it. Give me: 1. What was decided (one line each, with who made the call) 2. What's still open or disputed 3. Every next step, with an owner and a date if one was mentioned 4. Anything that's waiting on me specifically Keep it under 10 lines. If something is unclear or nobody owns it, say so instead of guessing. Link the message each decision came from.
Bug Report To Ticket
@Claude turn the bug report above into a ticket in our issue tracker. Include: - Title (under 10 words, starts with the affected feature) - Steps to reproduce, numbered - Expected vs. actual behavior - Who reported it and any screenshots or links from this thread - Suggested priority (P0 to P3) with one sentence on why Before you file it, check whether a ticket for this already exists. If it does, post the link here and add this thread to it instead of making a duplicate. Post the ticket link in this thread when you're done.
Weekly Digest Routine
@Claude every Friday at 3pm Eastern, post a digest of this week in this channel. Format: DECIDED: one line per decision, with the owner STILL OPEN: anything unresolved, oldest first WAITING ON SOMEONE: who is blocked, and on whom NEXT WEEK: deadlines or launches mentioned in the channel Keep it under 15 lines. Skip any section that's empty, and skip the post entirely on a week with no activity. Only use what was said in this channel. Don't fill gaps with guesses.
Channel Rule
@Claude remember for this channel: when someone tags you with a request, first check whether it duplicates something already reported here. If the answer already exists, answer it directly and link where it came from. Otherwise, route it to the right owner with a one-line summary. Never promise a deadline on someone's behalf.

To see what’s scheduled, send @Claude !scheduled. To stop one, just say "disable the Friday digest."

One Smart Move

Have your admin start narrow, with read-only access in just a few channels. Then widen it one grant at a time after checking the audit trail. Point it at one noisy channel first and let it earn its spot.