Anthropic Embeds Claude Tag Inside Slack Channels

Anthropic launched Claude Tag on June 23, 2026 as a beta feature on Slack, available to Claude Enterprise and Team customers, according to the company's product announcement and product page. The feature lets users summon an agent with "@Claude" that can read threads, remember relevant channel context, break tasks into stages, run scheduled or long-running tasks, and post results back into Slack. Reuters reported that Anthropic plans to expand the capability to other platforms in the coming weeks and noted admin controls that let workspace admins limit which data and tools Claude Tag can access. Anthropic's announcement said, "Tagging @Claude is now one of the main ways we get things done at Anthropic. Today, 65% of our product team's code is created by our internal version of Claude Tag." Reuters also quoted Slack's Rob Seaman, who called the move "making AI multiplayer. Instead of a private back-and-forth, Claude Tag shows up in the open," and Slack's Cat Wu, who described the tagging form factor as "really powerful."

Embedding a stateful agent in Slack introduces three technical shifts teams must plan for. Persistent context and memory across channels means models operate with longer-lived state, requiring decisions on retention policies, vector-store hygiene, and eviction rules. Connectors to tools and telemetry platforms, Anthropic's product page highlights integrations with services such as GitHub, Datadog, Linear, and Gmail, turn the agent into an orchestrator that can invoke APIs and create artifacts, raising authentication, least-privilege, and audit-log requirements. Ambient proactive behavior, like scheduled digests and thread re-surfacing, shifts latency and compute patterns from sporadic API calls to sustained background tasks, affecting cost modeling and SLOs.

Industry coverage frames Claude Tag as part of a broader push by model providers to embed agents into standard enterprise workflows. The Information and The Next Web reported friction inside Salesforce, which owns Slack and promoted the integration even as some employees expressed concern about competing with Slack's own agent efforts. Regulated industries face additional friction: organizations must evaluate applicable privacy regimes, such as South Africa's Protection of Personal Information Act (POPIA), before allowing persistent agents to access workplace communications and connected data sources.

When an agent lives where people already collaborate, treat it like any other runtime service: instrument calls, log decisions, enforce least privilege on connectors, and codify retention and deletion policies. Reporting shows both enthusiastic internal adopters and skeptical stakeholders inside customer organizations, which makes cross-disciplinary governance across engineering, security, and legal the practical locus for a safe rollout.

Track what admin controls and audit logs Anthropic and Slack expose for channel-level permissions and tool connectors; whether enterprise customers centralize agent access through managed service accounts or let per-user tokens proliferate, which changes the threat model; and whether local privacy authorities or corporate legal teams require data residency, consent flows, or additional data protection impact assessments before enabling @Claude in regulated environments.