What is Claude Tag?
Claude Tag puts one Claude in each Slack channel that everyone there can hand work to. Tag @Claude with a request and it breaks the job into stages, uses the tools an admin has connected, and posts a checklist and the result in the thread. It can open pull requests through its own GitHub app, query a data warehouse with a service account, run scheduled jobs and, in an optional ambient mode, follow up on stalled threads by itself.
Anthropic launched it on 23 June 2026, running on Opus 4.8, and it replaced the older Claude in Slack app on 3 August 2026. It is a public beta on Team and Enterprise plans only, and Slack is the only place it works. On 20 October 2026 Anthropic added an Admin API beta for managing it.
Each channel's Claude keeps memory of the work there, and credentials stay outside the sandbox it runs in. Channel work is billed by usage to an organisation balance, not per seat.
How much does Claude Tag cost?
| Plan | Price | What you get |
|---|---|---|
| Team | $25/seat/month ($20 yearly) | Channel usage paid from a prepaid balance |
| Enterprise | $20/seat/month | Plus usage, invoiced |
Needs a Claude Team (Standard seat $25/month, $20 yearly) or Enterprise ($20/seat/month plus usage) plan. Channel work is billed by usage from a prepaid or invoiced organisation balance under a monthly spend limit; no per-task price is published. One-to-one DMs bill to the sender's own seat.
Is Claude Tag worth it?
Every team has a channel where the same questions come up weekly, and a thread where a bug was reported, discussed and then quietly forgotten.
Claude Tag is built for those channels. Anyone can tag @Claude to reproduce a bug and open a draft pull request, turn a settled thread into a decision doc, or check a dashboard every morning. It posts a checklist as it works, and because each channel shares one Claude, the next person can pick up where the last one stopped. Anthropic says its internal version writes 65% of its product team's code.
The security design is better than most Slack bots. Each thread runs in its own temporary sandbox that holds no credentials; a proxy adds the key only when a request goes to a host an admin has allowed, and everything else is blocked by default. Claude acts through its own service accounts, so its actions show up as Claude's in GitHub and your other tools, and an Owner can see an activity log of what it did and who asked.
The catch: you cannot know the bill in advance. Anthropic publishes no per-task cost and tells admins to run a pilot with a spend limit and watch the per-channel breakdown. Team plans must buy credits before Claude will answer at all; invoiced Enterprise plans have no ceiling until an Owner sets one. Warnings post in the channel at 75% and 90% of the limit, and a task that would cross it is stopped, not finished.
Memory is the second trade-off. Claude keeps channel memory and session transcripts, which is why it is not available to organisations with zero data retention, customer-managed encryption or Anthropic's HIPAA configuration. Notes saved from a public channel are readable by sessions across the workspace, and anyone in a channel can use whatever a connected account can reach, so a shared credential needs a dedicated service account. Data is deleted within 30 days if you disconnect or uninstall.
Our take: Claude Tag earns its place in the channels where work already piles up, such as on-call, support intake or a busy engineering room. It is the wrong place for a finance or HR credential, because in a channel everyone shares Claude's keys.
Where it earns its place
A platform team of 15 engineers sharing an on-call channel
Have alerts looked into before someone wakes up
With Datadog or PagerDuty and the repository connected, Claude compares an alert against the last deploy and posts findings or a draft pull request in the thread. A per-channel spend limit caps what one noisy night can cost.
A support operations lead at a 60-person SaaS company
Answer the repeat questions in the internal help channel
Claude answers from connected docs such as Notion or Confluence, flags duplicates and routes the rest. Reading the channel and deciding whether to reply is not billed; only working sessions draw on the balance.
A head of IT at a 300-person fintech
Approve Claude in Slack without leaking finance credentials
Apply finance connectors to one private channel only, connect dedicated service accounts rather than personal logins, and restrict use to roles with Claude Tag access, an Enterprise-only setting. Organisations on zero data retention cannot turn it on.
Before you commit
- Setup
- An Owner of the Claude organisation runs setup at claude.ai/admin-settings/claude-tag, sends @Claude connect in Slack for a pairing code, sets a monthly spend limit and adds Claude to channels; a Slack workspace admin is usually needed to install the app.
- Integrations
- Slack only for now; the Claude GitHub App for code; connectors for tools such as Datadog, Sentry, PagerDuty, Google Drive, Notion, Confluence and data warehouses; custom HTTP connections, plugins and skills; an Admin API in beta for Enterprise.
- Data and privacy
- Channel memory and session transcripts are retained, so it is unavailable with zero data retention, customer-managed encryption or the HIPAA configuration. Slack conversations follow your Slack retention policy and are deleted within 30 days of disconnecting or uninstalling; Team and Enterprise data falls under Anthropic's commercial terms.
- Cost at scale
- Not published per task. Channel work draws from an organisation balance at list price under a monthly limit; negotiated discounts apply only at invoice time. Claude Enterprise can attribute channel spend to individual Slack users through the Analytics API.
- Limits
- Throughput limits on starting threads can block busy organisations even with budget left; files that exist only in the sandbox are lost when a thread goes idle; only Owners can set it up.
What’s good
- One shared Claude per channel that anyone can hand work to, with no Claude seat needed
- Sandboxed sessions; credentials are added by a proxy and never enter the sandbox
- Default-deny network access and its own service accounts for clear audit trails
- Opens pull requests, queries warehouses and runs scheduled checks from Slack
- Per-channel spend limits and a spend breakdown by channel
What’s not
- No published per-task cost; budgets come from a pilot
- Team plans must prepay credits before it responds
- Not available with zero data retention, customer-managed keys or HIPAA
- Public-channel memory is shared across the whole workspace
- Still a beta, and Slack only
Best for
Engineering, support and operations teams on Claude Team or Enterprise who already run their work through busy Slack channels.
Claude Tag alternatives
Claude Tag: common questions
- Is Claude Tag worth it?
- Claude Tag is the Slack bot that actually does the work, but it bills by a meter Anthropic will not price in advance and keeps memories you cannot switch off. We rate it 4.0 out of 5.
- How much does Claude Tag cost?
- Needs a Claude Team (Standard seat $25/month, $20 yearly) or Enterprise ($20/seat/month plus usage) plan. Channel work is billed by usage from a prepaid or invoiced organisation balance under a monthly spend limit; no per-task price is published. One-to-one DMs bill to the sender's own seat.
- What are the downsides of Claude Tag?
- No published per-task cost; budgets come from a pilot; team plans must prepay credits before it responds; not available with zero data retention, customer-managed keys or HIPAA; public-channel memory is shared across the whole workspace; still a beta, and Slack only.
- Who is Claude Tag best for?
- Engineering, support and operations teams on Claude Team or Enterprise who already run their work through busy Slack channels.
- How much does Claude Tag cost for a team or in production?
- Not published per task. Channel work draws from an organisation balance at list price under a monthly limit; negotiated discounts apply only at invoice time. Claude Enterprise can attribute channel spend to individual Slack users through the Analytics API.
- Is Claude Tag safe for company data?
- Channel memory and session transcripts are retained, so it is unavailable with zero data retention, customer-managed encryption or the HIPAA configuration. Slack conversations follow your Slack retention policy and are deleted within 30 days of disconnecting or uninstalling; Team and Enterprise data falls under Anthropic's commercial terms.
- What are the best Claude Tag alternatives?
- The closest alternatives we have reviewed are Claude Cowork, Devin (incl. Devin Desktop, formerly Windsurf), Lindy and Grok Bot.
Answers checked Nov 6, 2026.
Make Claude Tag? Show this rating on your site
