Tag @Claude in. Get results back in the thread.
Anyone in a channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.
checkout has felt slow all morning — anyone else seeing it?
same. @Claude can you investigate? Compare latency against this morning’s deploy and find what’s causing it.
On it. I’ll compare latency before and after the deploy, track down the cause, and report back here.
Where Claude Tag runs #
Claude Tag works in Slack. You interact with it by writing in a Slack channel, thread, or direct message, and it replies there. Mention@Claude
in a channel to guarantee it picks the message up. When Claude works on a task, it runs in an ephemeral sandbox hosted by Anthropic, not on your computer or inside your network. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See how Claude Tag worksfor the full lifecycle. You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through
connections, plugins, and skills. An Owner configures these per scope (a channel, a workspace, or the whole organization), separately from any connectors an individual user has set up in their own claude.ai account.
For end usersPut Claude Tag to work How do I hand Claude Tag a task?Mention Claude in any channel it’s in, with nothing to install
[What is Claude Tag good at?Use cases for coding, data, incidents, and GTM](/docs/claude-tag/users/use-cases)
[How do I get good results?Good habits for scoping and reviewing work](/docs/claude-tag/users/good-habits)
Can Claude Tag run tasks on a schedule?Scheduled jobs, channel watching, and triggers
Billing and spend limits #
Adding Claude to Slack doesn’t add a per-seat charge. Channel and thread work is billed by usage instead: it draws from ausage balance, an amount in your organization’s billing currency that an Owner funds. A
spend limitcaps how much of that balance Claude Tag can use each billing period. Direct messages don’t draw from this balance. A DM runs on the sender’s own claude.ai account and follows that seat’s usual usage limits, so the organization spend limit doesn’t apply to it. To learn what your team’s usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the
[usage page in your admin settings](https://claude.ai/admin-settings/usage/claude-in-slack). Your organization may already have a
[launch usage credit](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise)to run that pilot against before it funds the balance itself.
Set a spend limitcovers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.
Put Claude Tag to work #
If Claude Tag is in your channel, you can use it now. (If it isn’t there yet, an Owner in your Claude organization runs setup: seeSet up Claude Tag.) Anyone in the channel can hand it work, and channel work bills to the organization, not to you. What it can reach depends on the channel you’re in, not on who you are. The fastest way to find out is to ask it:
@Claude what can you access from this channel?
Or, if you’re signed in to your Claude organization, click Configure in the footer of any Claude reply to see the channel’s connections. The one exception is a DM, where it runs on your own claude.ai account instead of the channel’s setup. Admins can disable DMs organization-wide; see
Allow or disable direct messages. Begin with Get started, which covers your first message, what you see while it works, and how to shape its behavior in your channel.
Set Claude Tag up once for everyone #
Installing the Claude app in Slack is a prerequisite, not the setup. Setup is provisioning an identity. Claude Tag starts with no access to your external systems; you choose its credentials and repositories (anAccess bundle), and which workspaces and channels they apply to. You configure this once, at
claude.ai/admin-settings/claude-tag
Set up Claude Tagwalks the four provisioning steps, from creating the identity to attaching it to your first channel.
Security review
Security and data handling The security model, what admins can and can’t restrict, audit trails, and network requirements.