Claude Tag, launched June 23, 2026, puts a shared @claude teammate directly inside Slack. One Claude per channel, visible to everyone, learning from conversations over time. It runs on Opus 4.8.
If your team uses the legacy Claude in Slack app, you have until August 3, 2026 to migrate.
This guide covers what Claude Tag actually does, how to configure it properly, and where it falls short.
How Claude Tag Differs from Claude Code
The two tools solve different problems:
| Claude Code | Claude Tag | |
|---|---|---|
| Scope | Per-developer, local | Per-channel, team-shared |
| Interface | Terminal / IDE | Slack |
| Context | Project files, git | Channel history, connected tools |
| Invocation | Direct | @claude mention |
| Best for | Active coding | Async delegation, coordination |
Claude Code is your personal coding environment. Claude Tag is the shared team AI that watches channels, picks up tasks, and keeps working while you focus on something else.
Key Capabilities
Multiplayer by default. Within a channel, there is one Claude — not one per user. Any team member can tag it, pick up an ongoing conversation, or check what it is working on. Work is not siloed.
Persistent memory. Claude Tag builds context from channel history and connected data sources over time. You do not explain your stack from scratch every time.
Ambient mode. When enabled, Claude proactively surfaces relevant information without being tagged — flagging context from connected channels or noting that a deploy finished. This is opt-in per channel.
Async task scheduling. You can ask Claude to follow up when a condition clears: when the build passes, when a PR is merged, when someone responds. It defers and resumes.
Setup in Four Steps
Setup is admin-led. Go to claude.ai/admin-settings/claude-tag.
Step 1 — Pair the workspace. Connect Claude Tag to your Slack workspace. This requires Slack admin permissions on both sides.
Step 2 — Create access bundles. An access bundle defines which tools Claude can use in a channel. You attach bundles to channels, not to users. A typical engineering channel might include:
- GitHub (PR review, code search)
- Linear or Jira (issue lookup)
- Sentry (error log access)
- Confluence or Notion (documentation read)
A sales channel would have a different bundle entirely. Memory is scoped to the bundle: Claude in your engineering channel does not see what Claude in your sales channel knows.
Step 3 — Set spending caps. Billing is consumption-based. Set a monthly hard cap at the organizational level, with per-channel breakdowns available in the admin dashboard. Organizations that migrate from the legacy app before September 1, 2026 receive introductory credits.
Step 4 — Test in a private channel. Before deploying to active channels, run Claude Tag in a private test channel. Verify it can access the tools in its bundle and that ambient mode behaves as expected if you plan to enable it.
Configuring Access Bundles Well
The most common setup mistake is attaching too many tools to every channel. Claude Tag reads context broadly — giving it access to production databases in a general chat channel is a wider blast radius than you want.
Guidelines:
- Engineering channels: code access, issue tracker, error monitoring. Not billing, not HR systems.
- Incident channels: production logs, alerting, runbooks. Narrow and specific.
- Product channels: documentation, roadmap tools, customer feedback. Not internal compensation data.
- General / #random: no tools, or ambient-off. Claude watching casual conversation with full tool access adds noise without value.
Private channels are not reported to admins and stay private. Claude Tag respects this boundary.
Ambient Mode: When to Enable It
Ambient mode lets Claude monitor channels and speak up without being tagged. It works well in high-signal channels with ongoing operational context — incident rooms, deploy channels, on-call channels.
Enable ambient mode for:
#incidents— Claude surfaces related errors, past postmortems, open issues without being asked#deploys— Claude notes when a release completes or a check fails- Dedicated project channels with a small, focused team
Do not enable ambient mode for:
#general,#random, or high-traffic social channels- Channels where the team has not opted in to having Claude interject
- Channels with sensitive personnel discussions
Ambient mode can generate noise. The cost is not just billing — it is attention. Be deliberate.
Pairing Claude Tag with AGENTS.md
Claude Tag respects AGENTS.md files when it operates in channels connected to code repositories. If your repo has an AGENTS.md defining how AI agents should interact with the codebase, Claude Tag inherits those constraints for code-related tasks.
Use this to define:
- Which files Claude should not modify
- How it should format commit messages or PR descriptions
- Which tests it must run before declaring a task complete
This is where Claude Tag and Claude Code complement each other: Claude Code handles the hands-on editing under AGENTS.md rules; Claude Tag handles coordination, review delegation, and async follow-up at the channel level.
For reference, our rules gallery includes AGENTS.md templates across frameworks and team types.
Real Engineering Workflows
Incident response. Tag @claude in your incident channel with the error trace. It searches connected logs and documentation, proposes likely causes, and tracks open questions as the incident evolves.
Async code review. “Review this PR when you have a chance and flag anything that looks like it could break the staging build.” Claude Tag works while you are in another meeting.
Dependent work. “Once the migration lands on main, update the integration test to use the new table schema.” It waits, then acts.
Background watchers. “Let me know if anyone opens an issue related to the payment gateway this week.” Ambient monitoring without you checking manually.
What Claude Tag Does Not Do Well
Real-time pair programming. If you want line-by-line collaboration, Claude Code in your terminal is the right tool. Claude Tag is asynchronous by nature.
Stateful long-running processes. Claude Tag is not a daemon. It does not hold a persistent process open. It handles tasks and steps; not continuous runtime.
Everything in parallel. Within a channel, requests are processed one at a time. High-volume channels with many simultaneous @claude mentions can queue up.
Replace judgment on sensitive decisions. Claude Tag will flag options and surface information, but final calls on production changes, security decisions, and organizational choices stay with the team.
Migration from Legacy Claude in Slack
The old Claude in Slack app is retired on August 3, 2026. Migration window: 30 days from launch (June 23 to August 3).
Migration checklist:
- Identify which Slack channels currently use the legacy Claude app
- Decide which tools each channel needs in its access bundle
- Determine which channels should have ambient mode enabled
- Set organization-level spending cap
- Create access bundles per channel type (engineering, product, ops)
- Pair workspace at
claude.ai/admin-settings/claude-tag - Test in a private channel before rolling out to active channels
- Announce the change to teams with a short guide on how to use @claude
The migration itself takes under an hour for most organizations. The planning — deciding channel scope and tool bundles — is where the time goes.
Claude Tag vs Competing Team AI Tools
| Claude Tag | GitHub Copilot for Enterprises | Microsoft 365 Copilot | |
|---|---|---|---|
| Interface | Slack | GitHub, IDEs | Microsoft 365 apps |
| Model | Opus 4.8 | GPT-4o variants | GPT-4o variants |
| Multiplayer | Yes, per channel | No (per-user) | No (per-user) |
| Async scheduling | Yes | No | No |
| Ambient mode | Yes | No | Limited |
| Primary strength | Cross-team coordination | In-IDE code completion | Office productivity |
Claude Tag’s differentiation is the channel-scoped shared context and async scheduling — capabilities the other tools do not have in a Slack-native form.
Costs
Billing is consumption-based on Opus 4.8 token usage. Anthropic does not publish a per-message rate; pricing is governed by standard API rates for the model.
Organizations that migrate from the legacy app before September 1, 2026 receive introductory credits. A hard monthly spend cap with per-channel visibility is available in the admin dashboard.
Summary
Claude Tag works best when your team has clear channel ownership and specific, bounded tools attached to each channel. Invest the planning time in access bundle design before rollout. Enable ambient mode selectively — high-signal operational channels only.
For teams already using AGENTS.md and Claude Code for development, Claude Tag plugs into that workflow at the coordination layer: handling async follow-up, delegation, and channel-level context that Claude Code does not cover.
Migration deadline: August 3, 2026.