How Claude Tag works changedclaude-tag/concepts/how-it-works
Nearest release: v2.1.283, published 10 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 26 Sep 2026 05:33 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+31added
Lines−31removed
From line
114
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 114, old and new numbered
/
from line 114
114114
115115Where you message Claude determines whose tools and accounts it uses. In a channel, it acts with the connections an organization admin set for that channel, and the work is attributed to its own accounts. In a DM, the same engine runs with your own claude.ai connectors, and the work is attributed to you, except pull requests, which the Claude GitHub App authors from DMs as well.
116116
117| Working in… | Access | Attribution | Best for |
118| :---------- | :----------------------------------------- | :----------------------- | :--------------------------------- |
119| A channel | The channel's connections, set by an admin | The agent's own accounts | Shared work the team should see |
120| A DM | Your own claude.ai connectors | You | Personal tasks using your own data |
117| Working in… | Access | Attribution | Best for |
118| :- | :- | :- | :- |
119| A channel | The channel's connections, set by an admin | The agent's own accounts | Shared work the team should see |
120| A DM | Your own claude.ai connectors | You | Personal tasks using your own data |
121121
122122The Access column is about external systems. A channel session reaches what the channel was granted, and a DM session reaches what your own account is connected to.
123123
from line 127
127127
128128Anthropic offers several ways to work with Claude on real tasks; they reach the same kinds of systems but through different mechanisms.
129129
130| | Claude Tag | Cowork | Claude Code |
131| :---------------- | :---------------------------------------------------------------- | :------------------------------------ | :------------------------------------------- |
132| Where | Slack channels | claude.ai chat | Your terminal or IDE |
133| Whose access | The team's: service-account credentials an admin sets per channel | Yours: your personal OAuth connectors | Yours: your local credentials and filesystem |
134| Who sees the work | Everyone in the channel | Just you | Just you |
135| Best for | Shared work the team should see and steer | Personal research and drafting | Hands-on coding in your own checkout |
130| | Claude Tag | Cowork | Claude Code |
131| :- | :- | :- | :- |
132| Where | Slack channels | claude.ai chat | Your terminal or IDE |
133| Whose access | The team's: service-account credentials an admin sets per channel | Yours: your personal OAuth connectors | Yours: your local credentials and filesystem |
134| Who sees the work | Everyone in the channel | Just you | Just you |
135| Best for | Shared work the team should see and steer | Personal research and drafting | Hands-on coding in your own checkout |
136136
137137The short version: **team work → Claude Tag; personal work → Cowork or Claude Code.** Claude Tag's connections authenticate the agent itself with service accounts, not any person. Personal connectors apply in a Claude Tag DM, which runs on your own claude.ai account, the same way Cowork does.
138138
from line 176
176176
177177Claude posts each session's result in the thread you asked in, choosing the form that fits the work.
178178
179| Form | What it is | When you see it |
180| :------------------ | :------------------------------------------------------ | :--------------------------------- |
181| A reply | An answer, list, or summary as a Slack message | Questions and short results |
182| A file or chart | Attached to the thread the way anyone shares a file | Data, images, generated documents |
183| A page kept current | Any of the above, edited in place over time | Digests, indexes, standing reports |
184| A hosted page | A web page published on claude.ai, linked in the thread | Dashboards, prototypes, reports |
179| Form | What it is | When you see it |
180| :- | :- | :- |
181| A reply | An answer, list, or summary as a Slack message | Questions and short results |
182| A file or chart | Attached to the thread the way anyone shares a file | Data, images, generated documents |
183| A page kept current | Any of the above, edited in place over time | Digests, indexes, standing reports |
184| A hosted page | A web page published on claude.ai, linked in the thread | Dashboards, prototypes, reports |
185185
186186A hosted page stays available after the session ends, and Claude updates it when you ask in the thread. Anyone with access to the channel can open it. [Artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) covers the access model. These are the same artifacts [Claude Code publishes](https://code.claude.com/docs/en/artifacts), with channel-based access in place of owner-controlled sharing.
187187
from line 213
213213
214214Where you ask decides what Claude can do in the other channel:
215215
216| Where you ask | Read the other channel | Post, reply, or react there |
217| :---------------- | :------------------------------------------------- | :------------------------------------------------------------------- |
218| A public channel | Yes, unless the channel you ask in includes guests | Yes |
219| A private channel | Yes, unless the channel you ask in includes guests | No |
220| A DM with Claude | Yes | New top-level posts only, each after you select **Approve and post** |
216| Where you ask | Read the other channel | Post, reply, or react there |
217| :- | :- | :- |
218| A public channel | Yes, unless the channel you ask in includes guests | Yes |
219| A private channel | Yes, unless the channel you ask in includes guests | No |
220| A DM with Claude | Yes | New top-level posts only, each after you select **Approve and post** |
221221
222222* **Attribution line**: every message Claude posts outside the conversation you asked from carries a line under it that names where it came from. When you ask in a thread, the line links back to that thread and names whoever last addressed Claude there, as in "Sent by Claude in #team-eng on behalf of @jordan". When you ask in a DM, the line names the person who approved the post, as in "Sent by Claude, approved by @jordan".
223223* **Replies**: replies under a message Claude posted in another channel don't reach the session you asked in. To follow up on the original task, reply in the thread where you asked.
from line 243
243243
244244A thread is durable, but the sandbox behind it is not. Durable means the thread stays in Slack, and everything Claude read and said in it is kept in the session's transcript on Anthropic's side, so the session can pick up where it left off whenever someone replies. Deleting messages or the thread in Slack doesn't remove them from that transcript. The sandbox is the computer where Claude runs commands and keeps working files for a task. A few minutes after a session finishes its turn, its sandbox is released, and the same session resumes in a fresh one when the next message arrives. A thread's session keeps resuming this way for as long as people use the thread. Claude replaces it with a new session in two cases.
245245
246| When | What Claude does |
247| :-------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------- |
248| Someone sends [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) | Archives the session right away and starts a fresh one that rereads the thread |
249| The session [gets stuck and fails](/docs/claude-tag/users/troubleshooting#claude-reacted-or-started-thinking-then-never-replied) | Starts the replacement when the next message arrives in the thread |
246| When | What Claude does |
247| :- | :- |
248| Someone sends [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) | Archives the session right away and starts a fresh one that rereads the thread |
249| The session [gets stuck and fails](/docs/claude-tag/users/troubleshooting#claude-reacted-or-started-thinking-then-never-replied) | Starts the replacement when the next message arrives in the thread |
250250
251251<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/session-lifecycle.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=9a56231787b03f179e8d552d887778fc" alt="Timeline with two lanes. The Slack thread lane is one continuous bar that persists from the moment a task starts. The sandbox lane below it is segmented, built when the task starts, released while the thread goes quiet, and rebuilt fresh when someone replies." width="1000" height="270" data-path="images/claude-tag/diagrams/session-lifecycle.svg" />
252252
253253<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/session-lifecycle-dark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=0693a90b98baa729dcacfd35261f6494" alt="Timeline with two lanes. The Slack thread lane is one continuous bar that persists from the moment a task starts. The sandbox lane below it is segmented, built when the task starts, released while the thread goes quiet, and rebuilt fresh when someone replies." width="1000" height="270" data-path="images/claude-tag/diagrams/session-lifecycle-dark.svg" />
254254
255| | Survives idle periods |
256| :------------------------------------- | :---------------------------------- |
257| The conversation and its context | Yes |
258| Channel memory | Yes |
259| Work pushed, posted, or opened as a PR | Yes, in the external system |
260| Files that exist only in the sandbox | No. Claude recreates them if asked. |
255| | Survives idle periods |
256| :- | :- |
257| The conversation and its context | Yes |
258| Channel memory | Yes |
259| Work pushed, posted, or opened as a PR | Yes, in the external system |
260| Files that exist only in the sandbox | No. Claude recreates them if asked. |
261261
262262For long tasks, ask it to push branches and post drafts as it goes, so deliverables are saved somewhere durable while the work is still running. See [Good habits](/docs/claude-tag/users/good-habits#give-every-task-a-definition-of-done).
263263
No line in this hunk matches that.