what claude tag in slack means for ops busywork
anthropic put a persistent @claude agent in slack on june 23. here is what it changes for an ops lead drowning in lookups and approvals, and what it doesn't.
claude tag. a persistent @claude agent that lives inside a slack channel. anthropic launched it on june 23, 2026. it builds memory, works async, and admins scope it to specific tools, channels, and spend limits. for an ops lead, it is a front door for lookups, routing, and small approvals. it is not the audit logic behind those approvals.
if you run operations, your day is a queue. someone asks where an order is. someone needs a refund signed off. a ticket lands in the wrong channel and sits for three hours. claude tag is anthropic's attempt to put an agent inside that queue, in slack, where the asks already happen.
anthropic launched it on june 23, 2026 as a beta for claude enterprise and team, reported by fortune. the pitch: a persistent @claude that an admin scopes to specific tools, channels, and spend limits, that keeps memory across the week, and that works while you sleep.
what does claude tag actually change for an ops lead?
← back to journal