Shared engineering tasks
Investigate bugs, prepare code changes, open pull requests, or summarize technical context in a visible team thread.
Independent tool overview
Claude Tag at a glance
Claude Tag is Anthropic's beta Slack agent for Claude Team and Enterprise organizations, letting channels delegate tool-using work to a shared @Claude identity with scoped memory, scheduled tasks, proactive follow-up, and audit controls.
Visit the official Claude Tag site ↗
- Product type
- Shared agentic AI teammate in Slack
- Availability
- Beta on Claude Team and Enterprise
- Current platform
- Slack
- Migration date
- Replaced the earlier Claude in Slack experience on August 3, 2026
- Surfaces
- Channel mentions, direct messages, and Slack assistant panel
- Setup authority
- Claude Primary Owner or Owner; Admin alone cannot set it up
- Channel billing
- Consumption-based and charged to the organization
- Direct-message billing
- Charged to the individual Claude account
- Memory
- Retained by workspace and channel; reviewable and deletable by admins
- Spend controls
- Organization and per-channel hard caps with 75% and 95% alerts
Overview
What Claude Tag is
Claude Tag moves Claude from a private chat into Slack as a shared, asynchronous teammate. In a configured channel, anyone with access can mention @Claude, assign a task, watch its plan and progress in a thread, and continue from the same channel memory. Owners can connect repositories and workplace tools, let Claude schedule longer-running work, and optionally enable ambient behavior that proactively surfaces information or follows up on stalled threads.
That collaboration model is powerful because the agent can act with organization credentials rather than one employee's account. It is also the central risk. A broadly configured channel can turn a casual Slack message, malicious pasted content, guest access, or mistaken instruction into repository changes, external calls, data exposure, or spend. Claude Tag should be deployed as a privileged service identity with narrow scopes, isolated channels, hard budget limits, human approval for consequential actions, and continuous audit review.
Use cases
Who Claude Tag is best for
The strongest fit depends on the job you need the product to complete, not the size of its feature list.
Support operations
Research cases, connect approved systems, draft responses, and follow unresolved threads under human review.
Data and metrics requests
Let authorized channel members delegate repeatable queries against approved data sources.
Long-running work
Schedule multi-stage research, analysis, or coding work that runs asynchronously and reports back.
Team knowledge continuity
Retain useful channel context so the agent does not need the same project explanation on every task.
Proactive follow-up
Use ambient behavior to surface relevant updates or prompt owners when a thread appears unresolved.
Governed AI rollout
Provide central permissions, spend limits, channel isolation, guest controls, and an audit trail.
Capabilities
Core Claude Tag features
Channel mentions
Starts visible work when someone tags @Claude and returns progress and results in the Slack thread.
Shared channel identity
Everyone in a channel interacts with the same Claude context and can steer or continue the work.
Direct messages
Supports private conversations using the individual's enabled Claude tools and connectors.
Slack assistant panel
Opens Claude in Slack's side panel without requiring a channel mention.
Persistent scoped memory
Remembers relevant information by workspace and channel instead of starting each task from zero.
Tool and repository access
Uses organization-configured credentials, services, and code repositories to complete tasks.
Agent Identity
Acts under a distinct organization identity so posts, commits, pull requests, and network calls can be attributed.
Asynchronous tasks
Works in stages while people continue other work and reports back when finished.
Scheduled work
Can create recurring or future tasks that continue over hours or days.
Ambient behavior
Optionally checks in proactively, surfaces relevant information, and follows up on stalled work.
Layered permissions
Applies organization-wide, workspace, and private-channel credentials and repository scopes through inheritance.
Guest-channel controls
Lets owners block Claude, restrict it to channel-only access, or allow full configured access when Slack guests are present.
Spend limits
Provides organization-wide and per-channel hard caps, inherited defaults, threshold alerts, and channel analytics.
Memory controls
Lets admins inspect, edit, and delete what Claude remembers for a channel or workspace.
Audit view
Lists one-time and scheduled tasks plus Agent Identity network calls and the user who requested each action.
Process
How the Claude Tag workflow works
Step 1
Select a bounded pilot
Choose one high-value, reversible workflow with clear inputs, allowed tools, output, owner, and success measure.
Step 2
Create a dedicated identity
Have a Primary Owner or Owner provision Claude Tag separately from any human's broad personal credentials.
Step 3
Start with least privilege
Grant only the repositories, read scopes, write scopes, environments, and data needed for the pilot.
Step 4
Isolate the channel
Use a private test channel, verify membership and guests, and avoid inheriting unrelated workspace-wide credentials.
Step 5
Define approval gates
Require an accountable person before messages, ticket changes, merges, deployments, purchases, deletions, or sensitive data exports.
Step 6
Set hard spend caps
Apply a conservative organization cap, default per-channel cap, and named process for reviewing increase requests.
Step 7
Test adversarially
Try ambiguous requests, malicious pasted instructions, cross-channel questions, guest presence, stale tasks, and credential failures.
Step 8
Inspect every action
Review Slack threads, commits, pull requests, downstream system logs, network calls, memory, and spend during the pilot.
Step 9
Control standing work
List active triggers regularly, assign an owner, set an expiration date, and disable recurring tasks that no longer have a purpose.
Step 10
Expand by identity
Create separate scoped configurations for engineering, sales, legal, and other domains instead of one all-powerful Claude.
Cost
Claude Tag pricing and free plan
Claude Tag requires a Claude Team or Enterprise organization and adds consumption-based channel charges. Team seat prices are published, but Tag usage is not a flat per-seat add-on: channel tasks draw from the organization's usage balance, while direct messages draw from the individual's Claude account. Set hard limits before enabling it. U.S. Team prices below exclude tax; Enterprise seat and usage pricing requires the applicable live plan or sales quote.
Team Standard
$25/user/month monthly or $20/user/month annually
Base Team seat that makes the beta available to an eligible organization.
- Two-member minimum
- U.S. price excluding tax
- Team supports up to 150 seats
- Claude Tag channel consumption is additional
- Usage credits can extend work beyond included seat limits
Team Premium
$125/user/month monthly or $100/user/month annually
Higher-capacity Team seat for power users; organizations can mix Standard and Premium seats.
- U.S. price excluding tax
- Higher per-session and weekly capacity than Standard
- Claude Tag channel work still bills to the organization rather than a user's seat
- Direct-message work bills to the sender's account
Enterprise
Check live quote or checkout
Advanced governance and consumption model for larger or regulated organizations.
- Seat fee plus usage-based billing on current Enterprise plans
- Enterprise-only role-based control for Claude Tag access
- Advanced security, identity, compliance, and custom-role features
- Claude Tag has separate organization and channel spend controls
Claude Tag channel usage
Consumption-based
Variable organization charge based on the work delegated in Slack.
- Not priced as a flat fee per Slack user
- Organization-wide hard cap
- Per-channel limits and inherited defaults
- Alerts at 75% and 95%
- Work exceeding a limit is declined rather than silently truncated
Pricing checked . Check current pricing at the source ↗
Assessment
Claude Tag strengths and limitations
Where it stands out
- Lets a whole channel collaborate with one visible agent instead of forwarding results from private chats
- Persistent channel context reduces repeated project explanation
- Asynchronous and scheduled work supports tasks longer than a normal Slack exchange
- Ambient follow-up can surface stalled work and relevant updates
- Organization-owned Agent Identity improves attribution across Slack, GitHub, and connected tools
- Permissions and memory can be separated by workspace and private channel
- Guest-channel handling includes a restrictive default
- Hard organization and channel spend caps reduce runaway-cost risk
- Audit view includes tasks, requester attribution, and Agent Identity network calls
- Admins can inspect, edit, and delete Claude Tag memory
- Direct messages remain separate from channel work and use personal Claude tools
- The beta is available to both Team and Enterprise organizations
What to consider
- Claude Tag is a beta product and currently works only in Slack
- It requires a paid Claude Team or Enterprise organization in addition to variable channel consumption
- Only a Primary Owner or Owner can configure Claude Tag; the Admin role alone cannot
- Team plan role-based member restriction is less granular than Enterprise custom-role access
- Channel permissions inherit organization and workspace credentials, so an overly broad parent scope affects many channels
- Anyone allowed to use Claude in a channel can potentially steer shared work within the configured authority
- A prompt, pasted document, issue, webpage, or tool response can contain malicious or misleading instructions
- Tool-using models can select the wrong repository, record, customer, environment, or action
- Generated code can contain security defects, regressions, destructive migrations, or weak defaults
- Proactive ambient behavior can create noise, reveal information, or revive work that should remain closed
- Scheduled tasks can outlive the project, owner, permission need, or original assumptions
- Shared memory can preserve outdated, incorrect, sensitive, or biased context until an admin edits or deletes it
- Private-channel credentials are added on top of inherited scopes rather than automatically replacing them
- Using full access in channels with Slack guests can expose connected data or capabilities outside the intended employee group
- Slack messages can be edited, deleted, quoted, or taken out of context, weakening them as the only authorization record
- Channel work and direct-message work have different identities, tools, memories, visibility, and billing, which users must understand
- Slack conversations remain under Slack retention rules even though Anthropic deletes integration conversations within 30 days after disconnection
- Slack-initiated conversations do not appear in Claude chat history, and Claude web conversations are not available in Slack
- Spend is usage-based and long, tool-heavy, or repeatedly scheduled tasks can consume substantial budget
- Hitting a hard limit blocks new work and can interrupt an operational workflow
- Auditing shows what happened but does not prevent every bad or irreversible action
- Production changes, customer communications, financial decisions, legal work, access grants, and deletions still need explicit human authorization
Compare
Claude Tag alternatives
The right alternative depends on the specific output, workflow, controls and budget your project requires.
Consumer
Slackbot
Choose Slackbot for Slack's native personal AI agent and tighter alignment with Slack's own product experience.
Explore Slackbot →Coding
Slack Code
Choose Slack Code when the main need is a team software-development channel built around multiple coding agents.
Explore Slack Code →Project Management
Claude
Choose standard Claude when private chat, Projects, Code, or Cowork is sufficient and shared Slack identity is unnecessary.
Explore Claude →Questions
Claude Tag FAQs
What is Claude Tag?
Claude Tag is Anthropic's shared agent in Slack. Team members mention @Claude to delegate work using channel context, organization tools, persistent memory, scheduled tasks, and a distinct Agent Identity.
Who can use Claude Tag?
It is currently available in beta to Claude Team and Enterprise organizations. A Primary Owner or Owner must set it up and choose who and which channels can use it.
Did Claude Tag replace Claude in Slack?
Yes. Anthropic says the earlier Claude in Slack experience switched to Claude Tag on August 3, 2026.
How much does Claude Tag cost?
It requires Team or Enterprise access, then channel work is billed to the organization's usage balance based on consumption. Direct messages are billed to the individual's Claude account.
Does Claude Tag remember Slack conversations?
Yes. It retains relevant memory scoped to workspaces and channels so future tasks can use prior context. Admins can inspect, edit, and delete that memory.
Can Claude Tag access private channels?
Only channels and tools configured by an Owner or Primary Owner. Private channels can add credentials and repositories on top of inherited organization and workspace scopes.
What happens when a Slack guest is in the channel?
Owners can block Claude entirely, allow channel-only access, or permit full configured access. Restrict is the default and is the safer starting point.
Can Claude Tag write code and open pull requests?
Yes, when given the necessary repository and tool access. Commits and pull requests can be attributed to the Claude GitHub App, but humans must review tests, security, and change scope before merge.
Can Claude Tag run recurring tasks?
Yes. It can schedule work and follow up later. Teams should inventory active triggers, assign owners and expiration dates, and remove stale automation.
How are Claude Tag costs controlled?
Owners can set an organization hard cap, per-channel caps, inherited defaults, and alerts at 75% and 95%. A task that would exceed the limit is declined.
Is Claude Tag safe for production access?
Only under a carefully scoped control model. Use a dedicated identity, least privilege, isolated channels, guest restrictions, approval gates, sandboxed environments, hard spend limits, and continuous audit review.
Bottom line
Our Claude Tag verdict
Claude Tag is a meaningful step beyond a Slack chatbot: shared memory, a distinct identity, connected tools, long-running tasks, and proactive follow-up can make it useful operational infrastructure. Those same features make it a privileged agent rather than a convenience bot. The best deployments begin with read-only, reversible work in isolated channels and expand only after permissions, guests, memory, scheduled tasks, spend, and audit behavior have been tested.
Visit Claude Tag website ↗Similar Business Operations Tools
View all Business Operations AI tools →
Mistral OCR 4.1
Mistral OCR 4 - Mistral’s OCR model with layout-aware document understanding
Mercury 2
🗣️ Mercury 2 - Inception's diffusion reasoning model built for realtime voice agents
Meta Business Agent
Meta Enterprise Agent - AI agent for customer sales and support across Meta's apps
Presence
Presence - OpenAI's managed enterprise service deploying chat and voice agents
AI training for the future of work.
Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.
AI Courses
Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.
Daily Guides
To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.
Workshops
Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.
Community
Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.