← All agent and harness briefs
Agent runtimeagenticopscodingdocumentedunattended capable

Operational brief

Claude Tag

Anthropic's Slack-native shared Claude for scoped tools, persistent channel context, routines, and asynchronous team work.

No product visual on file

Choose it when

You already run Claude Team or Enterprise and want a shared Slack agent with scoped access, routines, and an organization spend limit.

Skip it when

You need Microsoft Teams, individual-plan access, Zero Data Retention, CMEK, or admin-added connectors inside self-hosted sessions.

01 / Classification

Autonomy evidence

This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.

How we classify it
Tool use + multi-step plans, still human-gated per session.
Runs unattended
Yes — that capability is documented in this brief.
Trigger
Primary use starts with an @Claude mention and a shared working session. Optional routines run on schedules or channel watches; GitHub subscriptions wake only for a single named PR.
State
Channel notes and session transcripts persist; files only in the sandbox don't. Save deliverables to Slack or a branch rather than treating a resumed thread as a persistent disk.
Tools
Can post Slack results, run code, edit sandbox files and push branches/PRs; configured channel connectors add external actions. Admin-added connectors aren't usable in self-hosted runner sessions.
Human control
Channel members can steer or stop a working session; DMs lack the Stop button. Anyone in the channel can pause/stop routines. Assign an owner to review runs and failures; completion/failure notices require the creator's linked account. This isn't a universal per-write approval gate.

02 / Operations

Control reality

Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.

Where it runs
First-party Slack service with ephemeral hosted sandboxes; security docs also describe runner environments inside your network, without admin-added connectors in those sessions.
Data boundary
Transcripts and channel memory are retained even when a sandbox is released. In hosted environments, outbound requests use Agent Proxy and configured allow layers; default Trusted access includes developer hosts, not zero egress.
Identity & permissions
Channel service-account access is shared by all members where it applies. Linked one-to-one DMs use the member's account; personal connectors in channels apply to that user's tasks after consent, not everyone's requests.
What it can write
Slack replies · files and code in its ephemeral sandbox · actions through administrator-connected tools
Surfaces
Slack channels and threads · Slack direct messages · Anthropic ephemeral sandbox · Scoped connections, plugins, and skills
Export / lock-in
Not recorded yet.

03 / Receipts

Evidence ledger

Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.

Evidence status
documented
Source set
6 primary sources
Evidence review
2026-10-14

Sources on file

Corrections

  • 2026-10-14 · Primary facet now reflects mention-triggered shared sessions; autonomous routines remain optional. Replaced blanket no-self-hosting fit with the documented runner/admin-connector limit. Clarified durable transcripts versus ephemeral files, shared channel identity, and routine timing/owner/notice boundaries; not runtime-tested.

Desk notes

What we found

Useful context, not a substitute for the source record above. This is not a desk test unless the evidence status says tested.

Choose it for shared Slack work, not private per-user authority. Optional routines need an owner after setup.

Primary mode
Mention-triggered shared sessions
Optional work
Schedules, channel watches, single-PR subscriptions
State
Durable transcripts; ephemeral sandbox files
Runner limit
No admin-added connectors in self-hosted sessions

What the vendor says

Current docs describe shared channel access and separately scoped personal connectors; don't assume each member brings only their own permissions.

Sources fetched 2026-10-14

04 / Change log

Related coverage

The brief tells you what the product is. Payloads track the changes that may alter the decision.

No linked change coverage on file yet.