One read of Claude Documentationclaude-docs-20261020T180705Z
246 pages moved out of 277 read.
Pages moved
246
significant first
Pages read
277
in this capture
Captured
18:07 UTC
Corpus hash
cf94986ff2f8
corpus-hash
What this read moved
76-100 of 246, page 4 of 10This capture is too large to show at once. Changes 76-100 of 246 are below, significant first; the rest are on the following screens.
claude-tag/concepts/data-lifecycle Changed · +3 / -3 lines
from line 2
22
33> What Claude Tag stores on Anthropic's side, how long session transcripts and memory are kept, and what disconnecting a workspace, uninstalling the app, deleting a Slack channel, removing a scope, or leaving the organization does to that data.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99Claude Tag keeps a record of its work on Anthropic's side, separate from the messages in your Slack workspace. This page is for an Owner or security reviewer who needs to know what that record contains, how long Anthropic keeps it, and which actions in Slack or in your Claude admin settings delete it. For each action, the tables below say what is deleted and whether Claude keeps responding, because the two don't always go together.
1010
claude-tag/concepts/for-claude-code-users Changed · +3 / -3 lines
from line 2
22
33> Which parts of a Claude Code setup carry into Claude Tag, which move to admin settings, and how Slack threads map to sessions.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99Claude Tag runs the same engine as Claude Code. When you tag `@Claude` in Slack with a task, a session starts in a sandbox that your organization configures, not on your machine. That sandbox is the same infrastructure that runs [Claude Code on the web](https://code.claude.com/docs/en/web-quickstart), described in [Compute and the sandbox](/docs/claude-tag/concepts/security-and-data#compute-and-the-sandbox).
1010
claude-tag/concepts/glossary Changed · +3 / -7 lines
from line 2
22
33> Claude Tag terms defined in one place, including agent identity, bundle, connector, personal connector, scope, Agent Proxy, routine, and session.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## Agent identity
1010
1111The service accounts Claude acts with: the Claude app in Slack, the Claude GitHub App on code, and the credentials an admin provisions for every other tool. See [How agent identity works](/docs/claude-tag/concepts/agent-identity).
from line 14
1414
1515The network layer that injects credentials into Claude's outbound requests. The model and the sandbox are not given the key; Agent Proxy adds the credential at the network boundary when a request matches the rules an admin set. See [How agent identity works](/docs/claude-tag/concepts/agent-identity#agent-proxy).
1616
17<a id="access-bundle" />
18
1917## Bundle
2018
2119A named set of connectors, repositories, [allowed domains](/docs/claude-tag/admins/add-connections#add-a-domain), plugins, and instructions that Claude uses for one kind of work, such as support triage. An Owner or a [Claude Tag admin](#claude-tag-admin) creates bundles on the **Bundles** tab under **Claude's access** at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), then adds the places where each one applies: all of Slack, a workspace, or a channel. One bundle can apply in many places, and an Owner can also apply one to every channel whose name matches a pattern. See [Give Claude access](/docs/claude-tag/admins/add-connections).
from line 42
4442| Proactive work | None | Routines and channel watching |
4543
4644Your admin chooses which generation answers `@Claude` in a given channel, so two channels in the same workspace can work differently. See [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
47
48<a id="connection" />
4945
5046## Connector
5147
claude-tag/concepts/how-it-works Changed · +29 / -67 lines
from line 2
22
33> Each Claude Tag thread in Slack runs a working session in a sandbox. See how progress shows in the thread, how to steer mid-task, what survives between turns, and how memory is scoped.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99Claude Tag is Claude, working inside your team's Slack channels. An organization Owner gives it its own accounts to the tools your team uses, so it arrives already able to act, and anyone in a channel can tag it into a problem without setting anything up.
1010
1111When someone tags Claude in at a channel's top level, the channel's own [session](/docs/claude-tag/concepts/glossary#session) picks the message up. A task that needs investigation, tools, or a longer exchange gets a working session in a thread under the message, and that thread binds to its own session from then on. Claude works through the task and posts the result back into the conversation. The work runs in an ephemeral cloud sandbox, not on your local machine.
from line 23
2323
2424The thread below is one task end to end in Slack: Jordan tags @Claude into `#launch-week` with a question, a colleague steers mid-thread, and the answer lands in the channel.
2525
26<div className="tm-slack">
27 <div className="tm-slack-head">
28 <span className="tm-slack-chan"># launch-week</span>
29 <span className="tm-slack-members">19 members</span>
30 </div>
26\# launch-week
2719 members
3128
32 <div className="tm-slack-body">
33 <div className="tm-msg">
34 <span className="tm-avatar tm-avatar-user" aria-hidden="true">J</span>
3529
36 <div className="tm-msg-col">
37 <div className="tm-msg-meta"><span className="tm-msg-name">Jordan</span><span className="tm-msg-time">9:02 AM</span></div>
38 <p><span className="tm-mention">@Claude</span> where are we on launch prep? Pull together what's still open from this channel.</p>
39 </div>
40 </div>
4130
42 <div className="tm-msg">
43 <span className="tm-avatar tm-avatar-claude">
44 <img src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/logo/clay-spark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=032101c39ca3b1af9f72fc4af8e60d12" alt="" noZoom width="94" height="94" data-path="images/claude-tag/logo/clay-spark.svg" />
45 </span>
31Jordan9:02 AM\@Claude where are we on launch prep? Pull together what's still open from this channel.
4632
47 <div className="tm-msg-col">
48 <div className="tm-msg-meta"><span className="tm-msg-name">Claude</span><span className="tm-msg-app">APP</span><span className="tm-msg-time">9:02 AM</span></div>
49 <p>On it. I'll go through this channel's open threads and the launch plan.</p>
33
5034
51 <div className="tm-tasklist">
52 <span className="tm-task-done"><span className="tm-sr">Done: </span>Read 14 open threads</span>
53 <span className="tm-task-done"><span className="tm-sr">Done: </span>Cross-checked the launch plan in Drive</span>
54 <span className="tm-task-done"><span className="tm-sr">Done: </span>Listed who each item is waiting on</span>
55 <span className="tm-task-done"><span className="tm-sr">Done: </span>Drafted the status summary</span>
56 </div>
57 </div>
58 </div>
35ClaudeAPP9:02 AMOn it. I'll go through this channel's open threads and the launch plan.
5936
60 <div className="tm-msg">
61 <span className="tm-avatar tm-avatar-user tm-avatar-b" aria-hidden="true">S</span>
37Done: Read 14 open threads
38Done: Cross-checked the launch plan in Drive
39Done: Listed who each item is waiting on
40Done: Drafted the status summary
6241
63 <div className="tm-msg-col">
64 <div className="tm-msg-meta"><span className="tm-msg-name">Sam</span><span className="tm-msg-time">9:06 AM</span></div>
65 <p>fold in the vendor quotes from last week's thread too</p>
66 </div>
67 </div>
6842
69 <div className="tm-msg">
70 <span className="tm-avatar tm-avatar-claude">
71 <img src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/logo/clay-spark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=032101c39ca3b1af9f72fc4af8e60d12" alt="" noZoom width="94" height="94" data-path="images/claude-tag/logo/clay-spark.svg" />
72 </span>
7343
74 <div className="tm-msg-col">
75 <div className="tm-msg-meta"><span className="tm-msg-name">Claude</span><span className="tm-msg-app">APP</span><span className="tm-msg-time">9:08 AM</span></div>
76 <p>Done. Full status below: eight items closed, three open. The venue contract is the oldest, waiting on legal since the 2nd.</p>
77 </div>
78 </div>
79 </div>
80</div>
44Sam9:06 AMfold in the vendor quotes from last week's thread too
8145
46
47
48ClaudeAPP9:08 AMDone. Full status below: eight items closed, three open. The venue contract is the oldest, waiting on legal since the 2nd.
49
8250Each of the five moments in that thread shows a piece of how Claude Tag works:
8351
84521. **Jordan handed Claude a problem, not a prompt.** Typing `@Claude` in a message that asks for something is what starts a working session.
from line 125
1571254. **The result lands in the thread.** An answer, a doc, a chart, or a pull request.
1581265. **A quiet period follows.** The sandbox is released while the thread persists; a new reply rebuilds it and starts the loop again.
159127
160<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/session-loop.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=436dd451c4ab3ab0f0b072f85051e844" alt="Flow diagram of one session in five numbered steps. Step 1, tag Claude in with an @Claude message carrying a task. Steps 2 and 3 happen inside the sandbox. Step 2, a sandbox builds, one per thread; step 3, the working loop runs through the task's steps using the channel's access. Step 4, Claude posts the result in the thread as an answer, a doc, a chart, or a pull request. Step 5, a dashed quiet period follows, where the sandbox is released while the thread persists. A dashed return arrow from the quiet period back up into the sandbox shows that a new reply rebuilds it and the loop continues." width="1000" height="400" data-path="images/claude-tag/diagrams/session-loop.svg" />
128
161129
162<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/session-loop-dark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=616c51832cbb9bc57fe6da5346c6ac85" alt="Flow diagram of one session in five numbered steps. Step 1, tag Claude in with an @Claude message carrying a task. Steps 2 and 3 happen inside the sandbox. Step 2, a sandbox builds, one per thread; step 3, the working loop runs through the task's steps using the channel's access. Step 4, Claude posts the result in the thread as an answer, a doc, a chart, or a pull request. Step 5, a dashed quiet period follows, where the sandbox is released while the thread persists. A dashed return arrow from the quiet period back up into the sandbox shows that a new reply rebuilds it and the loop continues." width="1000" height="400" data-path="images/claude-tag/diagrams/session-loop-dark.svg" />
163
164130Steps 1 and 2 are [starting a session](#start-a-session): a message tags Claude in, and a sandbox builds for that thread. Step 3, the working loop, is [the checklist](#how-the-checklist-updates) below. Steps 4 and 5, the result and the quiet period that follows, are covered in [What survives between replies](#what-survives-between-replies).
165131
166132Every session runs in an ephemeral sandbox, a real working environment where Claude can read documents, run code, build charts, and open pull requests. Claude clones your GitHub repositories into the sandbox, edits them there, and pushes changes back to GitHub as a branch or pull request. The sandbox runs the same engine that powers Claude Code on the web, Anthropic's agent for writing and running code, which is why the results are working artifacts rather than chat.
from line 219
253219| 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 |
254220| 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 |
255221
256<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" />
222
257223
258<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" />
259
260224| | Survives idle periods |
261225| :- | :- |
262226| The conversation and its context | Yes |
from line 248
284248
285249The whole model so far fits in one picture, with access set at the scope, memory kept per channel, work in progress per thread, and one-to-one DMs outside all of it.
286250
287<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/ZNX07pWnPReWiLwB/images/claude-tag/diagrams/three-levels.svg?fit=max&auto=format&n=ZNX07pWnPReWiLwB&q=85&s=78dfe70e5cf12007485d19baf47b803b" alt="Diagram showing three nested levels. A scope container holds two channels, #platform-eng and #gtm-west, and each channel holds its own threads, like 'fix checkout latency' or 'pull deal state'. The private channel is marked with a lock. Callouts mark what lives at each level (identity and access at the scope, memory at the channel plus workspace notes shared from public channels, and work in progress at the thread). A DM with Claude sits below, outside every scope, and runs on your own account." width="1000" height="648" data-path="images/claude-tag/diagrams/three-levels.svg" />
288
289<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/ZNX07pWnPReWiLwB/images/claude-tag/diagrams/three-levels-dark.svg?fit=max&auto=format&n=ZNX07pWnPReWiLwB&q=85&s=9b28d67feff32743e5cc2094e8fc3ec9" alt="Diagram showing three nested levels. A scope container holds two channels, #platform-eng and #gtm-west, and each channel holds its own threads, like 'fix checkout latency' or 'pull deal state'. The private channel is marked with a lock. Callouts mark what lives at each level (identity and access at the scope, memory at the channel plus workspace notes shared from public channels, and work in progress at the thread). A DM with Claude sits below, outside every scope, and runs on your own account." width="1000" height="648" data-path="images/claude-tag/diagrams/three-levels-dark.svg" />
251
290252
291253One-to-one DMs are outside this picture; they run on your own account, as covered in [Team channels and personal DMs](#team-channels-and-personal-dms). An Owner can turn off DMs for the whole organization; see [Allow or disable direct messages](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages).
292254
claude-tag/concepts/personal-connectors Changed · +3 / -3 lines
from line 2
22
33> Claude can use your own claude.ai connectors, called personal connectors, for your tasks in a Slack channel. See how you approve connector use, when Claude asks you to review a result before posting it, and what other people in the channel can reach.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99Personal connectors are the tools you add to your own claude.ai account, like your calendar or your email. When a task you ask for in a Slack channel needs one of your own tools, Claude can offer to use your connector for it.
1010
claude-tag/concepts/security-and-data Changed · +5 / -9 lines
from line 2
22
33> How Claude Tag keeps credentials out of the sandbox, limits where a channel session's requests can go, and controls who can see artifacts and invoke Claude.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99In channels, Claude acts under its own service accounts. By default it can read and post in Slack channels it's been added to and search public channels by keyword; it has no access to your external systems until an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) adds Claude Tag connectors. An admin chooses where each connector applies, from every channel down to one, and the actions Claude takes in connected tools are attributable to its own service accounts.
1010
1111Every channel request, whether a person typed it or a schedule triggered it, follows the same path: it runs in an isolated sandbox, and the credentials you provision aren't placed in that sandbox. In an Anthropic-hosted environment, requests leave that sandbox only through Agent Proxy and reach your systems under the agent's own accounts. Sessions in a [self-hosted environment](https://code.claude.com/docs/en/self-hosted-environments) run on runners inside your network, and Claude can't use the connectors an admin adds in those sessions.
from line 16
1616
1717Each Slack thread runs in its own sandbox. In an Anthropic-hosted environment, every outbound call from that sandbox passes through the same checkpoints.
1818
19<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/lijct3C2aoA3LHFn/images/claude-tag/diagrams/request-path.svg?fit=max&auto=format&n=lijct3C2aoA3LHFn&q=85&s=10d796e77738a52a505dcab2c9950cda" alt="Diagram showing the request path across three zones, labeled your Slack workspace, Anthropic's infrastructure, and your systems. A task mentioned in the Slack workspace runs in a session sandbox in the middle zone, one sandbox per thread, holding no stored credentials. Outbound requests pass to Agent Proxy, which injects the credential drawn from the credential store; a request that no rule, domain entry, or environment network access setting allows is blocked. Credentialed requests reach your systems, like GitHub, a data warehouse, monitoring, or any HTTP API. A dashed return path shows results posting back in the thread, as Claude." width="1000" height="440" data-path="images/claude-tag/diagrams/request-path.svg" />
19
2020
21<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/lijct3C2aoA3LHFn/images/claude-tag/diagrams/request-path-dark.svg?fit=max&auto=format&n=lijct3C2aoA3LHFn&q=85&s=613ad7bf32eee0f85bd3a26064dcc74a" alt="Diagram showing the request path across three zones, labeled your Slack workspace, Anthropic's infrastructure, and your systems. A task mentioned in the Slack workspace runs in a session sandbox in the middle zone, one sandbox per thread, holding no stored credentials. Outbound requests pass to Agent Proxy, which injects the credential drawn from the credential store; a request that no rule, domain entry, or environment network access setting allows is blocked. Credentialed requests reach your systems, like GitHub, a data warehouse, monitoring, or any HTTP API. A dashed return path shows results posting back in the thread, as Claude." width="1000" height="440" data-path="images/claude-tag/diagrams/request-path-dark.svg" />
22
2321| Checkpoint | The guarantee |
2422| :- | :- |
2523| The sandbox | Holds none of the credentials you provision |
from line 49
5149
5250In an Anthropic-hosted environment, outbound traffic from a channel session's sandbox is default-deny. Requests go only to hosts an allow layer covers, and the layers are a [credential's allowed websites](/docs/claude-tag/admins/connections/custom#fill-out-the-custom-tool-form), the [allowed domains](/docs/claude-tag/admins/add-connections#allow-a-host-without-a-credential) that apply to the channel, and the network access setting of the [environment](/docs/claude-tag/concepts/glossary#environment) the scope's sessions run on. A new environment's default level, Trusted access, already covers a [documented set of package registries and developer hosts](https://code.claude.com/docs/en/cloud-environments#default-allowed-domains). See [Agent Proxy](/docs/claude-tag/concepts/agent-identity#agent-proxy) for what happens to a request under each layer.
5351
54<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/f29MqpCRlPctgTn5/images/claude-tag/diagrams/proxy-decision.svg?fit=max&auto=format&n=f29MqpCRlPctgTn5&q=85&s=f87bc9ca2d2de09e4feda0a60695e9bd" alt="Flow diagram across two zones, labeled Anthropic's infrastructure and your systems. In the first zone, a session sandbox that holds no stored credentials sends every outbound request to Agent Proxy, which matches it against admin rules. Three outcomes branch toward your systems: on a rule match, the credential is attached at the boundary and the request proceeds; on an allowlist-only match, from an allowed domain or the environment's network access setting, the request is sent without credentials; on no match, the request is blocked entirely (the default-deny outcome) and the host is unreachable." width="1000" height="400" data-path="images/claude-tag/diagrams/proxy-decision.svg" />
55
56<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/f29MqpCRlPctgTn5/images/claude-tag/diagrams/proxy-decision-dark.svg?fit=max&auto=format&n=f29MqpCRlPctgTn5&q=85&s=ccbd8f7c4ba256a77cf85358880179b7" alt="Flow diagram across two zones, labeled Anthropic's infrastructure and your systems. In the first zone, a session sandbox that holds no stored credentials sends every outbound request to Agent Proxy, which matches it against admin rules. Three outcomes branch toward your systems: on a rule match, the credential is attached at the boundary and the request proceeds; on an allowlist-only match, from an allowed domain or the environment's network access setting, the request is sent without credentials; on no match, the request is blocked entirely (the default-deny outcome) and the host is unreachable." width="1000" height="400" data-path="images/claude-tag/diagrams/proxy-decision-dark.svg" />
52
5753
5854Because requests to any other host are blocked, data can only leave the sandbox to hosts an allow layer covers. An admin sets the allowed websites on each credential and the allowed domains. An admin sets the environment's network access level, which defaults to Trusted access, from the **Cloud environments** page in [admin settings](https://claude.ai/admin-settings). See [Set allowed websites](/docs/claude-tag/admins/add-connections#set-allowed-websites) and [Allow a host without a credential](/docs/claude-tag/admins/add-connections#allow-a-host-without-a-credential).
5955
claude-tag/concepts/settings-map Changed · +3 / -3 lines
from line 2
22
33> Claude Tag settings map: the admin page for access and behavior, the usage page for spend limits, the in-Slack Configure link for channel instructions, and personal connectors for DMs and your own tasks in channels. Claude Managed Agents is configured separately on the Claude Platform.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99Claude Tag's settings live on claude.ai, split across a few pages that each own a different kind of setting. Which page you need depends on what you're changing. The table maps each surface to what it controls.
1010
claude-tag/overview Changed · +60 / -143 lines
from line 2
22
33> Claude Tag puts Claude in your Slack channels with admin-governed access. See what to hand it, how setup works, and where to start as an admin or end user.
44
5<div className="tm-hero">
6 <div className="tm-hero-copy">
7 <span className="tm-pill">Public Beta</span>
8 <p className="tm-hero-title">Tag <span className="tm-hero-at">@Claude</span> in. Get results back in the thread.</p>
9 <p className="tm-hero-lede">Anyone in a Slack channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.</p>
5Public Beta
6Tag @Claude in. Get results back in the thread.
7Anyone in a Slack channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.
108
11 <div className="tm-hero-ctas">
12 <a className="tm-btn tm-btn-dark" href="/docs/claude-tag/admins/setup-overview">I'm setting it up →</a>
13 <a className="tm-btn tm-btn-light" href="#put-claude-tag-to-work">Use it in your channel ↓</a>
14 </div>
15 </div>
9[I'm setting it up →](/docs/claude-tag/admins/setup-overview)
10[Use it in your channel ↓](#put-claude-tag-to-work)
1611
17 <div className="tm-slack">
18 <div className="tm-slack-head">
19 <span className="tm-slack-chan"># platform-eng</span>
20 <span className="tm-slack-members">38 members</span>
21 </div>
12\# platform-eng
1338 members
2214
23 <div className="tm-slack-body">
24 <div className="tm-msg">
25 <span className="tm-avatar tm-avatar-user" aria-hidden="true">D</span>
2615
27 <div className="tm-msg-col">
28 <div className="tm-msg-meta"><span className="tm-msg-name">Dana</span><span className="tm-msg-time">2:14 PM</span></div>
29 <p>checkout has felt slow all morning — anyone else seeing it?</p>
30 </div>
31 </div>
3216
33 <div className="tm-msg">
34 <span className="tm-avatar tm-avatar-user tm-avatar-b" aria-hidden="true">L</span>
17Dana2:14 PMcheckout has felt slow all morning — anyone else seeing it?
3518
36 <div className="tm-msg-col">
37 <div className="tm-msg-meta"><span className="tm-msg-name">Leo</span><span className="tm-msg-time">2:15 PM</span></div>
38 <p>same. <span className="tm-mention">@Claude</span> can you investigate? Compare latency against this morning's deploy and find what's causing it.</p>
39 </div>
40 </div>
4119
42 <div className="tm-msg">
43 <span className="tm-avatar tm-avatar-claude">
44 <img src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/logo/clay-spark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=032101c39ca3b1af9f72fc4af8e60d12" alt="" noZoom width="94" height="94" data-path="images/claude-tag/logo/clay-spark.svg" />
45 </span>
4620
47 <div className="tm-msg-col">
48 <div className="tm-msg-meta"><span className="tm-msg-name">Claude</span><span className="tm-msg-app">APP</span><span className="tm-msg-time">2:15 PM</span></div>
49 <p>On it. I'll compare latency before and after the deploy, track down the cause, and report back here.</p>
21Leo2:15 PMsame. @Claude can you investigate? Compare latency against this morning's deploy and find what's causing it.
5022
51 <div className="tm-tasklist">
52 <span className="tm-task-done"><span className="tm-sr">Done: </span>Pulled p99 latency from Datadog</span>
53 <span className="tm-task-done"><span className="tm-sr">Done: </span>Diffed deploy 4f2c1 against main</span>
54 <span className="tm-task-done"><span className="tm-sr">Done: </span>Reproduced the slow query locally</span>
55 <span className="tm-task-doing"><span className="tm-sr">In progress: </span>Opening a pull request with the fix…</span>
56 </div>
57 </div>
58 </div>
59 </div>
60 </div>
61</div>
23
6224
25ClaudeAPP2:15 PMOn it. I'll compare latency before and after the deploy, track down the cause, and report back here.
26
27Done: Pulled p99 latency from Datadog
28Done: Diffed deploy 4f2c1 against main
29Done: Reproduced the slow query locally
30In progress: Opening a pull request with the fix…
31
6332## Plans that include Claude Tag
6433
6534Claude Tag is available on Team and Enterprise plans, on Anthropic's first-party service. It isn't available on individual plans (Free, Pro, or Max), or for third-party deployments. To use it, your organization pairs its Slack workspace with its Claude organization; see [the setup overview](/docs/claude-tag/admins/setup-overview) for the full prerequisites.
from line 51
8251
8352You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through [Claude Tag connectors](/docs/claude-tag/admins/add-connections), [plugins, and skills](/docs/claude-tag/admins/customize). An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) configures these for all of Slack, for one workspace, or for one channel. Members' own claude.ai connectors are separate from that configuration; Claude can use them in a channel for the member's own requests, as [personal connectors in channels](/docs/claude-tag/concepts/personal-connectors) describes.
8453
85<div className="tm-route-grid">
86 <div className="tm-card">
87 <a className="tm-band tm-band-admins" href="/docs/claude-tag/admins/setup-overview">
88 <span className="tm-band-text">
89 <span className="tm-band-label">For administrators</span>
90 <span className="tm-band-title">Set up Claude Tag</span>
91 </span>
54For administrators
55Set up Claude Tag
9256
93 <img src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/illustrations/Hand-Key.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=1b7a9675728f971bc7a4663c7f1ea599" alt="" noZoom width="1000" height="1000" data-path="images/claude-tag/illustrations/Hand-Key.svg" />
94 </a>
57
9558
96 <div className="tm-qrows">
97 <a className="tm-qrow" href="/docs/claude-tag/admins/setup-overview">
98 <span className="tm-qrow-text">
99 <span className="tm-qrow-q">Where do I start?</span>
100 <span className="tm-qrow-sub">Pair your Slack workspace, launch, and test that it works</span>
101 </span>
102 </a>
59[Open](/docs/claude-tag/admins/setup-overview)
10360
104 <a className="tm-qrow" href="/docs/claude-tag/concepts/agent-identity">
105 <span className="tm-qrow-text">
106 <span className="tm-qrow-q">What can Claude Tag access?</span>
107 <span className="tm-qrow-sub">How admins set access per channel, and where credentials are stored</span>
108 </span>
109 </a>
61[Where do I start?
62Pair your Slack workspace, launch, and test that it works](/docs/claude-tag/admins/setup-overview)
11063
111 <a className="tm-qrow" href="/docs/claude-tag/admins/add-connections">
112 <span className="tm-qrow-text">
113 <span className="tm-qrow-q">How do I connect each service?</span>
114 <span className="tm-qrow-sub">Credential types, allowed hosts, and what each connection lets Claude reach</span>
115 </span>
116 </a>
117 </div>
118 </div>
64[What can Claude Tag access?
65How admins set access per channel, and where credentials are stored](/docs/claude-tag/concepts/agent-identity)
11966
120 <div className="tm-card">
121 <a className="tm-band tm-band-users" href="#put-claude-tag-to-work">
122 <span className="tm-band-text">
123 <span className="tm-band-label">For end users</span>
124 <span className="tm-band-title">Put Claude Tag to work</span>
125 </span>
67[How do I connect each service?
68Credential types, allowed hosts, and what each connection lets Claude reach](/docs/claude-tag/admins/add-connections)
12669
127 <img src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/illustrations/Hand-NodePair.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=c64df4c6d27a6da752aa32c9e0622781" alt="" noZoom width="1000" height="1000" data-path="images/claude-tag/illustrations/Hand-NodePair.svg" />
128 </a>
70For end users
71Put Claude Tag to work
12972
130 <div className="tm-qrows">
131 <a className="tm-qrow" href="/docs/claude-tag/users/getting-started">
132 <span className="tm-qrow-text">
133 <span className="tm-qrow-q">How do I hand Claude Tag a task?</span>
134 <span className="tm-qrow-sub">Mention Claude in any channel it's in, with nothing to install</span>
135 </span>
136 </a>
73
13774
138 <a className="tm-qrow" href="/docs/claude-tag/users/use-cases">
139 <span className="tm-qrow-text">
140 <span className="tm-qrow-q">What is Claude Tag good at?</span>
141 <span className="tm-qrow-sub">Use cases for coding, data, incidents, and go-to-market</span>
142 </span>
143 </a>
75[Open](#put-claude-tag-to-work)
14476
145 <a className="tm-qrow" href="/docs/claude-tag/users/good-habits">
146 <span className="tm-qrow-text">
147 <span className="tm-qrow-q">How do I get good results?</span>
148 <span className="tm-qrow-sub">Good habits for scoping and reviewing work</span>
149 </span>
150 </a>
77[How do I hand Claude Tag a task?
78Mention Claude in any channel it's in, with nothing to install](/docs/claude-tag/users/getting-started)
15179
152 <a className="tm-qrow" href="/docs/claude-tag/users/memory">
153 <span className="tm-qrow-text">
154 <span className="tm-qrow-q">What does Claude Tag remember?</span>
155 <span className="tm-qrow-sub">Channel memory, what's shared across the workspace, and who can see what</span>
156 </span>
157 </a>
80[What is Claude Tag good at?
81Use cases for coding, data, incidents, and go-to-market](/docs/claude-tag/users/use-cases)
15882
159 <a className="tm-qrow" href="/docs/claude-tag/users/proactivity">
160 <span className="tm-qrow-text">
161 <span className="tm-qrow-q">Can Claude Tag run tasks on a schedule?</span>
162 <span className="tm-qrow-sub">Scheduled jobs, channel watching, and triggers</span>
163 </span>
164 </a>
165 </div>
166 </div>
167</div>
83[How do I get good results?
84Good habits for scoping and reviewing work](/docs/claude-tag/users/good-habits)
16885
86[What does Claude Tag remember?
87Channel memory, what's shared across the workspace, and who can see what](/docs/claude-tag/users/memory)
88
89[Can Claude Tag run tasks on a schedule?
90Scheduled jobs, channel watching, and triggers](/docs/claude-tag/users/proactivity)
91
16992## Billing and spend limits
17093
17194Adding Claude to Slack doesn't add a per-seat charge. Channel, thread, and group DM work is billed by usage instead: it draws from a **usage balance**, an amount in your organization's billing currency that an Owner funds. A [spend limit](/docs/claude-tag/admins/set-spend-limit) caps how much of that balance Claude Tag can use each billing period.
from line 97
17497
17598To learn what your team's usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the [usage page in your admin settings](https://claude.ai/admin-settings/usage/claude-tag). [Set a spend limit](/docs/claude-tag/admins/set-spend-limit) covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.
17699
177<div className="tm-eyebrow"><span className="tm-swatch tm-swatch-users" />For end users</div>
100For end users
178101
179102## Put Claude Tag to work
180103
from line 124
201124
202125[Get started](/docs/claude-tag/users/getting-started) covers your first message, what you see while Claude works, and how to shape Claude's behavior in your channel.
203126
204<div className="tm-eyebrow"><span className="tm-swatch tm-swatch-admins" />For administrators</div>
127For administrators
205128
206129## Set Claude Tag up once for everyone
207130
from line 139
216139
217140[Set up Claude Tag](/docs/claude-tag/admins/setup-overview) walks through setup and connecting tools, with what to have ready, what each choice means, and how to verify Claude Tag works once you launch.
218141
219<div className="tm-strip">
220 <div className="tm-strip-head">
221 <p className="tm-strip-title">Security review</p>
222 <a className="tm-strip-all" href="/docs/claude-tag/concepts/security-and-data">Security and data handling</a>
223 </div>
142Security review
143[Security and data handling](/docs/claude-tag/concepts/security-and-data)
224144
225 <p>The security model, what admins can and can't restrict, audit trails, and network requirements.</p>
226</div>
145The security model, what admins can and can't restrict, audit trails, and network requirements.
227146
228147## Where to start with Claude Tag
229148
230<CardGroup cols={2}>
231 <Card title="Set up Claude Tag" icon="gear" href="/docs/claude-tag/admins/setup-overview" horizontal arrow>
232 Admins: pair your Slack workspace and launch
233 </Card>
149> **[Set up Claude Tag](/docs/claude-tag/admins/setup-overview)**
150>
151> Admins: pair your Slack workspace and launch
234152
235 <Card title="Hand Claude Tag your first task" icon="paper-plane" href="/docs/claude-tag/users/getting-started" horizontal arrow>
236 It's already in your channel: send your first message
237 </Card>
153> **[Hand Claude Tag your first task](/docs/claude-tag/users/getting-started)**
154>
155> It's already in your channel: send your first message
238156
239 <Card title="How Claude Tag works" icon="diagram-project" href="/docs/claude-tag/concepts/how-it-works" horizontal arrow>
240 The session model, what it can read, and how memory follows places
241 </Card>
157> **[How Claude Tag works](/docs/claude-tag/concepts/how-it-works)**
158>
159> The session model, what it can read, and how memory follows places
242160
243 <Card title="Use case library" icon="list" href="/docs/claude-tag/users/use-cases" horizontal arrow>
244 Prompts to paste, by team and connection
245 </Card>
246</CardGroup>
161> **[Use case library](/docs/claude-tag/users/use-cases)**
162>
163> Prompts to paste, by team and connection
247164
claude-tag/users/commands Changed · +3 / -3 lines
from line 2
22
33> A few exact, bang-prefixed words after an @-mention run a fixed action instead of starting a normal turn: see the command list, get the link to a channel's settings page, restart a stuck or wrong-context session, check whether Claude is still working in a thread or channel, mute or unmute a thread, turn fast mode on or off, send feedback, list a channel's routines, and fork a thread's conversation into a new thread, here or in another channel.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99A command is `@Claude` followed immediately by one of a few exact words starting with `!`. Claude matches the message against that word and runs a fixed action instead of starting a normal turn.
1010
claude-tag/users/getting-started Changed · +6 / -4 lines
from line 2
22
33> Claude Tag works in your Slack channels. See how to check it's on, send your first message, what it can read, and why DMs work differently.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99Claude Tag is Claude working in your Slack workspace. You hand it work by writing a message where Claude is, and Claude carries it out in that thread. An `@Claude` mention guarantees a response in a channel, but it isn't required everywhere. One-to-one DMs and threads Claude is already in reach it without one. There's nothing for you to install or configure; if `@Claude` is in your channel, you can use it (unless your admin has [restricted who can invoke Claude](/docs/claude-tag/admins/restrict-access#restrict-who-can-use-claude)).
1010
1111## When to tag Claude in a channel versus a DM
from line 104
104104
105105Claude can't read an image or PDF over its limit and answers from the rest of your message. To hand Claude a larger image or PDF, resize the image, split the PDF, or paste the text.
106106
107<Note>Slack doesn't expose personal account settings (your sidebar, notification preferences, channel membership, or DMs between you and other people) to apps. If you want help organizing channels, paste or screenshot the list and Claude can propose a scheme you apply yourself.</Note>
107> [!NOTE]
108>
109> Slack doesn't expose personal account settings (your sidebar, notification preferences, channel membership, or DMs between you and other people) to apps. If you want help organizing channels, paste or screenshot the list and Claude can propose a scheme you apply yourself.
108110
109111### Which messages Claude reads
110112
claude-tag/users/good-habits Changed · +9 / -5 lines
from line 2
22
33> Name the outcome, give every task a definition of done, and pick the right channel. See how to write tasks Claude can finish and how to keep many threads reviewable.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99Tasks should have a verifiable end state. Claude runs each one in its own thread, and a thread closes when someone can confirm the work is done. A task without that end state produces an open-ended report, and the thread stays open while you decide what to do with it.
1010
1111The habits here are for anyone who tags Claude in from Slack.
from line 54
5454@Claude migrate the export config to the new schema. Hard rules: no behavior change, don't touch the billing module, and every old config key keeps working as an alias. Done means the full test suite passes, not only the export tests.
5555```
5656
57<Warning>Constraints in a task steer Claude but don't restrict Claude from performing a specific action. Anything you type to Claude goes into its working context, where it can be forgotten or overridden. If there are actions Claude must not take, enforce them outside the conversation, with controls like repository permissions, branch protection rules, and required checks.</Warning>
57> [!WARNING]
58>
59> Constraints in a task steer Claude but don't restrict Claude from performing a specific action. Anything you type to Claude goes into its working context, where it can be forgotten or overridden. If there are actions Claude must not take, enforce them outside the conversation, with controls like repository permissions, branch protection rules, and required checks.
5860
5961### Give every task a definition of done
6062
from line 90
8890@Claude update the retry logic the way this thread decided. Handle test failures and lint yourself. Come back to me before changing any public interface, and for anything you're not sure is in scope.
8991```
9092
91<Warning>These instructions steer Claude but don't restrict Claude from deciding on its own. A decision that must come back to you needs an enforced control too, such as branch protection for merges.</Warning>
93> [!WARNING]
94>
95> These instructions steer Claude but don't restrict Claude from deciding on its own. A decision that must come back to you needs an enforced control too, such as branch protection for merges.
9296
9397Once you've seen and verified Claude's output over several tasks, you can let it make more decisions without checking in, the same way you widen [what it closes on its own](#give-every-task-a-definition-of-done).
9498
claude-tag/users/group-dms Changed · +13 / -15 lines
from line 2
22
33> Add Claude to a Slack group DM to share a task with a few people. See whose access and billing apply, when Claude replies, and what differs from a channel.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99A group DM is a Slack direct message among several people. Claude works in a group DM it has been added to, so a few people can share a task with Claude without creating a channel.
1010
1111If Claude answers your mention with "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead.", see [the causes of that reply](/docs/claude-tag/users/troubleshooting#group-dms-aren%E2%80%99t-supported-yet).
from line 53
5353* **Channel-only access.** A guest is in the group DM, and Claude runs there with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works).
5454* **Blocked member edits.** An admin set [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) to **Block** for the workspace or the organization.
5555
56<Steps>
57 <Step title="Ask Claude">
58 Mention `@Claude` at the top level of the group DM and ask it to reply only to mentions.
56**1. Ask Claude**
5957
60 ```text wrap theme={null}
61 @Claude only reply here when someone mentions you.
62 ```
58Mention `@Claude` at the top level of the group DM and ask it to reply only to mentions.
6359
64 Claude posts a card in the thread under your message, with **Confirm** and **Cancel** buttons.
65 </Step>
60```text wrap theme={null}
61@Claude only reply here when someone mentions you.
62```
6663
67 <Step title="Confirm the change">
68 Select **Confirm** within 30 minutes. The card changes to a line that names the person who confirmed and says Claude now replies only when @mentioned.
69 </Step>
70</Steps>
64Claude posts a card in the thread under your message, with **Confirm** and **Cancel** buttons.
65
66**2. Confirm the change**
67
68Select **Confirm** within 30 minutes. The card changes to a line that names the person who confirmed and says Claude now replies only when @mentioned.
7169
7270After the change, Claude still answers a mention, and it still reads replies in a thread that started with an `@Claude` mention.
7371
claude-tag/users/memory Changed · +3 / -3 lines
from line 2
22
33> Claude Tag memory belongs to the channel, not to you. See what each channel keeps, which notes are shared across the workspace, and how to check or correct them.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99Claude keeps memory by channel. Each channel, public or private, has its own notes, and channel memory isn't organized by person. From a public channel Claude can also save workspace notes, which it reads in every channel in the workspace. In a one-to-one direct message, Claude keeps separate notes for its conversation with you; see [Channel and workspace memory](#channel-and-workspace-memory).
1010
claude-tag/users/models Changed · +3 / -3 lines
from line 2
22
33> Ask Claude to switch models in a Slack thread, set a channel's default model, pick the model for your direct messages, or run a thread in fast mode. See which models you can use and how to confirm which one replied.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99Every Claude Tag reply in Slack comes from one Claude model, and you choose which one by asking Claude for it in plain language, the same way you hand it any other task. The footer of each reply names the model that handled it, so you can confirm a switch took effect.
1010
claude-tag/users/proactivity Changed · +3 / -3 lines
from line 2
22
33> Claude Tag runs routines you set up from a channel. See scheduled jobs, channel watching, pull request subscriptions, where results post, and how to pause them.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99You can give Claude standing work from any channel it's in. This standing work is called a routine: a job that runs on a schedule, such as watching a channel, following a pull request, or posting status updates. You set a routine up in the channel where it should run, and it uses that channel's connections with the same permissions as a typed request.
1010
claude-tag/users/prompt-library Changed · +3 / -3 lines
from line 2
22
33> Copy-paste prompts for Claude Tag in Slack, each with why it works. See first messages, handoffs, channel rules, memory checks, routines, fan-out, and steering.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
6
7<BetaNote />
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
99These prompts are ready to copy, paste, and adapt: swap in your own channel names, services, and repositories. Each comes with the reason it works, so you can keep the mechanism when you change the words.
1010
claude-tag/users/troubleshooting Changed · +6 / -6 lines
from line 2
22
33> Fixes for common Claude Tag problems in Slack. See no reply after a reaction, queued or failed sessions, lost work, missing connections, blocked links and websites, and DM or account errors.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99When something goes wrong mid-conversation, the cause is usually one of a small set. Each entry below has the same three parts: what you see, what it means, and how to resolve it. For setup and credential errors, see the [admin troubleshooting page](/docs/claude-tag/admins/troubleshooting).
1010
1111Many fixes end with something to send your admin. On this page that means whoever manages your organization's Claude account at claude.ai, and it's often not the same person as your Slack administrator. If you don't know who that is, ask whoever set Claude up in your workspace.
from line 68
68681. Send [`@Claude !status`](/docs/claude-tag/users/commands#check-whether-claude-is-still-working) in the same thread. Claude tells you, in a note only you can see, whether it's still working and for how long, without interrupting the work. If the note says Claude got disconnected, @-mention Claude in the thread and it picks up where it left off, with no restart needed.
69692. If the silence has stretched well past what the task should need, send [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread; it archives the session and starts a fresh one that still reads the thread. Starting a new thread and restating the request also works.
7070
71<Warning>Restarting abandons whatever the session was midway through, and there's no way to resume it. A silent session may still be working through a long task, so treat `!restart` as a last resort.</Warning>
71> [!WARNING]
72>
73> Restarting abandons whatever the session was midway through, and there's no way to resume it. A silent session may still be working through a long task, so treat `!restart` as a last resort.
7274
7375### Claude says my session is queued or failed to start
7476
from line 108
106108**How to resolve**
107109
108110Send a new message with the mention included.
109
110<a id="claude-never-responds-in-a-channel-shared-with-another-company" />
111111
112112### Claude is silent in a channel shared with another company
113113
claude-tag/users/use-cases Changed · +6 / -4 lines
from line 2
22
33> Shapes of work teams hand Claude Tag in Slack, each with prompts to paste. See triage, catch-up, docs and tickets, project tracking, data, deals, monitoring, and bug fixes.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99Each use case below links to a page with prompts to paste, what it needs connected, and how to set it up to [run on a schedule or watch the channel](/docs/claude-tag/users/proactivity) instead of asking each time.
1010
11<Note>If typing `@Claude` doesn't show **Claude** with an **APP** badge, the Claude app isn't installed in your Slack workspace; ask your Slack admin to install it. If the mention sends but Claude doesn't reply, ask your Claude organization admin to enable Claude Tag for the channel and send them the [setup guide](/docs/claude-tag/admins/setup-overview).</Note>
11> [!NOTE]
12>
13> If typing `@Claude` doesn't show **Claude** with an **APP** badge, the Claude app isn't installed in your Slack workspace; ask your Slack admin to install it. If the mention sends but Claude doesn't reply, ask your Claude organization admin to enable Claude Tag for the channel and send them the [setup guide](/docs/claude-tag/admins/setup-overview).
1214
1315## All use cases
1416
claude-tag/users/use-cases/answer-data-questions Changed · +12 / -14 lines
from line 2
22
33> Claude Tag answers data questions in the Slack thread. See warehouse queries with charts, scheduled metric reports, and charts built from channel history alone.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How data-question prompts work
1010
1111This page is for teams who answer questions from a data warehouse (the database where your analytics tables live, like BigQuery or Snowflake). These prompts turn a question asked in Slack into a query and a chart.
from line 52
5252
5353## Related resources
5454
55<CardGroup cols={2}>
56 <Card title="Watch monitors and alerts" href="/docs/claude-tag/users/use-cases/watch-monitors" horizontal arrow>
57 When the question is about systems, not metrics
58 </Card>
55> **[Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors)**
56>
57> When the question is about systems, not metrics
5958
60 <Card title="Set up routines" href="/docs/claude-tag/users/proactivity" horizontal arrow>
61 Recurring reports
62 </Card>
59> **[Set up routines](/docs/claude-tag/users/proactivity)**
60>
61> Recurring reports
6362
64 <Card title="Self-service data analytics" href="https://claude.com/blog/self-service-data-analytics-in-slack-how-anthropic-deploys-claude-tag-for-ad-hoc-questions" horizontal arrow>
65 How Anthropic answers ad-hoc data questions in Slack with Claude
66 </Card>
67</CardGroup>
63> **[Self-service data analytics](https://claude.com/blog/self-service-data-analytics-in-slack-how-anthropic-deploys-claude-tag-for-ad-hoc-questions)**
64>
65> How Anthropic answers ad-hoc data questions in Slack with Claude
6866
claude-tag/users/use-cases/catch-up Changed · +9 / -11 lines
from line 2
22
33> Claude Tag summarizes Slack threads and channels on demand. See one-off recaps, a scheduled morning rollup of open threads, and what's waiting on you.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How catch-up prompts work
1010
1111Each prompt below is a Slack message. You paste it in any channel Claude is in, Claude reads the channel or thread history and posts progress in that thread, and the recap lands there too. The result is always a summary of what was said, returned once or every morning depending on the prompt.
from line 46
4646
4747## Related resources
4848
49<CardGroup cols={2}>
50 <Card title="Turn threads into docs and tickets" href="/docs/claude-tag/users/use-cases/create-artifacts" horizontal arrow>
51 When the catch-up should become an artifact
52 </Card>
49> **[Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts)**
50>
51> When the catch-up should become an artifact
5352
54 <Card title="Set up routines" href="/docs/claude-tag/users/proactivity" horizontal arrow>
55 Scheduling and triggers
56 </Card>
57</CardGroup>
53> **[Set up routines](/docs/claude-tag/users/proactivity)**
54>
55> Scheduling and triggers
5856
claude-tag/users/use-cases/create-artifacts Changed · +9 / -11 lines
from line 2
22
33> Claude Tag turns a Slack discussion into the artifact you name. See replies you can send, decision docs, status memos, filed tickets, hosted web pages, page comments that reach Claude, and a capture-channel pattern.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How artifact prompts work
1010
1111An artifact here is a generated document, page, chart, or file Claude posts or links in the thread for the team to use, as opposed to a chat reply.
from line 73
7373
7474## Related resources
7575
76<CardGroup cols={2}>
77 <Card title="Catch up" href="/docs/claude-tag/users/use-cases/catch-up" horizontal arrow>
78 When you need the summary, not the artifact
79 </Card>
76> **[Catch up](/docs/claude-tag/users/use-cases/catch-up)**
77>
78> When you need the summary, not the artifact
8079
81 <Card title="Good habits" href="/docs/claude-tag/users/good-habits" horizontal arrow>
82 How to specify outputs that come back right
83 </Card>
84</CardGroup>
80> **[Good habits](/docs/claude-tag/users/good-habits)**
81>
82> How to specify outputs that come back right
8583
claude-tag/users/use-cases/find-answers Changed · +9 / -11 lines
from line 2
22
33> Claude Tag finds answers in connected docs and replies in the thread. See policy lookups, runbook checks, prior decisions, and answers from the Slack channel alone.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How answer-finding prompts work
1010
1111Each prompt below is a Slack message. You paste it in the channel where the question came up, Claude searches the connected docs or the channel history and posts progress in that thread, and the answer lands there too. The result is always an answer with the source it came from, so you can open what it read.
from line 60
6060
6161## Related resources
6262
63<CardGroup cols={2}>
64 <Card title="Catch up" href="/docs/claude-tag/users/use-cases/catch-up" horizontal arrow>
65 The same mechanism pointed at "what did I miss"
66 </Card>
63> **[Catch up](/docs/claude-tag/users/use-cases/catch-up)**
64>
65> The same mechanism pointed at "what did I miss"
6766
68 <Card title="What Claude Tag remembers" href="/docs/claude-tag/users/memory" horizontal arrow>
69 How channel knowledge accumulates
70 </Card>
71</CardGroup>
67> **[What Claude Tag remembers](/docs/claude-tag/users/memory)**
68>
69> How channel knowledge accumulates
7270
claude-tag/users/use-cases/fix-bugs Changed · +9 / -11 lines
from line 2
22
33> Claude Tag takes a bug report from Slack to a draft pull request. See reproducing the issue, watching a bug channel, root-cause digs, and following CI to green.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How bug-fix prompts work
1010
1111This page is for engineering teams. A pull request is a proposed code change opened for review; Claude opens them under its own GitHub identity, so they appear in your review queue like any other pull request.
from line 78
7878
7979## Related resources
8080
81<CardGroup cols={2}>
82 <Card title="Watch monitors and alerts" href="/docs/claude-tag/users/use-cases/watch-monitors" horizontal arrow>
83 Catching the problem before the bug report
84 </Card>
81> **[Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors)**
82>
83> Catching the problem before the bug report
8584
86 <Card title="Good habits" href="/docs/claude-tag/users/good-habits" horizontal arrow>
87 Definitions of done for code tasks
88 </Card>
89</CardGroup>
85> **[Good habits](/docs/claude-tag/users/good-habits)**
86>
87> Definitions of done for code tasks
9088
claude-tag/users/use-cases/marketing-team Changed · +9 / -11 lines
from line 2
22
33> Claude Tag recipes for marketing teams in Slack. See policy answers in an intake channel, campaign channel recaps and send-ready drafts, lead and campaign state from the CRM, a weekly metrics digest, and brand voice rules saved to channel memory.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How marketing prompts work
1010
1111This page is for marketing teams. The recipes below run in the channels where marketing work already happens, like an intake channel where other teams post requests, a campaign channel during a launch, and the channel where lead numbers get discussed.
from line 105
105105
106106## Related resources
107107
108<CardGroup cols={2}>
109 <Card title="Pull deal and account state" href="/docs/claude-tag/users/use-cases/pull-deal-state" horizontal arrow>
110 The full set of go-to-market prompts
111 </Card>
108> **[Pull deal and account state](/docs/claude-tag/users/use-cases/pull-deal-state)**
109>
110> The full set of go-to-market prompts
112111
113 <Card title="Set up routines" href="/docs/claude-tag/users/proactivity" horizontal arrow>
114 How the scheduled digest runs, and more recipes
115 </Card>
116</CardGroup>
112> **[Set up routines](/docs/claude-tag/users/proactivity)**
113>
114> How the scheduled digest runs, and more recipes
117115
claude-tag/users/use-cases/pull-deal-state Changed · +9 / -11 lines
from line 2
22
33> Claude Tag pulls account and deal state into the Slack channel. See in-thread account answers, pre-call briefs, and a scheduled weekly pipeline digest.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99## How deal-state prompts work
1010
1111This page is for sales and customer-success teams. A deal (also called an opportunity) is a sales prospect tracked in a CRM like Salesforce or HubSpot; an account is a customer record. These prompts pull that state into the Slack channel where the team discusses it.
from line 60
6060
6161## Related resources
6262
63<CardGroup cols={2}>
64 <Card title="Answer data questions" href="/docs/claude-tag/users/use-cases/answer-data-questions" horizontal arrow>
65 When the question is metrics, not accounts
66 </Card>
63> **[Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions)**
64>
65> When the question is metrics, not accounts
6766
68 <Card title="Set up routines" href="/docs/claude-tag/users/proactivity" horizontal arrow>
69 Scheduled digests
70 </Card>
71</CardGroup>
67> **[Set up routines](/docs/claude-tag/users/proactivity)**
68>
69> Scheduled digests
7270