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 26 Sep 2026 05:37 UTC.
Upstream edited
Recorded here
Lines+20added
Lines−2removed
From line
16
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits15to this page, all time
### What Claude can do in other channels
The whole hunk
from line 16, old and new numbered
/
from line 16
1616* [Starting a session](#start-a-session), [tracking progress](#track-claude%E2%80%99s-progress), and [steering mid-thread](#reply-in-the-thread-to-steer): what to type, what to watch, and who can redirect
1717* [Team channels and personal DMs](#team-channels-and-personal-dms): which surface to use, and how access differs between them
1818* [Key concepts](#key-concepts): agent identity, scheduling, and memory defined
19* [Lifecycle of a request](#lifecycle-of-a-request): the five-step loop, [the checklist](#how-the-checklist-updates), [per-channel access](#channel-access), and [scheduled tasks](#one-off-and-scheduled-tasks)
19* [Lifecycle of a request](#lifecycle-of-a-request): the five-step loop, [the checklist](#how-the-checklist-updates), [per-channel access](#channel-access), [other channels](#what-claude-can-do-in-other-channels), and [scheduled tasks](#one-off-and-scheduled-tasks)
2020* [Session context and memory](#session-context-and-memory): what Claude reads, what survives idle, and what carries across channels
2121
2222## Walk through a Claude Tag session
from line 183
183183| A page kept current | Any of the above, edited in place over time | Digests, indexes, standing reports |
184184| A hosted page | A web page published on claude.ai, linked in the thread | Dashboards, prototypes, reports |
185185
186A 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.
186A 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
188188For code work, the result is usually a draft pull request opened under the Claude GitHub App, with the link posted in the thread.
189189
from line 206
206206* **Ask what Claude can reach.** In any channel, `@Claude what can you access from this channel?` lists its current reach.
207207* **If Claude cannot reach something, the channel was not granted access.** Another channel may have the access, and an organization Owner can add it. [How agent identity works](/docs/claude-tag/concepts/agent-identity) covers the model.
208208* **Personal connectors are separate from channel connections.** A connection an admin attaches to a channel is separate from a connector on your personal claude.ai account. Your own connectors work in your DMs. Claude can also [use them in a channel](/docs/claude-tag/concepts/personal-connectors) for your own tasks, after you allow it.
209
210### What Claude can do in other channels
211
212A session works in the channel or DM where you asked, and it can also reach other public channels that Claude is a member of. For example, ask in `#team-eng` to "post a summary of this thread in #announcements", and Claude posts the summary in `#announcements` as a new top-level message.
213
214Where you ask decides what Claude can do in the other channel:
215
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** |
221
222* **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".
223* **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.
224* **Which channels Claude can post into**: a public channel in the same Slack workspace that Claude is already a member of. Claude can't post into a Slack Connect channel or a [channel shared across workspaces](/docs/claude-tag/admins/restrict-access#channels-shared-across-workspaces-in-your-enterprise-grid), wherever you ask from.
225* **If Claude isn't a member of the target channel**: when you ask from a channel, add Claude by sending `/invite @Claude` from inside the target channel. When you ask from a DM, approving the post adds Claude to the target channel.
226* **Channels with guests**: Claude can post into a [channel that includes guests](/docs/claude-tag/admins/restrict-access#restrict-guest-channels) only when the **How should Claude work in channels with guests** setting covering that channel is **Full access**.
209227
210228### One-off and scheduled tasks
211229
No line in this hunk matches that.