The short answer
Claude Tag is Anthropic's shared Claude for Slack channels. It is distinct from Claude chat, Claude Cowork, and Claude Code. Anthropic's introduction says Claude Tag entered beta for Claude Team and Enterprise. Its help page says Claude Tag replaced the earlier Claude for Slack experience on August 3, 2026.
Claude Tag and Nema overlap more than many comparisons suggest. Both can work in channel threads, remember channel context, use connected tools, follow up, and run scheduled work. The decision depends on model strategy, app identity, channel configuration, and existing controls.
Compare the operating model
| Question | Nema | Claude Tag |
|---|---|---|
| Channel identity | A separately configured coworker for each channel | One shared Claude for everyone in an enabled channel |
| Tool access | Designed around requester-owned connections and channel tool policy | Organization Agent Identity with inherited credentials |
| Memory | Separate channel and personal memory, with editable channel guidance | Channel and workspace context that admins can review, edit, and delete |
| Models | Multiple providers, pinned choices, or routing | Anthropic models |
| Governance | Named approvers, action policy, and usage administration | Guest modes, role access, audit, spend caps, and task controls |
Checked September 22, 2026. Anthropic's current Claude Tag help page is the source for current access, identity, memory, and governance details.
An incident handoff example
An engineering channel needs to hand an incident from one responder to another. The inputs include the approved timeline, messages in the incident thread, authorized issue and repository records, and the current mitigation plan. The output should distinguish facts from hypotheses and point the incoming lead to unresolved decisions.
With Nema, the incident channel can keep instructions for how to format handoffs, which systems may be read, and who must approve a proposed write. A responder asks for the handoff in the thread. Nema gathers the allowed records, cites them, and drafts a follow-up issue. The incident lead reviews the draft before any change is made. A correction to the timeline can remain with that channel's coworker for the next handoff.
Claude Tag can handle a similar shared task. Everyone in the enabled channel works with the same Claude, and Anthropic documents channel memory, organization-configured tools, scheduled tasks, proactive follow-up, and audit controls. Engineering teams that already use Claude Code and prefer Anthropic's models may value the shared vendor and first-party identity.
Choose Nema when
Choose Nema when model choice matters or different channels need distinct coworker configurations. An operations channel may use different tools, guidance, and approvers than an engineering channel. Nema is also designed for app access tied to the person asking, which can preserve the requester's existing permissions during connected work.
That identity model is worth testing with a real action. Ask who appears as the actor in the destination system, what happens when the requester lacks access, and how approval is recorded.
Choose Claude Tag when
Choose Claude Tag when the organization wants Claude specifically and already buys Claude Team or Enterprise. Anthropic documents mature controls for guest channels, organization and channel access, credential inheritance, audit, and spend caps. Claude-heavy engineering organizations may also prefer the relationship between channel work, Claude Code, and GitHub attribution.
Claude Tag's channel requests use organization consumption, while direct messages use the sender's Claude account. Confirm current model selection and pricing because both can change faster than a comparison page.
Memory and scheduled work
Both products treat shared context as more than a one-time prompt. The practical question is how people inspect and correct it. Nema puts explicit channel guidance in a team-editable place and keeps personal and channel coworkers separate. Claude Tag lets authorized administrators review, edit, or delete its memory.
Run a scheduled task in each product, then change a source or revoke access. Check what the agent does, how it reports the change, and whether a human can stop or revise the task. Test a risky action that needs approval rather than assuming scheduled work and safe execution are the same feature.
Common questions
Is Claude Tag the same as Claude for Slack?
Claude Tag is the current Anthropic product for shared Claude work in Slack. Anthropic says it replaced the prior Claude for Slack experience in August 2026.
Can Nema use Claude models?
Nema supports model choice across providers, including Anthropic models when they are configured. The selected model and available tier depend on the organization's setup.
Which product is better for guest channels?
Claude Tag currently has the clearer published controls. Anthropic documents blocked, channel-only, and full-access guest modes. Teams considering Nema should test guest and private-channel behavior against their policy before rollout.