Work with Claude Tag

Claude Tag puts Claude in your Slack channels with admin-governed access. See what to hand it, how setup works, and where to start as an admin or end user.

Claude Tag: Public Beta. 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.

Example thread (#platform-eng, 38 members):

• Dana (2:14 PM): checkout has felt slow all morning — anyone else seeing it?
• Leo (2:15 PM): same. @Claude can you investigate? Compare latency against this morning's deploy and find what's causing it.
• Claude (APP, 2:15 PM): On it. I'll compare latency before and after the deploy, track down the cause, and report back here.
  • Done: Pulled p99 latency from Datadog
  • Done: Diffed deploy 4f2c1 against main
  • Done: Reproduced the slow query locally
  • In progress: Opening a pull request with the fix…

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 works for 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 administrators — Provision the identity

• Where do I start? — The four setup steps, what to have ready, and what to test first
• What can Claude Tag access? — Why access follows the channel, and where credentials are stored
• How do I connect each service? — Credential types, allowed hosts, and what each connection lets Claude reach

For end users — Put 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
• How do I get good results? — Good habits for scoping and reviewing work
• What does Claude Tag remember? — Channel memory, what's shared across the workspace, and who can see what
• 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 a usage balance, an amount in your organization's billing currency that an Owner funds. A spend limit caps 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. Your organization may already have a launch usage credit to run that pilot against before it funds the balance itself.

Set a spend limit covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.

Put Claude Tag to work (for end users)

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: see Set 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 (for administrators)

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 (an Access bundle), and which workspaces and channels they apply to.

You configure this once, at claude.ai/admin-settings/claude-tag, and everyone in those places can use Claude Tag immediately, with no per-user setup. You must be an Owner in your Claude organization to run setup.

Set up Claude Tag walks 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.

Where to start with Claude Tag

• Set up Claude Tag — Admins: provision the identity and connect your first channel
• Hand Claude Tag your first task — It's already in your channel: send your first message
• How Claude Tag works — The session model, what it can read, and how memory follows places
• Use case library — Prompts to paste, by team and connection