Claude Tag
Claude Tag is Anthropic's Slack-native beta feature for Claude Enterprise and Team customers: teams can mention Claude in a channel, give it selected tool access, and let it work on tasks such as summaries, metrics pulls, ticket triage, draft PRs, and incident follow-up.
Claude Tag turns the agent question from one user chatting with a model into a team-workflow question. Readers need to understand channel context, agent identity, tool permissions, memory boundaries, and review responsibility before treating an AI teammate as part of everyday Slack work.
Anthropic's product page and launch materials describe Claude Tag as available in beta for Claude Enterprise and Team in Slack. Official sources say Claude can read threads, react in real time, run scheduled or long tasks, post results in the thread, use configured tools under its own identity, and be constrained by channel-level access. Hacker News, Reddit, and X discussion show fresh demand and friction around permissions, shared context, Microsoft Teams availability, rollout timing, and whether ambient agents belong in team channels.
- Summarize long Slack threads into decisions, owners, and next actions.
- Pull team metrics or benchmarks into the channel where the question was asked.
- Turn a bug report or incident thread into a draft PR, ticket, or triage summary.
- Monitor a channel or backlog and tag humans only when a decision is needed.
- Give teams a shared agent with admin-scoped tools instead of each person running isolated prompts.
The official Claude Tag page says teams can tag Claude into Slack threads and channels, ask it to catch up on decisions, pull numbers, draft PRs, prepare call context, monitor channels, and run tasks that take days. Anthropic presents the feature as an @Claude beta for Claude Enterprise and Team in Slack.
- Entry point: mention @Claude in a Slack thread or channel.
- Task surface: summaries, action items, metrics, draft PRs, call prep, monitoring, triage, and backlog work.
- Availability: beta for Claude Enterprise and Team in Slack, with more places to tag Claude planned.
Claude Tag is not just a chatbot in Slack. Anthropic says admins configure which tools and data Claude can access, and Claude acts under its own identity rather than borrowing a human login. That makes access review, channel scope, credential logging, and auditability the core adoption questions for teams.
- Claude can be added per channel and constrained to specific tools or resources.
- Every credential use is meant to be attributable to Claude and the requester.
- Sensitive connectors should stay confined to the channel or team that actually needs them.
The strongest community signal is not disbelief that a Slack agent can be useful; it is concern about permissions, data exposure, reliability, and ambient interruption. Hacker News comments focus on shared credentials, channel memory, Teams availability, and whether a persistent agent should be present in sensitive company conversations. Reddit adds rollout-friction language from Claude users who were already frustrated by model availability and outages.
The runtime layer of tools, memory, identity, permissions, feedback, and review around an agent.
Security review for agent capabilities, tools, skills, permissions, and reusable workflows.
Records of prompts, tool calls, observations, and outputs that make agent work auditable.
Anthropic coding agent whose workflow model Claude Tag extends into shared Slack channels.
Team agent runtime that also connects agents to Slack, GitHub, Linear, data systems, and guardrails.
AI automation platform with Slack alerts, observability, and workflow execution signals.
Claude Tag FAQ
Page-level questions for Claude Tag.
Is Claude Tag a new Claude model?+
No. Claude Tag is a Slack-native Claude feature, not a separate model. The public product job is to let teams tag Claude into a shared Slack context, grant it selected tools, and review its output in the thread.
Who can use Claude Tag?+
Anthropic lists Claude Tag as a beta for Claude Enterprise and Team customers in Slack. Teams should verify current plan availability, workspace admin controls, and tool access before assuming it is available to every Claude user.
What should admins check before enabling Claude Tag?+
Admins should check which Slack channels Claude can read, which tools and data sources it can reach, whether it uses its own account, how credential use is logged, and who reviews draft PRs, metrics, tickets, or incident actions before they affect production work.
Why are people concerned about Claude Tag?+
Community discussion centers on permission scope, company data exposure, shared context, reliability, and whether an ambient Slack agent will interrupt or help. Those concerns do not negate the official feature, but they are useful adoption questions that teams should answer before rollout.