# Introducing Claude Tag

Source: [Anthropic](https://www.anthropic.com/news/introducing-claude-tag)  
Feed7 permalink: https://feed7.dev/p/introducing-claude-tag-042b1r5  
Published: Unknown  
Trust: Official Source (official_source)

## Why Included

Claude Tag puts a persistent Claude in Slack channels: tag @Claude to delegate async tasks running hours or days on Opus 4.8. Beta for Team/Enterprise; Anthropic says it writes 65% of its product team's code.

## Source Summary

**The gist** **Claude Tag** launched in beta **June 23, 2026** for Claude Team and Enterprise: one Claude instance per Slack channel, where anyone can tag **@Claude** to delegate tasks that run asynchronously for **hours or days** on **Opus 4.8**, with per-channel access to tools, data, and codebases. It replaces the old Claude-in-Slack app with a **30-day migration** window.

## Practical Implication

**Why it matters** This is agent-as-teammate rather than agent-as-tool: Claude accumulates context by following channel activity and, when enabled, proactively flags information and follows up on unresolved tasks. Anthropic claims **65%** of its product team's code now comes from its internal version — a marker of where delegated-agent workflows are heading.

## Agent-Ready Context

**The gist** **Claude Tag** launched in beta **June 23, 2026** for Claude Team and Enterprise: one Claude instance per Slack channel, where anyone can tag **@Claude** to delegate tasks that run asynchronously for **hours or days** on **Opus 4.8**, with per-channel access to tools, data, and codebases. It replaces the old Claude-in-Slack app with a **30-day migration** window.

**Why it matters** This is agent-as-teammate rather than agent-as-tool: Claude accumulates context by following channel activity and, when enabled, proactively flags information and follows up on unresolved tasks. Anthropic claims **65%** of its product team's code now comes from its internal version — a marker of where delegated-agent workflows are heading.

**Watch out** Admins scope tools and data per channel into **separate Claude identities**, and Claude **does not report from private channels** — but a long-lived agent reading team chat is a real governance surface. It is **Slack-only** for now; token spend limits and task logs are your controls.

## Context Map

- Layer: tools
- Domains: coding
- Topics: cloud-agents, enterprise

## Uncertainty

- Admins scope tools and data per channel into **separate Claude identities**, and Claude **does not report from private channels** — but a long-lived agent reading team chat is a real governance surface. It is **Slack-only** for now; token spend limits and task logs are your controls.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.