Skip to main content
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.

# platform-eng38 members
Dana2:14 PM

checkout has felt slow all morning — anyone else seeing it?

Leo2:15 PM

same. @Claude can you investigate? Compare latency against this morning’s deploy and find what’s causing it.

ClaudeAPP2: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 DatadogDone: Diffed deploy 4f2c1 against mainDone: Reproduced the slow query locallyIn progress: Opening a pull request with the fix…

Where Claude Tag runs

Claude Tag works in Slack. You interact with it by mentioning @Claude in a Slack channel, thread, or direct message, and it replies there. 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.

Billing and spend limits

Claude Tag is consumption-based. Usage is metered as model usage, the same way Claude Code is. For channel and thread messages, usage draws from your organization’s usage balance rather than from individual seats or API credits. For direct messages, usage bills to that user’s own seat, so the organization spend limit does not apply. Cost depends on how much your team uses Claude. You manage spend in three steps:
  • Start with your usage credit: an initial usage credit, available through September 1, 2026, lets you try real workflows and see what fits your team before you commit more budget.
  • Watch usage as you go: the usage page in Claude Console shows what Claude has consumed against your balance, with a per-channel breakdown.
  • Set a spend limit: an Owner sets a hard cap on Claude’s draw from the usage balance, so usage cannot exceed what you have approved.
How the balance is funded depends on your plan. Team plans buy usage credits in Claude Console, and Enterprise plans are invoiced. See set a spend limit for the full setup.
For end users

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: 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? 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.
For administrators

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 (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.

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