Anthropic turned Claude from a personal assistant into an actual teammate that lives in your Slack. Here is what it does, why it acts as itself instead of as you, and the three ways teams get real value out of it.
The Short Version
Up to now, AI at work has been a private thing. You opened a chat, you typed, it answered, and nobody else on your team ever saw it. Helpful, but lonely. It only ever knew your corner of the work.
This update flips that. With @Claude in Slack (the feature people are calling Claude Tag), Claude stops being your private chat and becomes something the whole team can talk to in the same place they already work. You mention it in a channel, it reads the conversation everyone already shares, and it jumps in to help right there.
That sounds small. It is not. Moving AI out of a private window and into the shared channel changes what it can actually do for a team, and it forced Anthropic to rethink something most people never think about: who exactly the AI is allowed to be. Let's break the whole thing down.
@Claude in Slack lets anyone on your team tag Claude directly inside a thread or channel, the same way you'd tag a coworker. The moment you mention it, it does three things:
The mental shift
Old way: you go to the AI, in private. New way: the AI is already in the room where the work is happening, and so is everyone else. It reacts in real time, where the conversation already lives.
A few of the things teams are tagging it to do on day one:
Catch Up
Pull the decisions and open questions out of a 90-message thread you don't have time to read.
Pull Numbers
Query the data and post the metric or chart straight into the channel.
Draft a PR
Turn a bug report in the thread into a pull request without opening your editor.
Monitor
Run an automated digest and flag the urgent stuff so nothing slips.
This is the part that's actually clever, and it's the part nobody's talking about. Stay with me, because it explains why this is more than a chatbot in a sidebar.
Normally, when AI does something for you, it acts as you. It uses your logins, your permissions, your access. That works fine in a private chat, because there's only one person: you.
But the second you drop AI into a channel with five people, that model breaks. If Claude has to borrow someone's identity to act, whose does it use? There's no single person who'd be the right choice every time. The intern shouldn't get the CFO's access just because they tagged Claude in the same channel.
The fix
Instead of borrowing a person's identity, Claude gets its own. It has its own account in each tool it touches, with permissions an admin sets, not permissions inherited from whoever happened to type the message.
So in practice, Claude shows up as itself everywhere it works:
An admin decides what that identity can reach: which repos it can read or write, which tools and connectors it can use, and at what level. The clever bit is that access can be scoped per channel. Claude can have read-only warehouse access in a general channel, and write access in the data team's private one. A private channel gets its own distinct Claude identity; public channels share one workspace-level identity.
Why you should care even if you're not the admin: it means a teammate who doesn't personally have database access can still ask Claude for a number in a channel that's been cleared for it, and every action Claude takes is logged under its own accounts. You get help without handing out keys, and a clean trail of what was done.
Way 1
It Does The Work In Real Time
Your team lands on a decision in the thread, and Claude just goes and does it while everyone keeps talking. "Let's ship the fix and post in #launches when it's live." Claude drafts the PR, and posts when the deploy is done. The busywork between the decision and the done handles itself, instead of becoming three follow-up tasks nobody wants.
Way 2
One Shared Brain For The Team
Before this, even on a Team plan, everyone still had their own private Claude that only knew their slice of the work. Now the whole channel shares one Claude that has the full context and remembers what's happened there. Ask it something and it answers from the team's shared history, not from one person's private chat. That's the difference between five separate assistants and one actual teammate.
Way 3
It Never Logs Off
Because Claude acts on its own identity, it doesn't need you online to keep going. Give it a standing instruction, like watch this channel and run the weekly digest, and the work keeps moving even when the whole team is offline. Reliable AI tasks are getting longer every few months, so an agent that runs while you sleep is starting to matter a lot more than it used to.
Right now @Claude in Slack is in beta for Claude Enterprise and Team plans. An admin adds the integration to your Slack workspace, sets what Claude is allowed to reach, and then anyone in an enabled channel can tag it.
Once it's in, here are real prompts you can paste into a Slack thread to feel it out. Notice the pattern: you're talking to it like a coworker, not writing a command.
Tag it on a noisy thread
@Claude catch me up on this thread. What was decided, what's still open, and who owns each next step?
Make it do the task, not just summarize
@Claude turn the bug report above into a clean ticket: title, steps to reproduce, expected vs actual, and a suggested priority.
Give it a standing job (set and forget)
@Claude from now on, every Friday at 4pm post a digest of this channel: top decisions, anything still blocked, and who's waiting on what.
One smart move
Have your admin scope Claude tightly at first: read-only in general channels, write access only where a specific team needs it. You get the upside of an always-on teammate without handing broad access to a channel full of people. Loosen it as you learn where it actually helps.
This isn't a better assistant. It's the first time your whole team has the same teammate, one that reads the room, does the work, and keeps going after everyone clocks out. Start small, point it at one noisy channel, and let it earn its spot.
The Only AI Masterclass You Need
If this guide helped, but you’re looking to go deeper, I got you!! My 30-Day Challenge takes you from saving AI tips you never use to actually building with AI, step-by-step.
I show you exactly how I automated two e-commerce brands, my social media, and most of my personal life, then hand you the agents, workflows & systems to do the same. I’m teaching you every single thing I know with one lesson and one build a day.
Join the AI Masterclass →© 2026 Mariah Brunner. All rights reserved.