One read of Claude Documentationclaude-docs-20261023T180724Z
267 pages moved out of 280 read.
Pages moved
267
significant first
Pages read
280
in this capture
Captured
18:07 UTC
Corpus hash
307a31a7094a
corpus-hash
What this read moved
76-100 of 267, page 4 of 11This capture is too large to show at once. Changes 76-100 of 267 are below, significant first; the rest are on the following screens.
claude-tag/overview Changed · +40 / -40 lines
from line 6
66Tag @Claude in. Get results back in the thread.
77Anyone 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.
88
9[I'm setting it up →](/docs/claude-tag/admins/setup-overview)
9[I'm setting it up →](https://claude.com/docs/claude-tag/admins/setup-overview)
1010[Use it in your channel ↓](#put-claude-tag-to-work)
1111
1212\# platform-eng
from line 31
3131
3232## Plans that include Claude Tag
3333
34Claude 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.
34Claude 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](https://claude.com/docs/claude-tag/admins/setup-overview) for the full prerequisites.
3535
36If you're choosing between Claude products for Slack-shaped work, [how Claude Tag differs from Cowork and Claude Code](/docs/claude-tag/concepts/how-it-works.md#how-claude-tag-differs-from-cowork-and-claude-code) compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.
36If you're choosing between Claude products for Slack-shaped work, [how Claude Tag differs from Cowork and Claude Code](https://claude.com/docs/claude-tag/concepts/how-it-works.md#how-claude-tag-differs-from-cowork-and-claude-code) compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.
3737
3838### Who needs a Claude seat
3939
4040Slack users don't each need a Claude seat to work with Claude in channels.
4141
42* **In channels**: by default, anyone in the paired Slack workspace can tag `@Claude` in a channel, and an Owner can [restrict who can use Claude](/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude) to people in your Claude organization or, on Enterprise, to specific roles. Channel work bills by usage to your organization's usage balance, under a [spend limit](/docs/claude-tag/admins/set-spend-limit.md) an Owner sets.
43* **In group DMs**: the same restriction on who can use Claude applies, and the work bills to your organization's usage balance. See [Group DMs](/docs/claude-tag/admins/restrict-access.md#group-dms).
44* **In one-to-one DMs**: a DM from a member who has connected a Claude account runs on that account and bills to that person's seat. The seat must include Claude Code, or, on the Enterprise plan, be a **Standard** or **Usage-Based Chat** seat held by someone who also has Cowork. A [DM from a member who hasn't connected a Claude account](/docs/claude-tag/admins/restrict-access.md#direct-messages-from-members-without-a-claude-account) can bill to your organization for a limited time.
42* **In channels**: by default, anyone in the paired Slack workspace can tag `@Claude` in a channel, and an Owner can [restrict who can use Claude](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude) to people in your Claude organization or, on Enterprise, to specific roles. Channel work bills by usage to your organization's usage balance, under a [spend limit](https://claude.com/docs/claude-tag/admins/set-spend-limit.md) an Owner sets.
43* **In group DMs**: the same restriction on who can use Claude applies, and the work bills to your organization's usage balance. See [Group DMs](https://claude.com/docs/claude-tag/admins/restrict-access.md#group-dms).
44* **In one-to-one DMs**: a DM from a member who has connected a Claude account runs on that account and bills to that person's seat. The seat must include Claude Code, or, on the Enterprise plan, be a **Standard** or **Usage-Based Chat** seat held by someone who also has Cowork. A [DM from a member who hasn't connected a Claude account](https://claude.com/docs/claude-tag/admins/restrict-access.md#direct-messages-from-members-without-a-claude-account) can bill to your organization for a limited time.
4545
4646## Where Claude Tag runs
4747
4848Claude Tag works in Slack. You interact with it by writing in a Slack channel, thread, or direct message, and it replies there. Mention `@Claude` in a channel to guarantee it picks the message up.
4949
50When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See [how Claude Tag works](/docs/claude-tag/concepts/how-it-works.md) for the full lifecycle.
50When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See [how Claude Tag works](https://claude.com/docs/claude-tag/concepts/how-it-works.md) for the full lifecycle.
5151
52You 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.md), [plugins, and skills](/docs/claude-tag/admins/customize.md). An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#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.md) describes.
52You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through [Claude Tag connectors](https://claude.com/docs/claude-tag/admins/add-connections.md), [plugins, and skills](https://claude.com/docs/claude-tag/admins/customize.md). An Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#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](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) describes.
5353
5454For administrators
5555Set up Claude Tag
from line 56
5656
5757
5858
59[Open](/docs/claude-tag/admins/setup-overview)
59[Open](https://claude.com/docs/claude-tag/admins/setup-overview)
6060
6161[Where do I start?
62Pair your Slack workspace, launch, and test that it works](/docs/claude-tag/admins/setup-overview)
62Pair your Slack workspace, launch, and test that it works](https://claude.com/docs/claude-tag/admins/setup-overview)
6363
6464[What can Claude Tag access?
65How admins set access per channel, and where credentials are stored](/docs/claude-tag/concepts/agent-identity.md)
65How admins set access per channel, and where credentials are stored](https://claude.com/docs/claude-tag/concepts/agent-identity.md)
6666
6767[How do I connect each service?
68Credential types, allowed hosts, and what each connection lets Claude reach](/docs/claude-tag/admins/add-connections.md)
68Credential types, allowed hosts, and what each connection lets Claude reach](https://claude.com/docs/claude-tag/admins/add-connections.md)
6969
7070For end users
7171Put Claude Tag to work
from line 75
7575[Open](#put-claude-tag-to-work)
7676
7777[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.md)
78Mention Claude in any channel it's in, with nothing to install](https://claude.com/docs/claude-tag/users/getting-started.md)
7979
8080[What is Claude Tag good at?
81Use cases for coding, data, incidents, and go-to-market](/docs/claude-tag/users/use-cases.md)
81Use cases for coding, data, incidents, and go-to-market](https://claude.com/docs/claude-tag/users/use-cases.md)
8282
8383[How do I get good results?
84Good habits for scoping and reviewing work](/docs/claude-tag/users/good-habits.md)
84Good habits for scoping and reviewing work](https://claude.com/docs/claude-tag/users/good-habits.md)
8585
8686[What does Claude Tag remember?
87Channel memory, what's shared across the workspace, and who can see what](/docs/claude-tag/users/memory.md)
87Channel memory, what's shared across the workspace, and who can see what](https://claude.com/docs/claude-tag/users/memory.md)
8888
8989[Can Claude Tag run tasks on a schedule?
90Scheduled jobs, channel watching, and triggers](/docs/claude-tag/users/proactivity.md)
90Scheduled jobs, channel watching, and triggers](https://claude.com/docs/claude-tag/users/proactivity.md)
9191
9292## Billing and spend limits
9393
94Adding 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.md) caps how much of that balance Claude Tag can use each billing period.
94Adding 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](https://claude.com/docs/claude-tag/admins/set-spend-limit.md) caps how much of that balance Claude Tag can use each billing period.
9595
96One-to-one direct messages from members who have connected a Claude account don't draw from this balance. Such a DM runs on the sender's own claude.ai account and follows that seat's usual usage limits, so the organization spend limit doesn't apply to it. A [DM from a member who hasn't connected a Claude account](/docs/claude-tag/admins/restrict-access.md#direct-messages-from-members-without-a-claude-account) can draw from this balance.
96One-to-one direct messages from members who have connected a Claude account don't draw from this balance. Such a DM runs on the sender's own claude.ai account and follows that seat's usual usage limits, so the organization spend limit doesn't apply to it. A [DM from a member who hasn't connected a Claude account](https://claude.com/docs/claude-tag/admins/restrict-access.md#direct-messages-from-members-without-a-claude-account) can draw from this balance.
9797
98To 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.md) covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.
98To 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](https://claude.com/docs/claude-tag/admins/set-spend-limit.md) covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.
9999
100100For end users
101101
102102## Put Claude Tag to work
103103
104If Claude Tag is in your channel, you can use it now. (If it isn't there yet, an Owner in your Claude organization runs setup: see [Set up Claude Tag](/docs/claude-tag/admins/setup-overview).) Anyone in the channel can hand it work, and channel work bills to the organization, not to you.
104If Claude Tag is in your channel, you can use it now. (If it isn't there yet, an Owner in your Claude organization runs setup: see [Set up Claude Tag](https://claude.com/docs/claude-tag/admins/setup-overview).) Anyone in the channel can hand it work, and channel work bills to the organization, not to you.
105105
106What it can reach starts with the channel you're in. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you're signed in to your Claude organization, click **Configure** in the footer of a Claude reply in the channel to see its [connections](/docs/claude-tag/concepts/glossary.md#connection), the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link.
106What it can reach starts with the channel you're in. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you're signed in to your Claude organization, click **Configure** in the footer of a Claude reply in the channel to see its [connections](https://claude.com/docs/claude-tag/concepts/glossary.md#connection), the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link.
107107
108For your own requests, Claude can also [use the connectors on your claude.ai account](/docs/claude-tag/concepts/personal-connectors.md), after you allow it.
108For your own requests, Claude can also [use the connectors on your claude.ai account](https://claude.com/docs/claude-tag/concepts/personal-connectors.md), after you allow it.
109109
110In a one-to-one DM, Claude runs on your own claude.ai account instead of a channel's setup. An Owner can turn off DMs for the whole organization; see [Allow or disable direct messages](/docs/claude-tag/admins/restrict-access.md#allow-or-disable-direct-messages).
110In a one-to-one DM, Claude runs on your own claude.ai account instead of a channel's setup. An Owner can turn off DMs for the whole organization; see [Allow or disable direct messages](https://claude.com/docs/claude-tag/admins/restrict-access.md#allow-or-disable-direct-messages).
111111
112112### Common uses
113113
114114Each link opens a guide with the prompts to paste and the connections the task needs.
115115
116* [Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md): scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
117* [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md): an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
118* [Find answers in your docs](/docs/claude-tag/users/use-cases/find-answers.md): policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
119* [Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions.md): a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
120* [Track projects and chase approvals](/docs/claude-tag/users/use-cases/track-projects.md): standing status digests and follow-ups that run until an approval lands
121* [Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts.md): a settled discussion becomes the decision doc, the customer reply, or the filed tickets
122* [Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md): a bug reported in the channel comes back as a draft pull request. Needs GitHub.
123* [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel.md): scratch questions, digests of channels you don't follow, and follow-ups on what you said you'd do
116* [Watch monitors and alerts](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md): scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
117* [Triage requests](https://claude.com/docs/claude-tag/users/use-cases/triage-requests.md): an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
118* [Find answers in your docs](https://claude.com/docs/claude-tag/users/use-cases/find-answers.md): policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
119* [Answer data questions](https://claude.com/docs/claude-tag/users/use-cases/answer-data-questions.md): a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
120* [Track projects and chase approvals](https://claude.com/docs/claude-tag/users/use-cases/track-projects.md): standing status digests and follow-ups that run until an approval lands
121* [Turn threads into docs and tickets](https://claude.com/docs/claude-tag/users/use-cases/create-artifacts.md): a settled discussion becomes the decision doc, the customer reply, or the filed tickets
122* [Fix bugs](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md): a bug reported in the channel comes back as a draft pull request. Needs GitHub.
123* [Work from your own channel](https://claude.com/docs/claude-tag/users/use-cases/your-own-channel.md): scratch questions, digests of channels you don't follow, and follow-ups on what you said you'd do
124124
125[Get started](/docs/claude-tag/users/getting-started.md) covers your first message, what you see while Claude works, and how to shape Claude's behavior in your channel.
125[Get started](https://claude.com/docs/claude-tag/users/getting-started.md) covers your first message, what you see while Claude works, and how to shape Claude's behavior in your channel.
126126
127127For administrators
128128
from line 135
135135
136136Once you launch, everyone in a channel Claude is in can use Claude Tag immediately, with no per-user setup.
137137
138Claude Tag starts with no access of its own to your external systems. After you launch, you connect the services Claude will work in, such as your issue tracker or data warehouse, and grant repositories to the Claude GitHub App. Members can also let Claude use their own [personal connectors](/docs/claude-tag/concepts/personal-connectors.md) for their requests.
138Claude Tag starts with no access of its own to your external systems. After you launch, you connect the services Claude will work in, such as your issue tracker or data warehouse, and grant repositories to the Claude GitHub App. Members can also let Claude use their own [personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) for their requests.
139139
140[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.
140[Set up Claude Tag](https://claude.com/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.
141141
142142Security review
143[Security and data handling](/docs/claude-tag/concepts/security-and-data.md)
143[Security and data handling](https://claude.com/docs/claude-tag/concepts/security-and-data.md)
144144
145145The security model, what admins can and can't restrict, audit trails, and network requirements.
146146
147147## Where to start with Claude Tag
148148
149> **[Set up Claude Tag](/docs/claude-tag/admins/setup-overview)**
149> **[Set up Claude Tag](https://claude.com/docs/claude-tag/admins/setup-overview)**
150150>
151151> Admins: pair your Slack workspace and launch
152152
153> **[Hand Claude Tag your first task](/docs/claude-tag/users/getting-started.md)**
153> **[Hand Claude Tag your first task](https://claude.com/docs/claude-tag/users/getting-started.md)**
154154>
155155> It's already in your channel: send your first message
156156
157> **[How Claude Tag works](/docs/claude-tag/concepts/how-it-works.md)**
157> **[How Claude Tag works](https://claude.com/docs/claude-tag/concepts/how-it-works.md)**
158158>
159159> The session model, what it can read, and how memory follows places
160160
161> **[Use case library](/docs/claude-tag/users/use-cases.md)**
161> **[Use case library](https://claude.com/docs/claude-tag/users/use-cases.md)**
162162>
163163> Prompts to paste, by team and connection
164164
claude-tag/users/commands Changed · +13 / -13 lines
from line 18
1818
1919Claude replies with the commands it understands in your workspace. The list can differ by workspace, since a command can be enabled for some workspaces and not others.
2020
21In a [Slack Connect channel](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), one shared with another company, only `!help`, `!mute`, `!unmute`, `!restart`, and `!fast` work, and people from the other company can use only `!help`.
21In a [Slack Connect channel](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), one shared with another company, only `!help`, `!mute`, `!unmute`, `!restart`, and `!fast` work, and people from the other company can use only `!help`.
2222
2323## Get the link to configure a channel
2424
from line 26
2626@Claude !configure
2727```
2828
29Run `!configure` in a channel, and Claude replies in the thread with a link to that channel's Configure page on claude.ai. On that page you [tailor how Claude works in the channel](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel), for example by editing its channel instructions, and it's the same page the **Configure** link in the footer of any Claude reply opens. In a DM with Claude there are no per-channel settings, so Claude replies there with a link to [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag) instead.
29Run `!configure` in a channel, and Claude replies in the thread with a link to that channel's Configure page on claude.ai. On that page you [tailor how Claude works in the channel](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel), for example by editing its channel instructions, and it's the same page the **Configure** link in the footer of any Claude reply opens. In a DM with Claude there are no per-channel settings, so Claude replies there with a link to [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag) instead.
3030
3131## Restart a stuck or wrong-context session
3232
from line 36
3636
3737Use this when a session is stuck, or when it's carrying context you don't want the next reply to build on. Claude archives the current session and starts a fresh one in its place.
3838
39Every thread Claude takes part in runs a session of its own, holding that one conversation. Some channels have one more session on top of the per-thread ones. That session belongs to the channel itself, and it's the session Claude works from at the channel's top level, outside any thread. When Claude [replies to a top-level message no one mentioned it in](/docs/claude-tag/users/when-claude-responds.md), the channel's session is the one replying.
39Every thread Claude takes part in runs a session of its own, holding that one conversation. Some channels have one more session on top of the per-thread ones. That session belongs to the channel itself, and it's the session Claude works from at the channel's top level, outside any thread. When Claude [replies to a top-level message no one mentioned it in](https://claude.com/docs/claude-tag/users/when-claude-responds.md), the channel's session is the one replying.
4040
4141Where you run `!restart` picks which session gets replaced:
4242
from line 69
6969@Claude !mute
7070```
7171
72Run `!mute` in a thread Claude is part of, and Claude stops replying there. Muting is per thread by design. Other threads, the channel's top level, [routine](/docs/claude-tag/users/proactivity.md) posts, and service notices are unaffected.
72Run `!mute` in a thread Claude is part of, and Claude stops replying there. Muting is per thread by design. Other threads, the channel's top level, [routine](https://claude.com/docs/claude-tag/users/proactivity.md) posts, and service notices are unaffected.
7373
7474There's no channel-level mute. If you run `!mute` at a channel's top level, Claude posts this hint:
7575
from line 77
7777:mute: Muting works per thread — reply `@Claude !mute` (or `!unmute`) inside the thread you mean.
7878```
7979
80To quiet unprompted replies across a whole channel, turn the channel's [**Respond automatically** setting](/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) off.
80To quiet unprompted replies across a whole channel, turn the channel's [**Respond automatically** setting](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) off.
8181
8282Unmute the same way:
8383
from line 106
106106@Claude !fast off
107107```
108108
109`!fast` turns on [fast mode](/docs/claude-tag/users/models.md#run-a-thread-in-fast-mode), which gives faster output at a higher cost per token. `!fast on` does the same, and `!fast off` returns to standard speed. Any other text after `!fast` makes the message an ordinary prompt.
109`!fast` turns on [fast mode](https://claude.com/docs/claude-tag/users/models.md#run-a-thread-in-fast-mode), which gives faster output at a higher cost per token. `!fast on` does the same, and `!fast off` returns to standard speed. Any other text after `!fast` makes the message an ordinary prompt.
110110
111111Fast mode runs on Opus models, so `!fast` can change the session's model as well as its speed. The footer of each Claude reply names the model the session is on.
112112
113113* **If the session is on an Opus model**, it stays on that model
114* **If the session is on another model, such as Sonnet**, Claude switches it to the newest Opus model [you can use](/docs/claude-tag/users/models.md#which-models-you-can-use). The session stays on that model after `!fast off`. To go back, [ask Claude to switch models](/docs/claude-tag/users/models.md#switch-the-model-in-a-thread).
114* **If the session is on another model, such as Sonnet**, Claude switches it to the newest Opus model [you can use](https://claude.com/docs/claude-tag/users/models.md#which-models-you-can-use). The session stays on that model after `!fast off`. To go back, [ask Claude to switch models](https://claude.com/docs/claude-tag/users/models.md#switch-the-model-in-a-thread).
115115
116116In both cases, replies speed up only if that Opus version [supports fast mode](https://code.claude.com/docs/en/fast-mode).
117117
118The command changes a different [session](/docs/claude-tag/concepts/glossary.md#session) depending on where you send it:
118The command changes a different [session](https://claude.com/docs/claude-tag/concepts/glossary.md#session) depending on where you send it:
119119
120120* **In a thread**, it changes that thread's session. In a channel thread Claude isn't part of yet, `!fast` starts the thread's session in fast mode and switches its model the same way, so your next request there runs fast from the start.
121121* **At a channel's top level**, it changes the channel's own session, the one Claude works from outside any thread. Thread sessions keep their speed. Claude's confirmation appears as a reply under your command. To turn fast mode off again, send `!fast off` at the top level, not in that reply thread.
from line 133
133133
134134| Claude replies | What to do |
135135| :- | :- |
136| `Fast mode isn't turned on for this organization. An organization owner can turn it on.` | Ask an Owner to [allow fast mode](/docs/claude-tag/admins/customize.md#allow-fast-mode) |
136| `Fast mode isn't turned on for this organization. An organization owner can turn it on.` | Ask an Owner to [allow fast mode](https://claude.com/docs/claude-tag/admins/customize.md#allow-fast-mode) |
137137| `Fast mode can't be changed for organizations with restricted compliance settings.` | Work at standard speed. Your organization's compliance settings don't allow fast mode. |
138138| `Fast mode isn't available for this session.` | Run the command in a new thread. If Claude gives the same reply there, fast mode isn't available in this channel. |
139139| `Only a workspace member who can use Claude here can change fast mode.` | Ask a full member of the workspace who can message Claude in this channel to run the command |
from line 159
159159@Claude !routines
160160```
161161
162Claude replies in the thread with the [routines](/docs/claude-tag/users/proactivity.md) set up in the channel: the scheduled jobs, watched channels, and other standing work it runs there. The list covers only that channel's routines.
162Claude replies in the thread with the [routines](https://claude.com/docs/claude-tag/users/proactivity.md) set up in the channel: the scheduled jobs, watched channels, and other standing work it runs there. The list covers only that channel's routines.
163163
164164* **For the current channel**, run `!routines` in that channel.
165165* **For another channel**, add the channel mention or its ID, as in `@Claude !routines #other-channel`. You need to be a member of that channel, and it must belong to your organization. Claude sends the list in a reply only you can see, so that channel's routines aren't posted for everyone in the channel where you asked.
from line 190
190190
191191## Related resources
192192
193* [Set up routines](/docs/claude-tag/users/proactivity.md): the standing work `!routines` lists, and how to create, edit, or disable it
194* [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without any command or mention at all
195* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access.md): the admin controls that decide who can message Claude at all, including its commands
193* [Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md): the standing work `!routines` lists, and how to create, edit, or disable it
194* [Control when Claude Tag responds](https://claude.com/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without any command or mention at all
195* [Restrict where Claude Tag operates](https://claude.com/docs/claude-tag/admins/restrict-access.md): the admin controls that decide who can message Claude at all, including its commands
196196
claude-tag/users/getting-started Changed · +21 / -21 lines
from line 6
66>
77> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
9Claude 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.md#restrict-who-can-use-claude)).
9Claude 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](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude)).
1010
1111## When to tag Claude in a channel versus a DM
1212
1313Where you tag Claude decides whose tools it uses and who sees the result.
1414
15* **Channel** for shared team work. The work happens in the open, so anything Claude does in the thread, including its checklist and results, is visible to everyone in the channel, and anyone can reply to steer the work. An admin sets what Claude can reach in each channel, and everyone who asks there gets the same access. By default you don't need a Claude account to tag Claude in a channel; the work bills to the organization. An admin can [restrict who can invoke Claude](/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude).
15* **Channel** for shared team work. The work happens in the open, so anything Claude does in the thread, including its checklist and results, is visible to everyone in the channel, and anyone can reply to steer the work. An admin sets what Claude can reach in each channel, and everyone who asks there gets the same access. By default you don't need a Claude account to tag Claude in a channel; the work bills to the organization. An admin can [restrict who can invoke Claude](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude).
1616 * Example: `@Claude where are we on the launch checklist? Pull what's still open from this channel and #design-review.`
17* **DM** for personal tasks. A one-to-one DM with Claude runs on your own claude.ai account with [your own connectors](/docs/connectors/getting-started.md). Every DM message reaches Claude without an @-mention. You can also DM Claude questions about getting started, like how to word a task or what to try first.
17* **DM** for personal tasks. A one-to-one DM with Claude runs on your own claude.ai account with [your own connectors](https://claude.com/docs/connectors/getting-started.md). Every DM message reaches Claude without an @-mention. You can also DM Claude questions about getting started, like how to word a task or what to try first.
1818 * Example: `Pull my afternoon meetings from my calendar and draft a one-line prep note for each.`
19* **Group DM** for shared work among a few people, without creating a channel. Claude uses the access an admin set for the workspace and the organization, and the work bills to the organization. See [Use Claude Tag in a group DM](/docs/claude-tag/users/group-dms.md).
19* **Group DM** for shared work among a few people, without creating a channel. Claude uses the access an admin set for the workspace and the organization, and the work bills to the organization. See [Use Claude Tag in a group DM](https://claude.com/docs/claude-tag/users/group-dms.md).
2020 * Example: `@Claude draft a rollout checklist for the pricing page change.`
2121
22See [team channels and personal DMs](/docs/claude-tag/concepts/how-it-works.md#team-channels-and-personal-dms) for the full comparison.
22See [team channels and personal DMs](https://claude.com/docs/claude-tag/concepts/how-it-works.md#team-channels-and-personal-dms) for the full comparison.
2323
24If your workspace previously used the earlier Claude in Slack app, see [how Claude Tag differs](/docs/claude-tag/admins/migrate-from-earlier.md) for what has changed.
24If your workspace previously used the earlier Claude in Slack app, see [how Claude Tag differs](https://claude.com/docs/claude-tag/admins/migrate-from-earlier.md) for what has changed.
2525
2626## Add Claude to a channel
2727
from line 51
5151
5252When a person first invites Claude to a channel, it posts a short intro on its own: it reads the channel's history and suggests a few tasks it could pick up. The intro doesn't post when a bot adds Claude, in org-shared channels, or in channels that already have memory.
5353
54The footer under each reply names the model that handled it. You can [choose a different model](/docs/claude-tag/users/models.md) yourself, and admins [set the default model for each channel](/docs/claude-tag/admins/customize.md#choose-the-model-for-a-scope). In a channel, the footer also has a **Configure** link; open it to [tailor how Claude works in this channel](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). Replies in DMs and in org-shared channels have no Configure link.
54The footer under each reply names the model that handled it. You can [choose a different model](https://claude.com/docs/claude-tag/users/models.md) yourself, and admins [set the default model for each channel](https://claude.com/docs/claude-tag/admins/customize.md#choose-the-model-for-a-scope). In a channel, the footer also has a **Configure** link; open it to [tailor how Claude works in this channel](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). Replies in DMs and in org-shared channels have no Configure link.
5555
5656| If you see | It means | Do this |
5757| :- | :- | :- |
58| Typing `@Claude` doesn't show **Claude** with an **APP** badge in the suggestion list | The Claude app isn't installed in your workspace | Ask your Slack admin to install the Claude app, and send them [the installation guide](/docs/claude-tag/admins/setup-overview#pair-your-slack-workspace) |
59| The mention sends but Claude doesn't reply | Setup isn't finished for this channel | Ask your Claude organization admin to enable Claude Tag for this channel, and send them [the setup guide](/docs/claude-tag/admins/setup-overview) with the channel name |
60| Claude replies "I couldn't find a Claude Code environment for your account" | Claude couldn't resolve an environment for this DM; one-to-one DMs run on your account rather than the organization's | Mention Claude again. If it keeps happening, see [I get an environment error in a DM](/docs/claude-tag/users/troubleshooting.md#i-get-an-environment-error-in-a-dm) |
58| Typing `@Claude` doesn't show **Claude** with an **APP** badge in the suggestion list | The Claude app isn't installed in your workspace | Ask your Slack admin to install the Claude app, and send them [the installation guide](https://claude.com/docs/claude-tag/admins/setup-overview#pair-your-slack-workspace) |
59| The mention sends but Claude doesn't reply | Setup isn't finished for this channel | Ask your Claude organization admin to enable Claude Tag for this channel, and send them [the setup guide](https://claude.com/docs/claude-tag/admins/setup-overview) with the channel name |
60| Claude replies "I couldn't find a Claude Code environment for your account" | Claude couldn't resolve an environment for this DM; one-to-one DMs run on your account rather than the organization's | Mention Claude again. If it keeps happening, see [I get an environment error in a DM](https://claude.com/docs/claude-tag/users/troubleshooting.md#i-get-an-environment-error-in-a-dm) |
6161
6262## Hand Claude a task
6363
from line 75
7575
7676Tasks run in the cloud, so Claude keeps working after you close Slack.
7777
78Replies in the thread reach Claude without re-mentioning. If the thread looks idle, Claude is usually still working; see [how to read its progress](/docs/claude-tag/concepts/how-it-works.md#track-claude%E2%80%99s-progress).
78Replies in the thread reach Claude without re-mentioning. If the thread looks idle, Claude is usually still working; see [how to read its progress](https://claude.com/docs/claude-tag/concepts/how-it-works.md#track-claude%E2%80%99s-progress).
7979
8080## What Claude can see
8181
from line 87
8787| A file you attach (image, screenshot, PDF, or another type) | Yes, up to a size limit that depends on the file type. See [Files you attach](#files-you-attach) |
8888| Other public channels in your workspace | By searching only, the same way a person searches Slack; Claude can find a message by keyword but can't read a channel's full history unless it's been added there |
8989| Private channels and DMs | Only from inside them. Adding Claude to a private channel lets it work there, but the channel stays unreadable from any other channel or DM. |
90| A link you paste, like a Google Doc or a webpage | If your admin allowed that site for this channel, or, for a file behind your own login, if you've [allowed Claude to use your connectors](/docs/claude-tag/concepts/personal-connectors.md). If neither applies, Claude tells you it can't reach it. |
90| A link you paste, like a Google Doc or a webpage | If your admin allowed that site for this channel, or, for a file behind your own login, if you've [allowed Claude to use your connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md). If neither applies, Claude tells you it can't reach it. |
9191| A Slack canvas | No |
92| A message you edited after sending | Yes. Each edit sends Claude a note showing the text before and after the edit. An edit never starts a new task on its own, so to be sure a correction is picked up, say it in a new reply; see [Reply in the thread to steer](/docs/claude-tag/concepts/how-it-works.md#reply-in-the-thread-to-steer) |
92| A message you edited after sending | Yes. Each edit sends Claude a note showing the text before and after the edit. An edit never starts a new task on its own, so to be sure a correction is picked up, say it in a new reply; see [Reply in the thread to steer](https://claude.com/docs/claude-tag/concepts/how-it-works.md#reply-in-the-thread-to-steer) |
9393
9494The fastest way to find out for your channel is to ask: `@Claude can you read the doc I just linked?` gets you a yes or a "that site isn't allowed here."
9595
from line 110
110110
111111### Which messages Claude reads
112112
113* An @-mention guarantees a response. Claude may also respond to a message that doesn't mention it when it judges a reply is warranted; include the mention to guarantee one. It receives the thread's root message and earlier replies for context when you mention it mid-thread; for details on the window, refer to [what Claude sees when you mention it](/docs/claude-tag/concepts/how-it-works.md#conversation-context).
113* An @-mention guarantees a response. Claude may also respond to a message that doesn't mention it when it judges a reply is warranted; include the mention to guarantee one. It receives the thread's root message and earlier replies for context when you mention it mid-thread; for details on the window, refer to [what Claude sees when you mention it](https://claude.com/docs/claude-tag/concepts/how-it-works.md#conversation-context).
114114* Once mentioned in a thread, Claude follows the rest of that thread and may reply without another mention.
115115* While working on a task, Claude can search the workspace's public channels by keyword, the same way a person searches Slack. It can't read a channel's full history unless it's been added there.
116116
117To quiet Claude in a thread or remove it from a channel, see [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds.md).
117To quiet Claude in a thread or remove it from a channel, see [Control when Claude Tag responds](https://claude.com/docs/claude-tag/users/when-claude-responds.md).
118118
119119## Give Claude standing instructions
120120
from line 124
124124@Claude remember for this channel: keep replies short, and always include a link to the source.
125125```
126126
127The instruction saves to [channel memory](/docs/claude-tag/users/memory.md) and applies to everyone's threads in the channel. Verify with "what do you remember about this channel?"
127The instruction saves to [channel memory](https://claude.com/docs/claude-tag/users/memory.md) and applies to everyone's threads in the channel. Verify with "what do you remember about this channel?"
128128
129129## Related resources
130130
131* [Use case library](/docs/claude-tag/users/use-cases.md): every shape of work, each with the prompts to paste
132* [Good habits](/docs/claude-tag/users/good-habits.md): how to write tasks that finish
133* [Set up routines](/docs/claude-tag/users/proactivity.md): once a task works, have Claude run it on its own schedule
134* [Commands](/docs/claude-tag/users/commands.md): exact words starting with `!` that run a fixed action, like `!restart` for a stuck session
135* [Personal connectors in channels](/docs/claude-tag/concepts/personal-connectors.md): how Claude can use your own claude.ai connectors for a task you hand it in a channel
131* [Use case library](https://claude.com/docs/claude-tag/users/use-cases.md): every shape of work, each with the prompts to paste
132* [Good habits](https://claude.com/docs/claude-tag/users/good-habits.md): how to write tasks that finish
133* [Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md): once a task works, have Claude run it on its own schedule
134* [Commands](https://claude.com/docs/claude-tag/users/commands.md): exact words starting with `!` that run a fixed action, like `!restart` for a stuck session
135* [Personal connectors in channels](https://claude.com/docs/claude-tag/concepts/personal-connectors.md): how Claude can use your own claude.ai connectors for a task you hand it in a channel
136136
claude-tag/users/good-habits Changed · +31 / -31 lines
from line 28
2828
2929Ask Claude to notify a user group, such as an on-call rotation. Claude mentions the group, and Slack notifies its members. If Claude writes the group's @handle as plain text instead of mentioning the group, Slack notifies no one, so ask Claude to notify the group rather than to include its handle.
3030
31If Claude replies with re-approval guidance instead of mentioning the group, your workspace's Claude app predates a Slack permission that group mentions need. Ask a Slack admin to re-approve the app, and send them [Slack app permissions](/docs/claude-tag/admins/troubleshooting.md#slack-app-permissions).
31If Claude replies with re-approval guidance instead of mentioning the group, your workspace's Claude app predates a Slack permission that group mentions need. Ask a Slack admin to re-approve the app, and send them [Slack app permissions](https://claude.com/docs/claude-tag/admins/troubleshooting.md#slack-app-permissions).
3232
3333Claude never pings @channel, @here, or @everyone.
3434
from line 42
4242
4343### How much detail to give
4444
45Claude [reads the thread you tag it in, can search the workspace's public channels, and works with the channel's connections](/docs/claude-tag/users/getting-started.md#what-claude-can-see). If the background for your task is already in a thread, channel, or connected tool, link to it and state the outcome you want in one sentence. You don't need to restate the background.
45Claude [reads the thread you tag it in, can search the workspace's public channels, and works with the channel's connections](https://claude.com/docs/claude-tag/users/getting-started.md#what-claude-can-see). If the background for your task is already in a thread, channel, or connected tool, link to it and state the outcome you want in one sentence. You don't need to restate the background.
4646
4747```text wrap theme={null}
4848@Claude take over the bug in the thread linked above. Fix it and open a draft PR.
from line 78
7878
7979For tasks Claude closes itself, ask it to attach proof, such as the source link, the chart, the test output, or the diff. You read the proof, not the transcript.
8080
81For long-running work, make getting the deliverable somewhere durable part of the definition. Post the file to the thread, push the branch, or open the draft pull request as it goes. See [what survives between replies](/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies).
81For long-running work, make getting the deliverable somewhere durable part of the definition. Post the file to the thread, push the branch, or open the draft pull request as it goes. See [what survives between replies](https://claude.com/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies).
8282
8383Calibrate over time. Check everything it produces in a new channel at first, and widen what it closes on its own as its output holds up under review.
8484
from line 118
118118@Claude remember for this channel: keep replies to three sentences unless someone asks for detail.
119119```
120120
121Verify what stuck by asking what it remembers about the channel. See [What Claude Tag remembers](/docs/claude-tag/users/memory.md).
121Verify what stuck by asking what it remembers about the channel. See [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md).
122122
123123## Work in the right place
124124
from line 128
128128
129129Each thread runs its own session, and the session carries the whole conversation into every reply. Keep follow-ups on the same task in the same thread, where Claude already has the context.
130130
131Start a new thread for each new task. The fresh session begins with full room for the work, picks up any configuration changes made since the old thread began, and keeps each piece of work reviewable on its own. A thread that accumulates many tasks eventually [grows past what one session can hold](/docs/claude-tag/users/troubleshooting.md#this-conversation-is-too-long-for-me-to-process).
131Start a new thread for each new task. The fresh session begins with full room for the work, picks up any configuration changes made since the old thread began, and keeps each piece of work reviewable on its own. A thread that accumulates many tasks eventually [grows past what one session can hold](https://claude.com/docs/claude-tag/users/troubleshooting.md#this-conversation-is-too-long-for-me-to-process).
132132
133To start several independent tasks from inside an existing thread, [ask Claude to open a thread for each](/docs/claude-tag/users/prompt-library.md#fan-out-work-across-threads). To continue the current discussion in a fresh thread, run [`!fork`](/docs/claude-tag/users/commands#fork-a-thread).
133To start several independent tasks from inside an existing thread, [ask Claude to open a thread for each](https://claude.com/docs/claude-tag/users/prompt-library.md#fan-out-work-across-threads). To continue the current discussion in a fresh thread, run [`!fork`](https://claude.com/docs/claude-tag/users/commands#fork-a-thread).
134134
135135### Pick the right surface
136136
137Channel access belongs to the channel, and access in a one-to-one DM belongs to you. A channel can also be yours alone. Create one with just you and Claude in it, and it works the same way a team channel does. The table compares the three surfaces. For a group DM, see [Use Claude Tag in a group DM](/docs/claude-tag/users/group-dms.md).
137Channel access belongs to the channel, and access in a one-to-one DM belongs to you. A channel can also be yours alone. Create one with just you and Claude in it, and it works the same way a team channel does. The table compares the three surfaces. For a group DM, see [Use Claude Tag in a group DM](https://claude.com/docs/claude-tag/users/group-dms.md).
138138
139139| | A team channel | Your own channel | A one-to-one DM |
140140| :- | :- | :- | :- |
from line 144
144144| Billing | The organization | The organization | Your seat |
145145| Best for | Shared work the team should see and steer | Your own questions, digests, and follow-ups, kept where a teammate can pick them up | Personal tasks on your own connections, or data that shouldn't run through a shared channel connection |
146146
147[Routines](/docs/claude-tag/users/proactivity.md) belong to a channel too. You set standing work up in the channel where it should post, and it runs with that channel's connections. [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel.md) shows what a channel of your own is good for.
147[Routines](https://claude.com/docs/claude-tag/users/proactivity.md) belong to a channel too. You set standing work up in the channel where it should post, and it runs with that channel's connections. [Work from your own channel](https://claude.com/docs/claude-tag/users/use-cases/your-own-channel.md) shows what a channel of your own is good for.
148148
149A DM can still answer questions about a public channel when the answer should stay private. Name the channel in the DM, as in `summarize the last week of #product-feedback`. Claude's Slack search covers public channels in this workspace from a DM the same as from a channel, so the DM advantage is privacy of the answer, not broader reach. Workspace search is unavailable in [channels that include guests](/docs/claude-tag/admins/restrict-access.md#restrict-guest-channels), so ask from a DM or from a channel without guests.
149A DM can still answer questions about a public channel when the answer should stay private. Name the channel in the DM, as in `summarize the last week of #product-feedback`. Claude's Slack search covers public channels in this workspace from a DM the same as from a channel, so the DM advantage is privacy of the answer, not broader reach. Workspace search is unavailable in [channels that include guests](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-guest-channels), so ask from a DM or from a channel without guests.
150150
151151Reading a public channel's full history, rather than what search finds, needs Claude to be a member of that channel. If it says it can't read a public channel, `/invite @Claude` from inside that channel adds it.
152152
153Claude can also post into other public channels, and the rules depend on where you ask. See [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works.md#what-claude-can-do-in-other-channels).
153Claude can also post into other public channels, and the rules depend on where you ask. See [What Claude can do in other channels](https://claude.com/docs/claude-tag/concepts/how-it-works.md#what-claude-can-do-in-other-channels).
154154
155155A private channel is readable only from inside it. Inviting Claude lets it work in that channel, but Claude can't read the private channel's messages from any other channel or DM. To ask about a private channel, ask in that channel.
156156
157Claude can't post into a channel in a different workspace. In a [Slack Connect channel](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), one shared with another company, Claude answers only if an Owner or a Claude Tag admin has turned it on there, and then with [limited access](/docs/claude-tag/admins/restrict-access.md#what-access-claude-has-in-a-slack-connect-channel).
157Claude can't post into a channel in a different workspace. In a [Slack Connect channel](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), one shared with another company, Claude answers only if an Owner or a Claude Tag admin has turned it on there, and then with [limited access](https://claude.com/docs/claude-tag/admins/restrict-access.md#what-access-claude-has-in-a-slack-connect-channel).
158158
159159When more than one surface would work, prefer a channel. Work that happens there compounds, because Claude can draw on it in later threads and teammates can find it, redirect it, or build on it.
160160
161If Claude says it can't reach something in a channel, the channel likely wasn't granted that access. See [How agent identity works](/docs/claude-tag/concepts/agent-identity.md).
161If Claude says it can't reach something in a channel, the channel likely wasn't granted that access. See [How agent identity works](https://claude.com/docs/claude-tag/concepts/agent-identity.md).
162162
163163### Teach Claude something that sticks
164164
from line 166
166166
167167| You want Claude to know | Put it in | Who can write it | Reaches |
168168| :- | :- | :- | :- |
169| How this channel should behave: format, tone, when to respond | [**Channel memory**](/docs/claude-tag/users/memory.md) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |
170| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](/docs/claude-tag/admins/configure-github.md#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |
171| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) | This channel |
172| A correction for this channel that you don't want to raise in the channel | [**Managed instructions**](/docs/claude-tag/admins/managed-by.md#correct-claude-privately-from-a-managing-channel), written from a private managing channel | Full workspace members in the managing channel who have a Claude account in your organization, after an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) sets it up | This channel |
173| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](/docs/claude-tag/admins/skills-repo.md) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every workspace and channel it's added to |
174| Standing rules across many channels | [**Workspace instructions** or **Slack instructions**](/docs/claude-tag/admins/attach-to-scope.md#add-custom-instructions) in Claude Tag admin settings | An organization Owner, or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) for a workspace | Every channel in that workspace, or in all of Slack |
169| How this channel should behave: format, tone, when to respond | [**Channel memory**](https://claude.com/docs/claude-tag/users/memory.md) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |
170| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](https://claude.com/docs/claude-tag/admins/configure-github.md#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |
171| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) | This channel |
172| A correction for this channel that you don't want to raise in the channel | [**Managed instructions**](https://claude.com/docs/claude-tag/admins/managed-by.md#correct-claude-privately-from-a-managing-channel), written from a private managing channel | Full workspace members in the managing channel who have a Claude account in your organization, after an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) sets it up | This channel |
173| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](https://claude.com/docs/claude-tag/admins/skills-repo.md) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every workspace and channel it's added to |
174| Standing rules across many channels | [**Workspace instructions** or **Slack instructions**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#add-custom-instructions) in Claude Tag admin settings | An organization Owner, or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) for a workspace | Every channel in that workspace, or in all of Slack |
175175
176176The first three are yours to write. You can still ask Claude to draft a skill change as a pull request for an admin to review:
177177
from line 179
179179@Claude that worked. Open a PR to the skills repo so this query pattern is part of the Datadog skill.
180180```
181181
182See [the admin guide to a skills repository](/docs/claude-tag/admins/skills-repo.md) for what that setup gives you.
182See [the admin guide to a skills repository](https://claude.com/docs/claude-tag/admins/skills-repo.md) for what that setup gives you.
183183
184A `CLAUDE.md` carries setup as well as conventions. Sessions run in a sandbox with a standard set of preinstalled tools. If the repository needs more, such as a language runtime or a database client, put the install commands in `CLAUDE.md`, and Claude [runs them when its work needs them](/docs/claude-tag/admins/configure-github.md#install-project-dependencies).
184A `CLAUDE.md` carries setup as well as conventions. Sessions run in a sandbox with a standard set of preinstalled tools. If the repository needs more, such as a language runtime or a database client, put the install commands in `CLAUDE.md`, and Claude [runs them when its work needs them](https://claude.com/docs/claude-tag/admins/configure-github.md#install-project-dependencies).
185185
186A `CLAUDE.md` is guidance; a required status check is a gate. If a pull request must carry a label or pass a check, make that a repository rule rather than a memory note or a skill. The same goes for review: to require an approval from someone other than the person who asked Claude for the change, see [Require a second approval on Claude's pull requests](/docs/claude-tag/admins/configure-github.md#require-a-second-approval-on-claude%E2%80%99s-pull-requests).
186A `CLAUDE.md` is guidance; a required status check is a gate. If a pull request must carry a label or pass a check, make that a repository rule rather than a memory note or a skill. The same goes for review: to require an approval from someone other than the person who asked Claude for the change, see [Require a second approval on Claude's pull requests](https://claude.com/docs/claude-tag/admins/configure-github.md#require-a-second-approval-on-claude%E2%80%99s-pull-requests).
187187
188188### Configure Claude for a channel
189189
190The **Configure** link in the footer of any Claude reply in a channel opens a page where you tailor how Claude behaves in that channel. You can also send [`@Claude !configure`](/docs/claude-tag/users/commands#get-the-link-to-configure-a-channel) in the channel, and Claude replies with a link to the same page. The page is on claude.ai, so you need to be signed in to your Claude organization to edit it, and an admin can [restrict editing](/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) so the page is read-only for members.
190The **Configure** link in the footer of any Claude reply in a channel opens a page where you tailor how Claude behaves in that channel. You can also send [`@Claude !configure`](https://claude.com/docs/claude-tag/users/commands#get-the-link-to-configure-a-channel) in the channel, and Claude replies with a link to the same page. The page is on claude.ai, so you need to be signed in to your Claude organization to edit it, and an admin can [restrict editing](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) so the page is read-only for members.
191191
192The **Respond automatically** toggle on that page controls whether Claude replies in the channel without an @-mention. See [Turn automatic replies on or off](/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for what the setting does and the other places you can change it.
192The **Respond automatically** toggle on that page controls whether Claude replies in the channel without an @-mention. See [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for what the setting does and the other places you can change it.
193193
194194Use the **Channel instructions** field on that page to write standing guidance Claude reads in every new session in the channel: the channel's purpose, its conventions, the tone replies should take, and anything Claude should do or avoid there. Channel instructions outrank channel memory and sit alongside any instructions an admin has set for the workspace or organization. Save the field and the change applies to new sessions started in the channel.
195195
196The page's **Tools and access** tab shows **Connections**, the services Claude can reach from this channel, along with any allowed domains. You can see those lists but not change them on this page. The same tab's **Plugins** card lists the channel's plugins, and you can add plugins there unless an admin has restricted editing to admins. If you've been made a [channel manager](/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) for the channel, the tab also has **Access bundles** and **GitHub repositories** cards you can edit.
196The page's **Tools and access** tab shows **Connections**, the services Claude can reach from this channel, along with any allowed domains. You can see those lists but not change them on this page. The same tab's **Plugins** card lists the channel's plugins, and you can add plugins there unless an admin has restricted editing to admins. If you've been made a [channel manager](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) for the channel, the tab also has **Access bundles** and **GitHub repositories** cards you can edit.
197197
198198## Keep thread count and review rate matched
199199
from line 205
205205
206206## Related resources
207207
208* [Use case library](/docs/claude-tag/users/use-cases.md): the full setups these habits make reliable
209* [What Claude Tag remembers](/docs/claude-tag/users/memory.md): make corrections stick
208* [Use case library](https://claude.com/docs/claude-tag/users/use-cases.md): the full setups these habits make reliable
209* [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md): make corrections stick
210210
claude-tag/users/group-dms Changed · +18 / -18 lines
from line 8
88
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
11If 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.md#group-dms-aren%E2%80%99t-supported-yet).
11If 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](https://claude.com/docs/claude-tag/users/troubleshooting.md#group-dms-aren%E2%80%99t-supported-yet).
1212
13This page is for Slack members. It covers how to add Claude, what Claude can reach, when it replies, how to make it quieter, what differs from a channel, and what to do when Claude doesn't answer. If you administer Claude for your organization, see [the settings that apply to group DMs](/docs/claude-tag/admins/restrict-access.md#group-dms).
13This page is for Slack members. It covers how to add Claude, what Claude can reach, when it replies, how to make it quieter, what differs from a channel, and what to do when Claude doesn't answer. If you administer Claude for your organization, see [the settings that apply to group DMs](https://claude.com/docs/claude-tag/admins/restrict-access.md#group-dms).
1414
1515## Add Claude to a group DM
1616
from line 22
2222
2323Claude replies in a thread under your message.
2424
25An admin decides [who can use Claude](/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude), and that choice covers group DMs as well as channels.
25An admin decides [who can use Claude](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude), and that choice covers group DMs as well as channels.
2626
2727## Access and billing in a group DM
2828
29In a group DM, Claude acts with [its own service accounts](/docs/claude-tag/concepts/agent-identity.md). If you've connected a Claude account, a one-to-one DM with Claude runs on [your own account](/docs/claude-tag/concepts/agent-identity.md#direct-message-channels) instead.
29In a group DM, Claude acts with [its own service accounts](https://claude.com/docs/claude-tag/concepts/agent-identity.md). If you've connected a Claude account, a one-to-one DM with Claude runs on [your own account](https://claude.com/docs/claude-tag/concepts/agent-identity.md#direct-message-channels) instead.
3030
3131* **Access.** Claude uses the connections, instructions, and repositories an admin set for the workspace and the organization. A connection an admin attached to one channel doesn't apply.
3232* **Billing.** The work bills to your organization, not to your seat.
33* **Your own connectors.** Where [personal connectors in channels](/docs/claude-tag/concepts/personal-connectors.md) are on for your organization, Claude can use the connectors on your claude.ai account for a task you ask for, after you allow it. Only your own requests use them.
33* **Your own connectors.** Where [personal connectors in channels](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) are on for your organization, Claude can use the connectors on your claude.ai account for a task you ask for, after you allow it. Only your own requests use them.
3434
3535## When Claude replies in a group DM
3636
from line 50
5050
5151Claude can't make the change in these cases:
5252
53* **Channel-only access.** A guest is in the group DM, and Claude runs there with [channel-only access](/docs/claude-tag/admins/restrict-access.md#how-channel-only-works).
54* **Blocked member edits.** An admin set [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) to **Block** for the workspace or the organization.
53* **Channel-only access.** A guest is in the group DM, and Claude runs there with [channel-only access](https://claude.com/docs/claude-tag/admins/restrict-access.md#how-channel-only-works).
54* **Blocked member edits.** An admin set [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) to **Block** for the workspace or the organization.
5555
5656**1. Ask Claude**
5757
from line 79
7979
8080### Quiet Claude in one thread of a group DM
8181
82In a thread that started with an `@Claude` mention, send [`@Claude !mute`](/docs/claude-tag/users/commands#mute-or-unmute-a-thread). `!mute` works on one thread at a time.
82In a thread that started with an `@Claude` mention, send [`@Claude !mute`](https://claude.com/docs/claude-tag/users/commands#mute-or-unmute-a-thread). `!mute` works on one thread at a time.
8383
8484## Differences between a group DM and a channel
8585
8686These parts of working with Claude differ between a group DM and a channel:
8787
88* **Settings.** A group DM has no [Configure page](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel), so you can't give it its own instructions or connections.
89* **Memory.** Claude keeps notes for the group DM and reads only those notes there. It doesn't read or add to the [workspace notes](/docs/claude-tag/users/memory.md#channel-and-workspace-memory).
90* **Routines.** A [routine](/docs/claude-tag/users/proactivity.md) you set up in a group DM posts its output in that group DM only.
91* **Other channels.** Claude can't post, reply, or react outside the group DM. [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works.md#what-claude-can-do-in-other-channels) covers what it can read.
92* **Forking.** You can't [fork a thread](/docs/claude-tag/users/commands.md#fork-a-thread) from a group DM.
88* **Settings.** A group DM has no [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel), so you can't give it its own instructions or connections.
89* **Memory.** Claude keeps notes for the group DM and reads only those notes there. It doesn't read or add to the [workspace notes](https://claude.com/docs/claude-tag/users/memory.md#channel-and-workspace-memory).
90* **Routines.** A [routine](https://claude.com/docs/claude-tag/users/proactivity.md) you set up in a group DM posts its output in that group DM only.
91* **Other channels.** Claude can't post, reply, or react outside the group DM. [What Claude can do in other channels](https://claude.com/docs/claude-tag/concepts/how-it-works.md#what-claude-can-do-in-other-channels) covers what it can read.
92* **Forking.** You can't [fork a thread](https://claude.com/docs/claude-tag/users/commands.md#fork-a-thread) from a group DM.
9393
9494## When Claude doesn't answer in a group DM
9595
from line 97
9797
9898| What you see | Why Claude can't answer | What to do |
9999| :- | :- | :- |
100| "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead." | Who is in the group DM, or how Slack shares it, keeps Claude from answering | See [Group DMs aren't supported yet](/docs/claude-tag/users/troubleshooting.md#group-dms-aren%E2%80%99t-supported-yet) |
100| "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead." | Who is in the group DM, or how Slack shares it, keeps Claude from answering | See [Group DMs aren't supported yet](https://claude.com/docs/claude-tag/users/troubleshooting.md#group-dms-aren%E2%80%99t-supported-yet) |
101101| "Your Claude admin has disabled sending direct messages to Claude." | An admin turned off direct messages, which covers group DMs too | Ask in a channel, or ask your admin about turning direct messages on |
102102| "Claude doesn't respond in channels that include guests." | The group DM includes a Slack guest, and your admin's guest setting keeps Claude from replying | Start a group DM without the guest, or ask your admin about the guest setting |
103103| "Claude is disabled in this channel." | An admin turned Claude off for the workspace | Ask your admin about turning Claude on for the workspace |
104104| "This workspace only lets people with a connected Claude account work with me." Only you can see this notice | An admin restricted who can use Claude | Connect your Claude account, then send your message again |
105105| No reply and no notice | Claude isn't in the group DM | Start a new group DM that includes Claude |
106| No reply and no notice | Your workspace uses the [earlier Claude in Slack](/docs/claude-tag/admins/migrate-from-earlier.md) | Ask your admin which version answers in your workspace |
106| No reply and no notice | Your workspace uses the [earlier Claude in Slack](https://claude.com/docs/claude-tag/admins/migrate-from-earlier.md) | Ask your admin which version answers in your workspace |
107107
108108## Related resources
109109
110* [Get started with Claude Tag](/docs/claude-tag/users/getting-started.md): choose between a channel, a group DM, and a one-to-one DM
111* [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without an @-mention
112* [How agent identity works](/docs/claude-tag/concepts/agent-identity.md): whose accounts Claude acts with in each place
110* [Get started with Claude Tag](https://claude.com/docs/claude-tag/users/getting-started.md): choose between a channel, a group DM, and a one-to-one DM
111* [Control when Claude Tag responds](https://claude.com/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without an @-mention
112* [How agent identity works](https://claude.com/docs/claude-tag/concepts/agent-identity.md): whose accounts Claude acts with in each place
113113
claude-tag/users/memory Changed · +6 / -6 lines
from line 10
1010
1111Memory accumulates three ways:
1212
13* **You tell Claude.** Say "remember for this channel: reports go out as tables" and it saves the instruction. To save details from a document, [attach the file](/docs/claude-tag/users/getting-started.md#files-you-attach) and name what to remember. Claude saves those details, not the file.
13* **You tell Claude.** Say "remember for this channel: reports go out as tables" and it saves the instruction. To save details from a document, [attach the file](https://claude.com/docs/claude-tag/users/getting-started.md#files-you-attach) and name what to remember. Claude saves those details, not the file.
1414* **Claude saves facts on its own.** While working it keeps notes like decisions the channel made.
1515* **Claude can read past sessions.** Ask it to look back and it lists earlier sessions in the channel and reads their transcripts; it can't full-text search across them, so name a timeframe or topic.
1616
from line 28
2828| Private channel | That channel's notes, plus the workspace notes (read-only) | That channel's notes only |
2929| Group DM | That group DM's notes only | That group DM's notes only |
3030
31Other workspaces stay separate. One-to-one direct messages stay separate too. Claude keeps notes for each one-to-one direct-message conversation, stored with the workspace rather than with your Claude account. Those notes are deleted when an Owner [disconnects the workspace](/docs/claude-tag/admins/workspaces.md#revoke-a-pairing), not when you disconnect your own Claude account in Slack.
31Other workspaces stay separate. One-to-one direct messages stay separate too. Claude keeps notes for each one-to-one direct-message conversation, stored with the workspace rather than with your Claude account. Those notes are deleted when an Owner [disconnects the workspace](https://claude.com/docs/claude-tag/admins/workspaces.md#revoke-a-pairing), not when you disconnect your own Claude account in Slack.
3232
3333If a channel switches between public and private, its channel notes stay with the channel, and Claude keeps reading and adding to them there. Workspace notes Claude saved from the channel while it was public stay in the workspace notes. If those shouldn't stay shared, ask an Owner to delete them from the workspace's memory files in [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag).
3434
from line 61
6161Two habits keep memory useful over time:
6262
6363* **After correcting an entry, have Claude record the fix.** "Update your memory for this channel so this doesn't happen again" turns a one-time fix into a standing one.
64* **Prune what your work has outgrown.** Entries written weeks ago can describe a repository, owner, or convention that no longer exists. Ask Claude in the channel to review its memory and drop the entries that no longer apply. For ongoing upkeep, set up a [routine](/docs/claude-tag/users/proactivity.md) that repeats the review on a schedule; weekly works well.
64* **Prune what your work has outgrown.** Entries written weeks ago can describe a repository, owner, or convention that no longer exists. Ask Claude in the channel to review its memory and drop the entries that no longer apply. For ongoing upkeep, set up a [routine](https://claude.com/docs/claude-tag/users/proactivity.md) that repeats the review on a schedule; weekly works well.
6565
66An Owner in your Claude organization can view, edit, or delete the [memory files](/docs/claude-tag/admins/audit.md) of a workspace and its channels.
66An Owner in your Claude organization can view, edit, or delete the [memory files](https://claude.com/docs/claude-tag/admins/audit.md) of a workspace and its channels.
6767
6868## Related resources
6969
70* [How Claude Tag works](/docs/claude-tag/concepts/how-it-works.md): the scope, channel, and thread model behind memory
71* [Good habits](/docs/claude-tag/users/good-habits.md): habits that keep memory accurate
70* [How Claude Tag works](https://claude.com/docs/claude-tag/concepts/how-it-works.md): the scope, channel, and thread model behind memory
71* [Good habits](https://claude.com/docs/claude-tag/users/good-habits.md): habits that keep memory accurate
7272
claude-tag/users/models Changed · +8 / -8 lines
from line 34
3434@Claude use Sonnet for this thread, and make it the default model for this channel.
3535```
3636
37Claude sets the channel's default model. New threads in the channel start on it. If you asked for a family rather than a version, the default keeps following that family: when your organization gets a newer model in it, new threads start on the newer model without anyone changing the setting. A thread already underway switches to it at the next message anyone posts there, unless someone in that thread has already had Claude switch models. If an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) has set **Channel member edits** to **Block** for the channel, Claude declines to set the channel default; ask for the thread alone instead.
37Claude sets the channel's default model. New threads in the channel start on it. If you asked for a family rather than a version, the default keeps following that family: when your organization gets a newer model in it, new threads start on the newer model without anyone changing the setting. A thread already underway switches to it at the next message anyone posts there, unless someone in that thread has already had Claude switch models. If an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) has set **Channel member edits** to **Block** for the channel, Claude declines to set the channel default; ask for the thread alone instead.
3838
39An Owner sets the same default in Claude Tag admin settings for the whole organization or for one workspace or channel, and a Claude Tag admin can set it for a workspace or channel; see [choose the model for a scope](/docs/claude-tag/admins/customize.md#choose-the-model-for-a-scope).
39An Owner sets the same default in Claude Tag admin settings for the whole organization or for one workspace or channel, and a Claude Tag admin can set it for a workspace or channel; see [choose the model for a scope](https://claude.com/docs/claude-tag/admins/customize.md#choose-the-model-for-a-scope).
4040
4141## Choose the model for your direct messages
4242
from line 48
4848
4949Fast mode gives a thread faster output at a higher cost per token. It's the same [fast mode as in Claude Code](https://code.claude.com/docs/en/fast-mode), and that page lists the models that support it and what it costs. Use it where response time matters more than cost, such as a thread working a live alert.
5050
51Fast mode is available once an Owner [allows it for your organization](/docs/claude-tag/admins/customize.md#allow-fast-mode). To turn it on, send the [`!fast` command](/docs/claude-tag/users/commands#turn-fast-mode-on-or-off) in the thread.
51Fast mode is available once an Owner [allows it for your organization](https://claude.com/docs/claude-tag/admins/customize.md#allow-fast-mode). To turn it on, send the [`!fast` command](https://claude.com/docs/claude-tag/users/commands#turn-fast-mode-on-or-off) in the thread.
5252
5353```text wrap theme={null}
5454@Claude !fast
from line 62
6262
6363* You send `@Claude !fast off`
6464* You ask Claude to [switch models](#switch-the-model-in-a-thread)
65* The thread's session is replaced, for example when you [restart it](/docs/claude-tag/users/commands.md#restart-a-stuck-or-wrong-context-session)
65* The thread's session is replaced, for example when you [restart it](https://claude.com/docs/claude-tag/users/commands.md#restart-a-stuck-or-wrong-context-session)
6666
6767After `!fast off`, a thread that Claude switched to Opus stays on Opus. To return to the earlier model, ask Claude to switch.
6868
from line 78
7878
7979If you ask for a model that isn't on the list, Claude tells you it isn't available, and the thread stays on the model it was already using.
8080
81For how your organization's model settings apply in Slack, see [Models your organization allows](/docs/claude-tag/admins/customize.md#models-your-organization-allows).
81For how your organization's model settings apply in Slack, see [Models your organization allows](https://claude.com/docs/claude-tag/admins/customize.md#models-your-organization-allows).
8282
8383## Related resources
8484
85* [Get started](/docs/claude-tag/users/getting-started.md): what else the reply footer links to
86* [Commands](/docs/claude-tag/users/commands.md#turn-fast-mode-on-or-off): where `!fast` works and what Claude replies when it can't change the speed
87* [Customize Claude Tag](/docs/claude-tag/admins/customize.md#choose-the-model-for-a-scope): how admins set a default model per workspace or channel, and how the organization's model policy applies
85* [Get started](https://claude.com/docs/claude-tag/users/getting-started.md): what else the reply footer links to
86* [Commands](https://claude.com/docs/claude-tag/users/commands.md#turn-fast-mode-on-or-off): where `!fast` works and what Claude replies when it can't change the speed
87* [Customize Claude Tag](https://claude.com/docs/claude-tag/admins/customize.md#choose-the-model-for-a-scope): how admins set a default model per workspace or channel, and how the organization's model policy applies
8888
claude-tag/users/proactivity Changed · +14 / -14 lines
from line 50
5050@Claude every weekday at 9am Pacific, post a summary of open threads in this channel and anything that looks like it's waiting on someone.
5151```
5252
53"Waiting on someone" makes the rollup surface actions, not just a recap; [Catch up](/docs/claude-tag/users/use-cases/catch-up.md) has the one-off version.
53"Waiting on someone" makes the rollup surface actions, not just a recap; [Catch up](https://claude.com/docs/claude-tag/users/use-cases/catch-up.md) has the one-off version.
5454
5555### Weekly channel digest
5656
from line 60
6060@Claude every Friday at 3pm Eastern, post a digest of this week in this channel: what got decided, what's still open, and anything waiting on someone.
6161```
6262
63For an intake channel, the [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md) version of this rollup also sweeps posts that never tagged Claude.
63For an intake channel, the [Triage requests](https://claude.com/docs/claude-tag/users/use-cases/triage-requests.md) version of this rollup also sweeps posts that never tagged Claude.
6464
6565### Watch a pull request until it merges
6666
from line 74
7474
7575### Alert investigation when a monitor fires
7676
77Claude checks the alerting dashboard on a schedule and posts a first pass at diagnosis for anything new, so the investigation is underway before anyone asks. This recipe needs a monitoring connection such as Datadog or PagerDuty; [Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md) has the full setup.
77Claude checks the alerting dashboard on a schedule and posts a first pass at diagnosis for anything new, so the investigation is underway before anyone asks. This recipe needs a monitoring connection such as Datadog or PagerDuty; [Watch monitors and alerts](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md) has the full setup.
7878
7979```text wrap theme={null}
8080@Claude every two hours, check the alerting dashboard against its last state. For anything new, post when it started, what changed around then, and what to look at first.
from line 84
8484
8585### Automatic triage for new requests
8686
87Claude answers, deduplicates, and routes requests as they arrive. This recipe is a standing role rather than a schedule; "remember for this channel" saves it to [channel memory](/docs/claude-tag/users/memory.md), so it applies to everyone's threads.
87Claude answers, deduplicates, and routes requests as they arrive. This recipe is a standing role rather than a schedule; "remember for this channel" saves it to [channel memory](https://claude.com/docs/claude-tag/users/memory.md), so it applies to everyone's threads.
8888
8989```text wrap theme={null}
9090@Claude remember for this channel: when someone tags you on a request, check whether it duplicates something already reported, answer it directly if the answer exists, and otherwise route it to the right owner with a one-line summary.
9191```
9292
93Pair it with a weekly rollup so untagged posts are still swept; [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md) has both messages.
93Pair it with a weekly rollup so untagged posts are still swept; [Triage requests](https://claude.com/docs/claude-tag/users/use-cases/triage-requests.md) has both messages.
9494
9595## Where a routine posts its results
9696
97A routine you set up from inside a thread usually reports back in that thread each time it runs, for as long as the thread's [session](/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies) lasts. To keep the results in the thread, ask Claude to report back there when you set the routine up. If you send [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread, the routine moves to the thread's new session and keeps reporting there.
97A routine you set up from inside a thread usually reports back in that thread each time it runs, for as long as the thread's [session](https://claude.com/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies) lasts. To keep the results in the thread, ask Claude to report back there when you set the routine up. If you send [`@Claude !restart`](https://claude.com/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread, the routine moves to the thread's new session and keeps reporting there.
9898
99If the thread's session [gets stuck](/docs/claude-tag/users/troubleshooting.md#claude-reacted-or-started-thinking-then-never-replied), the routine doesn't move to the session that replaces it, and its later runs usually post at the channel's top level instead. To bring the results back into a thread, disable the routine and set it up again from that thread.
99If the thread's session [gets stuck](https://claude.com/docs/claude-tag/users/troubleshooting.md#claude-reacted-or-started-thinking-then-never-replied), the routine doesn't move to the session that replaces it, and its later runs usually post at the channel's top level instead. To bring the results back into a thread, disable the routine and set it up again from that thread.
100100
101101For a routine you set up at the channel's top level, Claude usually announces each run in a short top-level message and does the work in the thread under it. To follow up on any routine post, mention `@Claude` in a reply under it.
102102
from line 104
104104
105105Anyone in the channel can manage its standing work:
106106
107* **List.** Ask "what routines do you have set up in this channel?", or send [`@Claude !routines`](/docs/claude-tag/users/commands#list-the-routines-in-a-channel). When you ask in plain language from inside a thread, Claude lists that thread's own routines first and may leave out the rest of the channel's; ask for "every routine in this channel" to get them all, or use `!routines`, which lists the channel's routines wherever you send it. Add a channel mention or its ID, as in `@Claude !routines #other-channel`, to list another channel's routines; pick the channel from Slack's autocomplete so it lands as a real mention, since a typed name on its own isn't accepted.
107* **List.** Ask "what routines do you have set up in this channel?", or send [`@Claude !routines`](https://claude.com/docs/claude-tag/users/commands#list-the-routines-in-a-channel). When you ask in plain language from inside a thread, Claude lists that thread's own routines first and may leave out the rest of the channel's; ask for "every routine in this channel" to get them all, or use `!routines`, which lists the channel's routines wherever you send it. Add a channel mention or its ID, as in `@Claude !routines #other-channel`, to list another channel's routines; pick the channel from Slack's autocomplete so it lands as a real mention, since a typed name on its own isn't accepted.
108108* **Reschedule, pause, or stop a routine.** Name the routine and the change, as in "disable the Friday rollup" or "move the standup summary to 10am Pacific"
109109* **Change what a routine does.** Ask Claude to stop the routine, then set up a replacement from the channel where the results should post.
110110
from line 114
114114
115115* A job runs with the channel's connections, the same as an interactive request.
116116* Claude can post a job's output into another public channel in the same workspace only if the job's own channel is public and Claude has been added to the target channel. It labels the message with the channel it came from.
117* A routine you set up in a [group DM](/docs/claude-tag/users/group-dms.md) posts its output in that group DM only.
117* A routine you set up in a [group DM](https://claude.com/docs/claude-tag/users/group-dms.md) posts its output in that group DM only.
118118* Claude doesn't post a channel job's output into a different channel that's private or externally shared, or into a DM or group DM, and doesn't message people directly. Claude does send a completion or failure notice to whoever set up the routine, when that person's Slack account is connected to their Claude account.
119* Schedules run in UTC. Name the timezone when you set a schedule, as in "every weekday at 9am Pacific". With no timezone in your message, Claude uses the one on your Slack profile. To confirm the time Claude set, send [`@Claude !routines`](/docs/claude-tag/users/commands#list-the-routines-in-a-channel), which lists schedules in UTC.
119* Schedules run in UTC. Name the timezone when you set a schedule, as in "every weekday at 9am Pacific". With no timezone in your message, Claude uses the one on your Slack profile. To confirm the time Claude set, send [`@Claude !routines`](https://claude.com/docs/claude-tag/users/commands#list-the-routines-in-a-channel), which lists schedules in UTC.
120120* A routine runs at a fixed UTC time, so each daylight saving change shifts its local time by an hour, in the same direction the clocks move. A routine running at 9am Pacific moves to 10am after the clocks go forward, or to 8am after they go back. Ask Claude to reschedule the routine to the local time you want.
121* A scheduled job that touches a github.com repository uses the same GitHub connection your admin set up for interactive work. See [Configure GitHub access](/docs/claude-tag/admins/configure-github.md#scheduled-work-uses-the-same-connection).
121* A scheduled job that touches a github.com repository uses the same GitHub connection your admin set up for interactive work. See [Configure GitHub access](https://claude.com/docs/claude-tag/admins/configure-github.md#scheduled-work-uses-the-same-connection).
122122
123123## Related resources
124124
125* [Use case library](/docs/claude-tag/users/use-cases.md): every entry has a proactive form to copy
126* [Prompt library](/docs/claude-tag/users/prompt-library.md#manage-routines): prompts to create, audit, and stop routines
127* [Good habits](/docs/claude-tag/users/good-habits.md): write schedules that keep working
125* [Use case library](https://claude.com/docs/claude-tag/users/use-cases.md): every entry has a proactive form to copy
126* [Prompt library](https://claude.com/docs/claude-tag/users/prompt-library.md#manage-routines): prompts to create, audit, and stop routines
127* [Good habits](https://claude.com/docs/claude-tag/users/good-habits.md): write schedules that keep working
128128
claude-tag/users/prompt-library Changed · +17 / -17 lines
from line 50
5050@Claude read the thread linked below and take over the fix it describes. Post your plan here before changing anything.
5151```
5252
53**Why it works**: Claude works in the thread where you pasted the link, not in the thread you linked, so it uses this channel's connections and this channel can see the result. By asking Claude to post its plan first, you can redirect it before it starts. To read a linked thread in a public channel, Claude must be a member of that channel, and it can read a private channel's threads [only from inside that channel](/docs/claude-tag/users/good-habits.md#pick-the-right-surface). If Claude says it can't read the link, `/invite @Claude` in the linked public channel, or forward the messages instead.
53**Why it works**: Claude works in the thread where you pasted the link, not in the thread you linked, so it uses this channel's connections and this channel can see the result. By asking Claude to post its plan first, you can redirect it before it starts. To read a linked thread in a public channel, Claude must be a member of that channel, and it can read a private channel's threads [only from inside that channel](https://claude.com/docs/claude-tag/users/good-habits.md#pick-the-right-surface). If Claude says it can't read the link, `/invite @Claude` in the linked public channel, or forward the messages instead.
5454
5555## Shape how the channel works
5656
from line 72
7272@Claude remember for this channel: treat every top-level post as a task and pick it up without waiting for a mention.
7373```
7474
75**Why it works**: Claude already [picks up untagged posts when it judges a reply is warranted](/docs/claude-tag/users/when-claude-responds.md), and it weighs this channel-memory rule in that judgment, so teammates don't have to remember to tag Claude on posts with a concrete ask. If you don't specify a need, or if a teammate has already claimed the task, Claude may not respond to the message. In [a channel Claude has stopped reading](/docs/claude-tag/users/when-claude-responds.md#when-claude-stops-reading-a-channel), mention `@Claude` so that it replies and starts reading the channel again.
75**Why it works**: Claude already [picks up untagged posts when it judges a reply is warranted](https://claude.com/docs/claude-tag/users/when-claude-responds.md), and it weighs this channel-memory rule in that judgment, so teammates don't have to remember to tag Claude on posts with a concrete ask. If you don't specify a need, or if a teammate has already claimed the task, Claude may not respond to the message. In [a channel Claude has stopped reading](https://claude.com/docs/claude-tag/users/when-claude-responds.md#when-claude-stops-reading-a-channel), mention `@Claude` so that it replies and starts reading the channel again.
7676
7777## Check and correct memory
7878
from line 96
9696
9797## Manage routines
9898
99Create, audit, and stop the scheduled jobs Claude runs in this channel. For paste-ready schedules by scenario, like a daily standup summary or a weekly digest, see [Routine recipes](/docs/claude-tag/users/proactivity.md#routine-recipes).
99Create, audit, and stop the scheduled jobs Claude runs in this channel. For paste-ready schedules by scenario, like a daily standup summary or a weekly digest, see [Routine recipes](https://claude.com/docs/claude-tag/users/proactivity.md#routine-recipes).
100100
101101```text wrap theme={null}
102102@Claude every Friday at 3pm, post a summary of this week's requests: how many, top themes, and anything still unrouted.
from line 124
124124@Claude for each of these issues, start a new thread in this channel and fix it there. Open a draft PR in each, and post the links here when the threads are up.
125125```
126126
127**Why it works**: each new thread [runs its own session](/docs/claude-tag/users/good-habits.md#start-a-new-thread-for-a-new-task) in its own sandbox, so the tasks run at the same time and you can review each one on its own. To continue one existing discussion in a new thread instead, use [`!fork`](/docs/claude-tag/users/commands#fork-a-thread).
127**Why it works**: each new thread [runs its own session](https://claude.com/docs/claude-tag/users/good-habits.md#start-a-new-thread-for-a-new-task) in its own sandbox, so the tasks run at the same time and you can review each one on its own. To continue one existing discussion in a new thread instead, use [`!fork`](https://claude.com/docs/claude-tag/users/commands#fork-a-thread).
128128
129129## Steer work mid-thread
130130
from line 146
146146Post the draft to the thread, or commit and push what you have, then keep going.
147147```
148148
149**Why it works**: the thread is durable but [the isolated workspace behind it isn't](/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies). Anything Claude posts to the thread or pushes to a branch survives idle recycling; files that exist only in that workspace don't.
149**Why it works**: the thread is durable but [the isolated workspace behind it isn't](https://claude.com/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies). Anything Claude posts to the thread or pushes to a branch survives idle recycling; files that exist only in that workspace don't.
150150
151151## Task starters, by shape
152152
from line 154
154154
155155| To do this | Paste this |
156156| :- | :- |
157| [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md) | "remember for this channel: when someone tags you on a request, check whether it duplicates something already reported, answer it directly if the answer exists, and otherwise route it to the right owner with a one-line summary. Track recurring themes." |
158| [Catch up](/docs/claude-tag/users/use-cases/catch-up.md) | "what got decided in this thread, and what's still open?" |
159| [Create an artifact](/docs/claude-tag/users/use-cases/create-artifacts.md) | "turn this thread into a one-page decision doc" |
160| [Track a project](/docs/claude-tag/users/use-cases/track-projects.md) | "where are we on the migration? What's blocked and on whom?" |
161| [Answer a data question](/docs/claude-tag/users/use-cases/answer-data-questions.md) | "show signup growth by week, and explain the dips discussed above" |
162| [Find an answer in the docs](/docs/claude-tag/users/use-cases/find-answers.md) | "what's our policy on data retention, and which doc says so?" |
163| [Pull deal state](/docs/claude-tag/users/use-cases/pull-deal-state.md) | "what's the state of the Acme renewal?" |
164| [Watch monitors](/docs/claude-tag/users/use-cases/watch-monitors.md) | "every morning at 7, check the dashboards and post one line per service" |
165| [Fix a bug](/docs/claude-tag/users/use-cases/fix-bugs.md) | "in acme/data-pipeline, reproduce the bug in this thread, fix it, and open a draft PR" |
157| [Triage requests](https://claude.com/docs/claude-tag/users/use-cases/triage-requests.md) | "remember for this channel: when someone tags you on a request, check whether it duplicates something already reported, answer it directly if the answer exists, and otherwise route it to the right owner with a one-line summary. Track recurring themes." |
158| [Catch up](https://claude.com/docs/claude-tag/users/use-cases/catch-up.md) | "what got decided in this thread, and what's still open?" |
159| [Create an artifact](https://claude.com/docs/claude-tag/users/use-cases/create-artifacts.md) | "turn this thread into a one-page decision doc" |
160| [Track a project](https://claude.com/docs/claude-tag/users/use-cases/track-projects.md) | "where are we on the migration? What's blocked and on whom?" |
161| [Answer a data question](https://claude.com/docs/claude-tag/users/use-cases/answer-data-questions.md) | "show signup growth by week, and explain the dips discussed above" |
162| [Find an answer in the docs](https://claude.com/docs/claude-tag/users/use-cases/find-answers.md) | "what's our policy on data retention, and which doc says so?" |
163| [Pull deal state](https://claude.com/docs/claude-tag/users/use-cases/pull-deal-state.md) | "what's the state of the Acme renewal?" |
164| [Watch monitors](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md) | "every morning at 7, check the dashboards and post one line per service" |
165| [Fix a bug](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md) | "in acme/data-pipeline, reproduce the bug in this thread, fix it, and open a draft PR" |
166166
167167## Related resources
168168
169* [Use case library](/docs/claude-tag/users/use-cases.md): the full setup behind each starter
170* [Good habits](/docs/claude-tag/users/good-habits.md): the habits these prompts are built from
171* [Getting started](/docs/claude-tag/users/getting-started.md): the basics, if you haven't sent a first message yet
169* [Use case library](https://claude.com/docs/claude-tag/users/use-cases.md): the full setup behind each starter
170* [Good habits](https://claude.com/docs/claude-tag/users/good-habits.md): the habits these prompts are built from
171* [Getting started](https://claude.com/docs/claude-tag/users/getting-started.md): the basics, if you haven't sent a first message yet
172172
claude-tag/users/troubleshooting Changed · +60 / -60 lines
from line 6
66>
77> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
9When 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.md).
9When 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](https://claude.com/docs/claude-tag/admins/troubleshooting.md).
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.
1212
from line 26
2626
2727Work through these in order. Each step says what success looks like and where to go if it fails.
2828
291. **Is the Claude app installed in this workspace?** Start typing `@Claude` in any channel. **Works**: Slack autocompletes to a Claude app with an app badge; if more than one Claude app appears, check with your admin which one to use. **Fails**: nothing autocompletes, or only a person named Claude appears. The app isn't installed; this needs your admin (send them the [setup overview](/docs/claude-tag/admins/setup-overview)).
291. **Is the Claude app installed in this workspace?** Start typing `@Claude` in any channel. **Works**: Slack autocompletes to a Claude app with an app badge; if more than one Claude app appears, check with your admin which one to use. **Fails**: nothing autocompletes, or only a person named Claude appears. The app isn't installed; this needs your admin (send them the [setup overview](https://claude.com/docs/claude-tag/admins/setup-overview)).
30302. **Is Claude in this channel?** Type `/invite @Claude` in the channel's message box, not in a thread reply. Slack rejects `/invite` inside threads ("/invite is not supported in threads. Sorry!"). **Works**: Slack posts "Claude was added to #channel" (or "is already in this channel"). Mention it again. **Fails**: Slack says you can't add apps to this channel (a Slack Connect or guest-restricted channel); try an internal channel instead. If Slack says "You don't have permission to invite people to this channel", the channel or workspace limits who can add people. In Slack, open **Channel details** → **Agents & apps** (called **Integrations** in some Slack versions), select **Add**, and pick **Claude**. Or ask someone who can add people to the channel to add Claude.
31313. **Is Claude Tag turned on for this channel?** Mention it again now that it's invited. **Works**: it reacts and replies. **Fails**: Claude replies in one of these ways, and each needs your admin:
32 * **A notice that starts "Claude isn't on in this channel yet"**: your admin hasn't finished setting up Claude Tag. Send them [Launch Claude Tag](/docs/claude-tag/admins/setup-overview#launch-claude-tag).
33 * **A notice that says "Claude is disabled in this channel"**: Claude Tag is turned off for the channel, its workspace, or the organization. Send them [Claude is disabled in this channel](/docs/claude-tag/admins/troubleshooting.md#claude-is-disabled-in-this-channel).
34 * **A notice that the legacy Claude in Slack bot is retired**: the channel is still set to **Legacy**. Send them [The legacy Claude in Slack bot is retired](/docs/claude-tag/admins/troubleshooting.md#the-legacy-claude-in-slack-bot-is-retired-effective-october-5-2026).
32 * **A notice that starts "Claude isn't on in this channel yet"**: your admin hasn't finished setting up Claude Tag. Send them [Launch Claude Tag](https://claude.com/docs/claude-tag/admins/setup-overview#launch-claude-tag).
33 * **A notice that says "Claude is disabled in this channel"**: Claude Tag is turned off for the channel, its workspace, or the organization. Send them [Claude is disabled in this channel](https://claude.com/docs/claude-tag/admins/troubleshooting.md#claude-is-disabled-in-this-channel).
34 * **A notice that the legacy Claude in Slack bot is retired**: the channel is still set to **Legacy**. Send them [The legacy Claude in Slack bot is retired](https://claude.com/docs/claude-tag/admins/troubleshooting.md#the-legacy-claude-in-slack-bot-is-retired-effective-october-5-2026).
3535
36If `@Claude` still gets no reaction and no reply after all three, send the [admin entries for a silent workspace](/docs/claude-tag/admins/troubleshooting.md#nothing-responds) to an admin. For silence in one channel, send them to your Claude admin. For silence across a whole workspace or a whole Enterprise Grid, send them to whoever administers Slack for you, because the fix usually needs a Slack admin.
36If `@Claude` still gets no reaction and no reply after all three, send the [admin entries for a silent workspace](https://claude.com/docs/claude-tag/admins/troubleshooting.md#nothing-responds) to an admin. For silence in one channel, send them to your Claude admin. For silence across a whole workspace or a whole Enterprise Grid, send them to whoever administers Slack for you, because the fix usually needs a Slack admin.
3737
3838### Claude replies to me but not to a teammate
3939
from line 43
4343
4444**What it means**
4545
46Mentioning Claude in a channel doesn't require the sender to have a Claude account or seat, so by default anyone in the workspace can use it. Your organization can restrict that with the [member access setting](/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude), in which case members outside the restriction are declined.
46Mentioning Claude in a channel doesn't require the sender to have a Claude account or seat, so by default anyone in the workspace can use it. Your organization can restrict that with the [member access setting](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude), in which case members outside the restriction are declined.
4747
4848**How to resolve**
4949
from line 51
5151
5252* No reaction and no reply at all: unusual when it works for you in the same channel; send your admin the exact channel and person.
5353* A message about guests: see [the guest entry below](#claude-doesn%E2%80%99t-respond-in-channels-that-include-guests).
54* A message about permissions or access: your organization restricts who can use Claude; send your admin [the member access setting](/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude).
54* A message about permissions or access: your organization restricts who can use Claude; send your admin [the member access setting](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude).
5555
5656### Claude reacted or started thinking, then never replied
5757
from line 65
6565
6666**How to resolve**
6767
681. 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.
692. 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.
681. Send [`@Claude !status`](https://claude.com/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.
692. If the silence has stretched well past what the task should need, send [`@Claude !restart`](https://claude.com/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
7171> [!WARNING]
7272>
from line 92
9292
9393**How to resolve**
9494
95* For the capacity message, wait a few minutes. To add context while waiting, @-mention Claude in the same thread rather than starting a new one. A new thread only queues a second session behind the first. If Claude still hasn't started after several more minutes, send your admin [Still waiting for available capacity](/docs/claude-tag/admins/troubleshooting.md#still-waiting-for-available-capacity).
95* For the capacity message, wait a few minutes. To add context while waiting, @-mention Claude in the same thread rather than starting a new one. A new thread only queues a second session behind the first. If Claude still hasn't started after several more minutes, send your admin [Still waiting for available capacity](https://claude.com/docs/claude-tag/admins/troubleshooting.md#still-waiting-for-available-capacity).
9696* For the failed-start message, mention Claude in the same thread to retry. If the session fails to start again, ask an admin.
9797
9898### Claude didn't react to a message I edited
from line 119
119119
120120Find what you saw in this list:
121121
122* **No answer and no notice.** By default, Claude is off in Slack Connect channels and posts no notice there. An Owner or a Claude Tag admin can [turn Claude on for Slack Connect channels](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels). If your admin has turned Claude on and it still doesn't answer, your admin can check the cases listed there.
122* **No answer and no notice.** By default, Claude is off in Slack Connect channels and posts no notice there. An Owner or a Claude Tag admin can [turn Claude on for Slack Connect channels](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels). If your admin has turned Claude on and it still doesn't answer, your admin can check the cases listed there.
123123* **A reply only you can see.** If Claude's reply starts "This is a shared Slack Connect channel, and here I only act on requests from people in the host organization with a connected Claude account", the company that set up Claude in this channel has limited it to its own members.
124124* **A notice about the thread's earlier session.** The notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here" means Claude was working in this thread before the channel was shared. Mention `@Claude` in a new thread.
125125
from line 127
127127
128128Where guest access is restricted, you may first see "This channel is shared across multiple workspaces, and Claude can't verify whether it includes guests, so Claude can't respond here." If you ask Claude from another conversation to act in one of these channels, such as posting a message there, you see a reply that ends "Claude isn't available in channels shared across your Enterprise Grid".
129129
130Each of these Enterprise Grid messages means the channel spans more than one workspace. The [admin entries on these messages](/docs/claude-tag/admins/troubleshooting.md#this-channel-is-shared-across-multiple-workspaces) explain what causes each one and what an admin can change.
130Each of these Enterprise Grid messages means the channel spans more than one workspace. The [admin entries on these messages](https://claude.com/docs/claude-tag/admins/troubleshooting.md#this-channel-is-shared-across-multiple-workspaces) explain what causes each one and what an admin can change.
131131
132132**How to resolve**
133133
134Move the conversation to an internal channel that belongs to a single workspace, or to a DM, and mention Claude there. For a Slack Connect channel, you can also ask your admin to [turn Claude on there](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels).
134Move the conversation to an internal channel that belongs to a single workspace, or to a DM, and mention Claude there. For a Slack Connect channel, you can also ask your admin to [turn Claude on there](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels).
135135
136136### Couldn't check this channel just now
137137
from line 147
147147
148148**How to resolve**
149149
150Mention Claude again; the check usually passes on retry. If the same channel hits this repeatedly, send your admin [the admin entry on this message](/docs/claude-tag/admins/troubleshooting.md#couldn%E2%80%99t-check-this-channel-just-now).
150Mention Claude again; the check usually passes on retry. If the same channel hits this repeatedly, send your admin [the admin entry on this message](https://claude.com/docs/claude-tag/admins/troubleshooting.md#couldn%E2%80%99t-check-this-channel-just-now).
151151
152152### Claude doesn't respond in channels that include guests
153153
from line 167
167167
168168* Remove the guests from the channel. In Slack, open **Channel details** → **Members** and filter by "guests"; guests show a **guest** badge on their Slack profile.
169169* Move the conversation to a channel with no guests.
170* Ask a claude.ai organization owner to change the guest setting for this channel, and send them [the guest access setting](/docs/claude-tag/admins/restrict-access.md#restrict-guest-channels). They can let Claude reply with only the channel's own setup, or with full access. If you don't know who your organization's owners are, ask whoever set Claude up in your workspace.
170* Ask a claude.ai organization owner to change the guest setting for this channel, and send them [the guest access setting](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-guest-channels). They can let Claude reply with only the channel's own setup, or with full access. If you don't know who your organization's owners are, ask whoever set Claude up in your workspace.
171171
172172The guest access setting restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even when it's allowed to respond there. Removing the guests or moving the conversation to a channel with no guests restores search as well.
173173
from line 189
189189
190190Before you share or act on a result, check the source links it posted, and ask it to show its work ("which channels did you search?" or "show me the query you ran"). If the answer is wrong, say so in the same thread with the correct answer; correcting it there is also how you steer the next attempt.
191191
192For numbers and facts that matter, the [definition-of-done habit](/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done) helps. Make "include the source for every figure" or "show me the query" part of the ask.
192For numbers and facts that matter, the [definition-of-done habit](https://claude.com/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done) helps. Make "include the source for every figure" or "show me the query" part of the ask.
193193
194194### Claude replies to every message in a thread
195195
from line 213
213213
214214**What it means**
215215
216The channel's [**Respond automatically**](/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting is on. The setting is on by default.
216The channel's [**Respond automatically**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting is on. The setting is on by default.
217217
218In a channel where someone has [told Claude which kinds of untagged messages to answer](/docs/claude-tag/users/when-claude-responds.md#what-claude-does-with-a-channel-message), it answers those kinds as well.
218In a channel where someone has [told Claude which kinds of untagged messages to answer](https://claude.com/docs/claude-tag/users/when-claude-responds.md#what-claude-does-with-a-channel-message), it answers those kinds as well.
219219
220220**How to resolve**
221221
from line 229
2292292. Turn off the **Respond automatically** toggle.
2302303. Click **Save**.
231231
232If the Configure page says an admin has locked the channel's settings, ask an admin to [turn automatic replies off](/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for the channel.
232If the Configure page says an admin has locked the channel's settings, ask an admin to [turn automatic replies off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for the channel.
233233
234234The **Respond automatically** setting doesn't quiet a thread Claude has already posted in. To quiet one of those threads, reply in it with an instruction such as "only respond when I @-mention you".
235235
from line 255
255255
256256**What it means**
257257
258Claude can delete only messages that the conversation's current [session](/docs/claude-tag/concepts/glossary.md#session) posted, so it can't delete your messages, anyone else's, or a message it posted before that session started.
258Claude can delete only messages that the conversation's current [session](https://claude.com/docs/claude-tag/concepts/glossary.md#session) posted, so it can't delete your messages, anyone else's, or a message it posted before that session started.
259259
260260**How to resolve**
261261
from line 265
265265
266266* The deletion is permanent.
267267* When the deleted message started a thread that has replies, Slack keeps the replies.
268* Deleting the message from Slack doesn't remove it from the session's transcript. See [What Anthropic stores](/docs/claude-tag/concepts/data-lifecycle.md#what-anthropic-stores).
268* Deleting the message from Slack doesn't remove it from the session's transcript. See [What Anthropic stores](https://claude.com/docs/claude-tag/concepts/data-lifecycle.md#what-anthropic-stores).
269269
270270### This conversation is too long for me to process
271271
from line 343
343343
344344**How to resolve**
345345
346An admin enables or purchases usage credits in claude.ai for your organization. Once that's done, mention Claude in the same thread to retry (adding credits doesn't restart the work on its own). The retry continues with the thread's conversation and context. [What survives between replies](/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies) covers what else carries over.
346An admin enables or purchases usage credits in claude.ai for your organization. Once that's done, mention Claude in the same thread to retry (adding credits doesn't restart the work on its own). The retry continues with the thread's conversation and context. [What survives between replies](https://claude.com/docs/claude-tag/concepts/how-it-works.md#what-survives-between-replies) covers what else carries over.
347347
348348### Claude couldn't clone a repository for this session
349349
from line 359
359359
360360**How to resolve**
361361
362Wait a few minutes, then mention Claude in the same thread to retry. If the same repository fails every time, send your admin [the GitHub access entry](/docs/claude-tag/admins/troubleshooting.md#github-doesn%E2%80%99t-work-in-this-channel).
362Wait a few minutes, then mention Claude in the same thread to retry. If the same repository fails every time, send your admin [the GitHub access entry](https://claude.com/docs/claude-tag/admins/troubleshooting.md#github-doesn%E2%80%99t-work-in-this-channel).
363363
364364### I got disconnected partway through
365365
from line 417
417417
418418**How to resolve**
419419
420Ask Claude to recreate the file, and for long-running work, ask it to commit and push early, or to post drafts into the thread as it goes, so nothing lives only in that workspace. The [definition-of-done habit](/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done) helps here. Make "push the branch" or "post the file" part of the task.
420Ask Claude to recreate the file, and for long-running work, ask it to commit and push early, or to post drafts into the thread as it goes, so nothing lives only in that workspace. The [definition-of-done habit](https://claude.com/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done) helps here. Make "push the branch" or "post the file" part of the task.
421421
422422### My old thread stopped working, but new threads are fine
423423
from line 431
431431
432432**How to resolve**
433433
434Send [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread. It archives the stuck session and starts a fresh one with your organization's current configuration, and the fresh session still reads the thread.
434Send [`@Claude !restart`](https://claude.com/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread. It archives the stuck session and starts a fresh one with your organization's current configuration, and the fresh session still reads the thread.
435435
436436Starting a new thread and restating your request also works; paste a link to the old thread so Claude picks up the context.
437437
from line 463
463463
464464To make an instruction stick, say so explicitly, as in `remember for this channel: always post reports as a table`. Keep saved instructions short; the per-channel memory budget is limited, and long entries crowd out everything else. For longer playbooks, store them in a repository Claude can read.
465465
466Verify what stuck by asking what it remembers about the channel. See [What Claude Tag remembers](/docs/claude-tag/users/memory.md).
466Verify what stuck by asking what it remembers about the channel. See [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md).
467467
468468### A session link Claude posted shows a not-found page
469469
from line 523
523523
524524**What it means**
525525
526The channel likely hasn't been given a connection for that service; see [what each connection adds](/docs/claude-tag/admins/add-connections.md).
526The channel likely hasn't been given a connection for that service; see [what each connection adds](https://claude.com/docs/claude-tag/admins/add-connections.md).
527527
528528**How to resolve**
529529
530Ask your admin to add one for this channel and send them [the connection scope entry](/docs/claude-tag/admins/troubleshooting.md#a-connection-works-in-one-channel-but-not-another). Once they have, ask Claude to use the service by name, or start a new thread, which picks up the connection on its own. If the fix worked, asking `@Claude what can you access from this channel?` in a new thread lists the service.
530Ask your admin to add one for this channel and send them [the connection scope entry](https://claude.com/docs/claude-tag/admins/troubleshooting.md#a-connection-works-in-one-channel-but-not-another). Once they have, ask Claude to use the service by name, or start a new thread, which picks up the connection on its own. If the fix worked, asking `@Claude what can you access from this channel?` in a new thread lists the service.
531531
532532### A connector works on claude.ai but not in Slack
533533
from line 537
537537
538538**What it means**
539539
540Where you message Claude determines which connectors apply. A channel session uses the connections an admin attached to it. Claude can also [use your personal connectors there](/docs/claude-tag/concepts/personal-connectors.md) for your own tasks, after you allow it. A one-to-one DM runs on your own claude.ai account and uses that account's connectors.
540Where you message Claude determines which connectors apply. A channel session uses the connections an admin attached to it. Claude can also [use your personal connectors there](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) for your own tasks, after you allow it. A one-to-one DM runs on your own claude.ai account and uses that account's connectors.
541541
542You set up and authenticate connectors on claude.ai under **Customize > Connectors**; Slack has no connector settings of its own. The [settings map](/docs/claude-tag/concepts/settings-map.md) covers every settings surface.
542You set up and authenticate connectors on claude.ai under **Customize > Connectors**; Slack has no connector settings of its own. The [settings map](https://claude.com/docs/claude-tag/concepts/settings-map.md) covers every settings surface.
543543
544544**How to resolve**
545545
546For a channel, ask your admin to [add a connection](/docs/claude-tag/admins/add-connections.md) for the service. Claude can also use your [personal connectors](/docs/claude-tag/concepts/personal-connectors.md) for your own tasks in the channel, after you allow it.
546For a channel, ask your admin to [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) for the service. Claude can also use your [personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) for your own tasks in the channel, after you allow it.
547547
548548For a DM, work through these in order:
549549
5505501. Check that your Claude account is connected. DM `@Claude` and it prompts you to connect if it isn't.
5515512. Check that the connector shows as connected under **Customize > Connectors** on claude.ai.
5523. For a custom connector on a Team or Enterprise plan, an Owner adds it to the organization before you can connect it; see [add a connector by URL](/docs/connectors/custom/add-unlisted.md#add-a-connector-by-url).
5523. For a custom connector on a Team or Enterprise plan, an Owner adds it to the organization before you can connect it; see [add a connector by URL](https://claude.com/docs/connectors/custom/add-unlisted.md#add-a-connector-by-url).
5535534. After connecting or reconnecting the connector on claude.ai, send Claude a new top-level direct message. A session loads its connectors when it starts, so your existing DM threads keep the set they started with and don't pick up the change.
554554
555555### Claude says it needs Claude Opus 5 to use my personal connectors
from line 556
556556
557557**What you see**
558558
559You ask Claude in a channel to do something that needs one of your [personal connectors](/docs/claude-tag/concepts/personal-connectors.md). Claude replies that it can't, because your Claude organization has turned off Claude Opus 5, which it needs to use your personal connectors in Slack.
559You ask Claude in a channel to do something that needs one of your [personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md). Claude replies that it can't, because your Claude organization has turned off Claude Opus 5, which it needs to use your personal connectors in Slack.
560560
561561**What it means**
562562
from line 564
564564
565565**How to resolve**
566566
567Ask your admin to turn Claude Opus 5 back on for your organization, and send them [the admin controls for personal connectors](/docs/claude-tag/concepts/personal-connectors.md#admin-controls-for-personal-connectors). Once it's on, ask Claude again in the thread. Your thread keeps running on the model it was already using.
567Ask your admin to turn Claude Opus 5 back on for your organization, and send them [the admin controls for personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md#admin-controls-for-personal-connectors). Once it's on, ask Claude again in the thread. Your thread keeps running on the model it was already using.
568568
569569### Claude says it has no internet access or can't open a link
570570
from line 578
578578
579579**How to resolve**
580580
581Send your admin the link you tried to open along with [the blocked host entry](/docs/claude-tag/admins/troubleshooting.md#claude-says-a-host-isn%E2%80%99t-allowed-or-it-can%E2%80%99t-reach-the-internet). While you wait, ask Claude to search for the page instead; a search often brings back enough of the content to answer. Once your admin has allowed the website, retry; if it's still blocked, start a fresh thread.
581Send your admin the link you tried to open along with [the blocked host entry](https://claude.com/docs/claude-tag/admins/troubleshooting.md#claude-says-a-host-isn%E2%80%99t-allowed-or-it-can%E2%80%99t-reach-the-internet). While you wait, ask Claude to search for the page instead; a search often brings back enough of the content to answer. Once your admin has allowed the website, retry; if it's still blocked, start a fresh thread.
582582
583583### Claude can't connect over SSH
584584
from line 588
588588
589589**What it means**
590590
591Every request Claude makes from a channel passes through [Agent Proxy](/docs/claude-tag/concepts/agent-identity.md#agent-proxy), which carries HTTP and HTTPS only. A protocol that isn't HTTP, such as SSH or a database's native wire protocol, can't cross the proxy to any host, so this isn't a connection your admin can add.
591Every request Claude makes from a channel passes through [Agent Proxy](https://claude.com/docs/claude-tag/concepts/agent-identity.md#agent-proxy), which carries HTTP and HTTPS only. A protocol that isn't HTTP, such as SSH or a database's native wire protocol, can't cross the proxy to any host, so this isn't a connection your admin can add.
592592
593593**How to resolve**
594594
595If the service exposes an HTTP API, ask your admin to [add a connection](/docs/claude-tag/admins/add-connections.md) for that instead.
595If the service exposes an HTTP API, ask your admin to [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) for that instead.
596596
597597### You've reached a Claude Tag spend limit
598598
from line 620
620620
621621**What it means**
622622
623Usage hit a cap. For the **Claude Tag spend limit** message, the cap is a spend limit an admin set, either for the whole organization or [for this channel](/docs/claude-tag/admins/restrict-access.md#set-spend-limits), and the message reads the same for both.
623Usage hit a cap. For the **Claude Tag spend limit** message, the cap is a spend limit an admin set, either for the whole organization or [for this channel](https://claude.com/docs/claude-tag/admins/restrict-access.md#set-spend-limits), and the message reads the same for both.
624624
625625A rate limit looks similar but is a different problem, and raising the spend limit doesn't clear it. If your message instead says "That message didn't get through to Claude." or begins "Rate-limited delivering that message", requests arrived faster than Claude accepts them at that moment. Wait a few seconds, then send your message again.
626626
from line 669
6696691. Mention Claude again; the retry usually clears it.
6706702. If it keeps happening, the environment your account is set to use may no longer be available; check it at [`claude.ai/code`](https://claude.ai/code).
671671
672If a channel (not a DM) shows session-start failures that mention an environment, send your admin [the environment scope entry](/docs/claude-tag/admins/troubleshooting.md#channel-sessions-use-the-wrong-environment-or-can%E2%80%99t-find-one).
672If a channel (not a DM) shows session-start failures that mention an environment, send your admin [the environment scope entry](https://claude.com/docs/claude-tag/admins/troubleshooting.md#channel-sessions-use-the-wrong-environment-or-can%E2%80%99t-find-one).
673673
674674### Your Claude account is connected, but it doesn't have access in this organization
675675
from line 687
687687
688688**How to resolve**
689689
690Channels keep working while you wait, so mention `@Claude` there if you need an answer now. Then ask your admin (whoever manages your organization's Claude account at claude.ai) about your seat assignment; the [admin entry on this message](/docs/claude-tag/admins/troubleshooting.md#your-claude-account-is-connected-but-it-doesn%E2%80%99t-have-access-in-this-organization) covers the fix.
690Channels keep working while you wait, so mention `@Claude` there if you need an answer now. Then ask your admin (whoever manages your organization's Claude account at claude.ai) about your seat assignment; the [admin entry on this message](https://claude.com/docs/claude-tag/admins/troubleshooting.md#your-claude-account-is-connected-but-it-doesn%E2%80%99t-have-access-in-this-organization) covers the fix.
691691
692692### Your Claude admin has disabled sending direct messages to Claude
693693
from line 703
703703
704704**How to resolve**
705705
706Use a channel instead, or ask an Owner of your Claude organization to [turn DMs back on](/docs/claude-tag/admins/restrict-access.md#allow-or-disable-direct-messages).
706Use a channel instead, or ask an Owner of your Claude organization to [turn DMs back on](https://claude.com/docs/claude-tag/admins/restrict-access.md#allow-or-disable-direct-messages).
707707
708708### Group DMs aren't supported yet
709709
from line 722
722722
723723**How to resolve**
724724
725Ask Claude in a channel or a one-to-one DM instead. If you're an admin, [Group DMs](/docs/claude-tag/admins/restrict-access.md#group-dms) covers how who is in a group DM, and how Slack shares it, can change whether Claude answers.
725Ask Claude in a channel or a one-to-one DM instead. If you're an admin, [Group DMs](https://claude.com/docs/claude-tag/admins/restrict-access.md#group-dms) covers how who is in a group DM, and how Slack shares it, can change whether Claude answers.
726726
727727### Agents can only be added at the start of direct messages
728728
from line 745
745745
746746## Related resources
747747
748* [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without an @-mention, and the controls that turn those replies off
749* [How Claude Tag works](/docs/claude-tag/concepts/how-it-works.md): why behavior differs by channel and thread
748* [Control when Claude Tag responds](https://claude.com/docs/claude-tag/users/when-claude-responds.md): what makes Claude reply without an @-mention, and the controls that turn those replies off
749* [How Claude Tag works](https://claude.com/docs/claude-tag/concepts/how-it-works.md): why behavior differs by channel and thread
750750* [Give feedback](https://support.claude.com): report a bug from the thread where it happened
751751
claude-tag/users/use-cases Changed · +25 / -25 lines
from line 6
66>
77> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
9Each 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.md) instead of asking each time.
9Each 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](https://claude.com/docs/claude-tag/users/proactivity.md) instead of asking each time.
1010
1111> [!NOTE]
1212>
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).
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](https://claude.com/docs/claude-tag/admins/setup-overview).
1414
1515## All use cases
1616
1717| Use case | Who it's for | What Claude does | Connections needed |
1818| :- | :- | :- | :- |
19| [Catch up](/docs/claude-tag/users/use-cases/catch-up.md) | Anyone | Summarizes a thread, a channel, or what's waiting on you | Nothing |
20| [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel.md) | Anyone | Answers scratch questions, digests channels you don't follow, and chases what you said you'd do | Nothing (issue tracker or GitHub optional) |
21| [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md) | Support, ops, IT, any intake channel | Answers what it can, flags duplicates, routes the rest, rolls up themes | Nothing (issue tracker optional for filing) |
22| [Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts.md) | Anyone | Produces a decision doc, status memo, ticket, send-ready reply, or hosted web page from a discussion | Nothing (Drive or issue tracker optional) |
23| [Track projects and chase approvals](/docs/claude-tag/users/use-cases/track-projects.md) | PMs, leads, anyone running a project channel | Posts standing status digests; follows up on stalled sign-offs | Nothing (issue tracker optional) |
24| [Find answers in your docs](/docs/claude-tag/users/use-cases/find-answers.md) | Anyone | Looks up policies, runbooks, prior decisions; replies with the source | Google Drive, Notion, or Confluence |
25| [Review documents against a checklist](/docs/claude-tag/users/use-cases/review-documents.md) | Ops, compliance, anyone reviewing against criteria | Checks documents in a connected tool against a checklist or policy; posts findings per item | Google Drive, Notion, or Confluence |
26| [Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions.md) | Analysts, data-adjacent teams | Runs warehouse queries, returns charts; or charts from Slack history alone | BigQuery, Snowflake, or Redshift (charts from Slack need none) |
27| [Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md) | Engineering | Reproduces the bug, opens a draft PR, follows CI to green | GitHub (Datadog, Sentry optional) |
28| [Work with GitHub](/docs/claude-tag/users/use-cases/work-with-github.md) | Engineering, anyone with repository questions | Answers repository questions in-thread, watches pull requests for you, turns postponed chores into draft PRs | GitHub |
29| [Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md) | On-call, SRE | Checks dashboards on a schedule; investigates alerts before anyone asks | Datadog, Sentry, or PagerDuty |
30| [Pull deal and account state](/docs/claude-tag/users/use-cases/pull-deal-state.md) | Sales, customer success | Answers account questions in-thread; pre-call briefs; weekly pipeline digest | Salesforce, HubSpot, or Gong |
31| [Claude Tag for marketing teams](/docs/claude-tag/users/use-cases/marketing-team.md) | Marketing | Answers policy questions from team docs, drafts from campaign threads, checks lead state, posts a weekly metrics digest | HubSpot or Salesforce, plus Google Drive, Notion, or Confluence; BigQuery or Snowflake for the metrics digest (varies by recipe) |
19| [Catch up](https://claude.com/docs/claude-tag/users/use-cases/catch-up.md) | Anyone | Summarizes a thread, a channel, or what's waiting on you | Nothing |
20| [Work from your own channel](https://claude.com/docs/claude-tag/users/use-cases/your-own-channel.md) | Anyone | Answers scratch questions, digests channels you don't follow, and chases what you said you'd do | Nothing (issue tracker or GitHub optional) |
21| [Triage requests](https://claude.com/docs/claude-tag/users/use-cases/triage-requests.md) | Support, ops, IT, any intake channel | Answers what it can, flags duplicates, routes the rest, rolls up themes | Nothing (issue tracker optional for filing) |
22| [Turn threads into docs and tickets](https://claude.com/docs/claude-tag/users/use-cases/create-artifacts.md) | Anyone | Produces a decision doc, status memo, ticket, send-ready reply, or hosted web page from a discussion | Nothing (Drive or issue tracker optional) |
23| [Track projects and chase approvals](https://claude.com/docs/claude-tag/users/use-cases/track-projects.md) | PMs, leads, anyone running a project channel | Posts standing status digests; follows up on stalled sign-offs | Nothing (issue tracker optional) |
24| [Find answers in your docs](https://claude.com/docs/claude-tag/users/use-cases/find-answers.md) | Anyone | Looks up policies, runbooks, prior decisions; replies with the source | Google Drive, Notion, or Confluence |
25| [Review documents against a checklist](https://claude.com/docs/claude-tag/users/use-cases/review-documents.md) | Ops, compliance, anyone reviewing against criteria | Checks documents in a connected tool against a checklist or policy; posts findings per item | Google Drive, Notion, or Confluence |
26| [Answer data questions](https://claude.com/docs/claude-tag/users/use-cases/answer-data-questions.md) | Analysts, data-adjacent teams | Runs warehouse queries, returns charts; or charts from Slack history alone | BigQuery, Snowflake, or Redshift (charts from Slack need none) |
27| [Fix bugs](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md) | Engineering | Reproduces the bug, opens a draft PR, follows CI to green | GitHub (Datadog, Sentry optional) |
28| [Work with GitHub](https://claude.com/docs/claude-tag/users/use-cases/work-with-github.md) | Engineering, anyone with repository questions | Answers repository questions in-thread, watches pull requests for you, turns postponed chores into draft PRs | GitHub |
29| [Watch monitors and alerts](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md) | On-call, SRE | Checks dashboards on a schedule; investigates alerts before anyone asks | Datadog, Sentry, or PagerDuty |
30| [Pull deal and account state](https://claude.com/docs/claude-tag/users/use-cases/pull-deal-state.md) | Sales, customer success | Answers account questions in-thread; pre-call briefs; weekly pipeline digest | Salesforce, HubSpot, or Gong |
31| [Claude Tag for marketing teams](https://claude.com/docs/claude-tag/users/use-cases/marketing-team.md) | Marketing | Answers policy questions from team docs, drafts from campaign threads, checks lead state, posts a weekly metrics digest | HubSpot or Salesforce, plus Google Drive, Notion, or Confluence; BigQuery or Snowflake for the metrics digest (varies by recipe) |
3232
3333## Use cases by connection
3434
from line 36
3636
3737| Connection | Examples | What it adds |
3838| :- | :- | :- |
39| Knowledge and docs | Google Drive, Notion, Confluence | [Find answers in your docs](/docs/claude-tag/users/use-cases/find-answers.md) |
40| Issue tracking | Linear, Jira, Asana | [Turn threads into tickets](/docs/claude-tag/users/use-cases/create-artifacts.md), [track projects](/docs/claude-tag/users/use-cases/track-projects.md) |
41| Data warehouse | BigQuery, Snowflake | [Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions.md) with charts |
42| Go-to-market | Salesforce, HubSpot, Gong | [Pull deal and account state](/docs/claude-tag/users/use-cases/pull-deal-state.md) |
43| Monitoring | Datadog, Sentry, PagerDuty | [Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md) |
44| Code | GitHub | [Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md), open pull requests, follow CI |
39| Knowledge and docs | Google Drive, Notion, Confluence | [Find answers in your docs](https://claude.com/docs/claude-tag/users/use-cases/find-answers.md) |
40| Issue tracking | Linear, Jira, Asana | [Turn threads into tickets](https://claude.com/docs/claude-tag/users/use-cases/create-artifacts.md), [track projects](https://claude.com/docs/claude-tag/users/use-cases/track-projects.md) |
41| Data warehouse | BigQuery, Snowflake | [Answer data questions](https://claude.com/docs/claude-tag/users/use-cases/answer-data-questions.md) with charts |
42| Go-to-market | Salesforce, HubSpot, Gong | [Pull deal and account state](https://claude.com/docs/claude-tag/users/use-cases/pull-deal-state.md) |
43| Monitoring | Datadog, Sentry, PagerDuty | [Watch monitors and alerts](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md) |
44| Code | GitHub | [Fix bugs](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md), open pull requests, follow CI |
4545
46If a connection your work needs is missing, an admin can [add it](/docs/claude-tag/admins/add-connections.md).
46If a connection your work needs is missing, an admin can [add it](https://claude.com/docs/claude-tag/admins/add-connections.md).
4747
4848## Related resources
4949
50* [Prompt library](/docs/claude-tag/users/prompt-library.md): the prompts from every entry, plus the operational ones, on one page
51* [Good habits](/docs/claude-tag/users/good-habits.md): make any of these reliable
52* [Set up routines](/docs/claude-tag/users/proactivity.md): turn any entry into a scheduled job
50* [Prompt library](https://claude.com/docs/claude-tag/users/prompt-library.md): the prompts from every entry, plus the operational ones, on one page
51* [Good habits](https://claude.com/docs/claude-tag/users/good-habits.md): make any of these reliable
52* [Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md): turn any entry into a scheduled job
5353
claude-tag/users/use-cases/answer-data-questions Changed · +4 / -4 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 38
3838@Claude every morning at 8, post yesterday's key metrics as a chart with a two-line summary of anything unusual.
3939```
4040
41Naming the format, here a chart plus two lines, keeps a recurring post scannable instead of letting it grow each day. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
41Naming the format, here a chart plus two lines, keeps a recurring post scannable instead of letting it grow each day. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
4242
4343### Chart from Slack alone
4444
from line 52
5252
5353## Related resources
5454
55> **[Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md)**
55> **[Watch monitors and alerts](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md)**
5656>
5757> When the question is about systems, not metrics
5858
59> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
59> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
6060>
6161> Recurring reports
6262
claude-tag/users/use-cases/catch-up Changed · +4 / -4 lines
from line 12
1212
1313## Check the channel's connections
1414
15This use case needs no connections; it works on Slack history alone. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
15This use case needs no connections; it works on Slack history alone. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1616
1717## Prompts to paste
1818
from line 42
4242@Claude every weekday at 9am, post a summary of open threads in this channel and anything that looks like it's waiting on someone.
4343```
4444
45"Waiting on someone" makes the rollup surface actions, not just a recap of yesterday. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
45"Waiting on someone" makes the rollup surface actions, not just a recap of yesterday. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
4646
4747## Related resources
4848
49> **[Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts.md)**
49> **[Turn threads into docs and tickets](https://claude.com/docs/claude-tag/users/use-cases/create-artifacts.md)**
5050>
5151> When the catch-up should become an artifact
5252
53> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
53> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
5454>
5555> Scheduling and triggers
5656
claude-tag/users/use-cases/create-artifacts Changed · +4 / -4 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 49
4949@Claude build a status page from the open items in this channel and post the link here.
5050```
5151
52Anyone with access to this channel can open the page; [artifact visibility](/docs/claude-tag/concepts/security-and-data.md#artifact-visibility) covers the access model.
52Anyone with access to this channel can open the page; [artifact visibility](https://claude.com/docs/claude-tag/concepts/security-and-data.md#artifact-visibility) covers the access model.
5353
5454### Comment on the page to ask for changes
5555
from line 73
7373
7474## Related resources
7575
76> **[Catch up](/docs/claude-tag/users/use-cases/catch-up.md)**
76> **[Catch up](https://claude.com/docs/claude-tag/users/use-cases/catch-up.md)**
7777>
7878> When you need the summary, not the artifact
7979
80> **[Good habits](/docs/claude-tag/users/good-habits.md)**
80> **[Good habits](https://claude.com/docs/claude-tag/users/good-habits.md)**
8181>
8282> How to specify outputs that come back right
8383
claude-tag/users/use-cases/find-answers Changed · +4 / -4 lines
from line 12
1212
1313## Check the channel's connections
1414
15Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
15Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1616
1717| Connection | Examples | Why it matters here |
1818| :- | :- | :- |
from line 56
5656@Claude what did this channel decide about the retention policy, and when?
5757```
5858
59Answers come from this channel's history and [memory](/docs/claude-tag/users/memory.md).
59Answers come from this channel's history and [memory](https://claude.com/docs/claude-tag/users/memory.md).
6060
6161## Related resources
6262
63> **[Catch up](/docs/claude-tag/users/use-cases/catch-up.md)**
63> **[Catch up](https://claude.com/docs/claude-tag/users/use-cases/catch-up.md)**
6464>
6565> The same mechanism pointed at "what did I miss"
6666
67> **[What Claude Tag remembers](/docs/claude-tag/users/memory.md)**
67> **[What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md)**
6868>
6969> How channel knowledge accumulates
7070
claude-tag/users/use-cases/fix-bugs Changed · +7 / -7 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 32
3232
3333The done definition, CI green and the PR linking back, gives the session a finish line it can check itself against.
3434
35The pull request appears under the Claude GitHub App and links back to the Slack thread it came from. See [how agent identity works](/docs/claude-tag/concepts/agent-identity.md#agent-access).
35The pull request appears under the Claude GitHub App and links back to the Slack thread it came from. See [how agent identity works](https://claude.com/docs/claude-tag/concepts/agent-identity.md#agent-access).
3636
3737### Move a bug report to the owning team's channel
3838
from line 42
4242@Claude !fork #data-platform in acme/data-pipeline, reproduce the bug described in the linked thread, fix it, and open a draft PR. Done means CI is green and the PR links back here.
4343```
4444
45Both channels must be public, and you and Claude must both be in the target. See [Fork a thread](/docs/claude-tag/users/commands.md#fork-a-thread).
45Both channels must be public, and you and Claude must both be in the target. See [Fork a thread](https://claude.com/docs/claude-tag/users/commands.md#fork-a-thread).
4646
4747### Watch a bug channel
4848
from line 52
5252@Claude when a bug report lands in this channel, try to reproduce it. If you can, open a draft PR and tag the area owner; if you can't, reply with what you tried.
5353```
5454
55With the if/can't branch, every report gets a reply, either a draft or a list of what was tried. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
55With the if/can't branch, every report gets a reply, either a draft or a list of what was tried. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
5656
5757### Diagnose a failure without a fix
5858
from line 74
7474
7575"Tag me if anything failed" is the filter. Green runs land quietly in the thread, and only a failure interrupts you.
7676
77For repository conventions that should hold across every session that touches the code, like where files go or what a pull request must include, see [Make repo conventions stick](/docs/claude-tag/users/good-habits.md#teach-claude-something-that-sticks).
77For repository conventions that should hold across every session that touches the code, like where files go or what a pull request must include, see [Make repo conventions stick](https://claude.com/docs/claude-tag/users/good-habits.md#teach-claude-something-that-sticks).
7878
7979## Related resources
8080
81> **[Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md)**
81> **[Watch monitors and alerts](https://claude.com/docs/claude-tag/users/use-cases/watch-monitors.md)**
8282>
8383> Catching the problem before the bug report
8484
85> **[Good habits](/docs/claude-tag/users/good-habits.md)**
85> **[Good habits](https://claude.com/docs/claude-tag/users/good-habits.md)**
8686>
8787> Definitions of done for code tasks
8888
claude-tag/users/use-cases/marketing-team Changed · +8 / -8 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing. Each recipe below names the connection it uses.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing. Each recipe below names the connection it uses.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 41
4141@Claude remember for this channel: when someone tags you on a request, answer it from the brand guidelines and the marketing process docs, name the doc you used, and route anything the docs don't cover to the right owner with a one-line summary.
4242```
4343
44"Remember for this channel" saves the role to [channel memory](/docs/claude-tag/users/memory.md), so it applies to everyone's threads, not just yours. [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md) adds a weekly rollup that also sweeps posts that never tagged Claude.
44"Remember for this channel" saves the role to [channel memory](https://claude.com/docs/claude-tag/users/memory.md), so it applies to everyone's threads, not just yours. [Triage requests](https://claude.com/docs/claude-tag/users/use-cases/triage-requests.md) adds a weekly rollup that also sweeps posts that never tagged Claude.
4545
4646Some questions have no doc to cite, and a person on the team answers in the thread. When that answer will come up again, tell Claude to save it:
4747
from line 65
6565@Claude turn this thread into an announcement draft I can send to the customer list. Keep it under 200 words and match the messaging doc linked above.
6666```
6767
68Name the format, the length, and the source the draft should match. The same prompt shape produces a decision doc or a status memo; [Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts.md) lists the variants.
68Name the format, the length, and the source the draft should match. The same prompt shape produces a decision doc or a status memo; [Turn threads into docs and tickets](https://claude.com/docs/claude-tag/users/use-cases/create-artifacts.md) lists the variants.
6969
7070### Check lead and campaign state in the CRM
7171
from line 81
8181@Claude compare the leads the June campaign created against the ones that reached a queue, and post which ones stalled and at what stage.
8282```
8383
84The reply lists the stalled records and the stage where each stopped. The [HubSpot connection](/docs/claude-tag/admins/connections/hubspot.md) is created with read scopes, so prompts in this channel pull records and don't change them. For account questions, pre-call briefs, and a pipeline digest, see [Pull deal and account state](/docs/claude-tag/users/use-cases/pull-deal-state.md).
84The reply lists the stalled records and the stage where each stopped. The [HubSpot connection](https://claude.com/docs/claude-tag/admins/connections/hubspot.md) is created with read scopes, so prompts in this channel pull records and don't change them. For account questions, pre-call briefs, and a pipeline digest, see [Pull deal and account state](https://claude.com/docs/claude-tag/users/use-cases/pull-deal-state.md).
8585
8686### Schedule a weekly campaign metrics digest
8787
from line 91
9191@Claude every Monday at 9am Eastern, post last week's campaign metrics as a chart: signups by campaign, week-over-week change, and a two-line note on anything unusual.
9292```
9393
94Name the timezone in the message, since schedules run in UTC. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
94Name the timezone in the message, since schedules run in UTC. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
9595
9696### Save brand voice rules to channel memory
9797
from line 101
101101@Claude remember for this channel: headlines use sentence case, "sign up" is the verb and "signup" is the noun, and the product is never called a platform.
102102```
103103
104Keep saved entries short, since long entries crowd out everything else. For a full style guide, link the document in the channel or store it in a connected tool Claude can read, instead of re-describing its contents in memory. [What Claude Tag remembers](/docs/claude-tag/users/memory.md) covers how to check and correct what's saved.
104Keep saved entries short, since long entries crowd out everything else. For a full style guide, link the document in the channel or store it in a connected tool Claude can read, instead of re-describing its contents in memory. [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) covers how to check and correct what's saved.
105105
106106## Related resources
107107
108> **[Pull deal and account state](/docs/claude-tag/users/use-cases/pull-deal-state.md)**
108> **[Pull deal and account state](https://claude.com/docs/claude-tag/users/use-cases/pull-deal-state.md)**
109109>
110110> The full set of go-to-market prompts
111111
112> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
112> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
113113>
114114> How the scheduled digest runs, and more recipes
115115
claude-tag/users/use-cases/pull-deal-state Changed · +4 / -4 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 56
5656@Claude every Monday at 9am, post a pipeline digest: deals that moved stage last week, deals stalled more than two weeks, and renewals due in the next 30 days.
5757```
5858
59The three lines cover what moved, what's stuck, and what's coming due, so the digest reads the same way every Monday. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
59The three lines cover what moved, what's stuck, and what's coming due, so the digest reads the same way every Monday. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
6060
6161## Related resources
6262
63> **[Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions.md)**
63> **[Answer data questions](https://claude.com/docs/claude-tag/users/use-cases/answer-data-questions.md)**
6464>
6565> When the question is metrics, not accounts
6666
67> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
67> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
6868>
6969> Scheduled digests
7070
claude-tag/users/use-cases/review-documents Changed · +6 / -6 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
2121| Knowledge and docs | Google Drive, Notion, Confluence | Required. Claude reads the documents under review, and the checklist or policy they're checked against, from these tools |
2222
23Claude can reach only what the connected account can see in that tool. If a document is missing from a review, ask an admin to [share it with the connected account](/docs/claude-tag/admins/add-connections.md#limit-access-to-specific-resources).
23Claude can reach only what the connected account can see in that tool. If a document is missing from a review, ask an admin to [share it with the connected account](https://claude.com/docs/claude-tag/admins/add-connections.md#limit-access-to-specific-resources).
2424
2525## Prompts to paste
2626
from line 72
7272@Claude every Monday at 9am Pacific, check the shared folder for documents added in the past week, review each against the review checklist, and post the findings here.
7373```
7474
75Include the timezone in the message, since schedules run in UTC. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
75Include the timezone in the message, since schedules run in UTC. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
7676
77Keep the checklist as a document Claude can read, in the connected tool or linked in the channel, rather than re-describing its contents in [channel memory](/docs/claude-tag/users/memory.md).
77Keep the checklist as a document Claude can read, in the connected tool or linked in the channel, rather than re-describing its contents in [channel memory](https://claude.com/docs/claude-tag/users/memory.md).
7878
7979## Related resources
8080
81> **[Find answers in your docs](/docs/claude-tag/users/use-cases/find-answers.md)**
81> **[Find answers in your docs](https://claude.com/docs/claude-tag/users/use-cases/find-answers.md)**
8282>
8383> The same connections pointed at a single question
8484
85> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
85> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
8686>
8787> How the recurring review runs on a schedule
8888
claude-tag/users/use-cases/track-projects Changed · +5 / -5 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 41
4141@Claude every weekday at 5pm, post a project digest: what moved today, what's blocked, and what hasn't been touched in three days.
4242```
4343
44Name the format in the prompt, like the three sections here, so every digest comes back in the same readable shape. "Hasn't been touched in three days" is a number, so stalled work surfaces itself instead of depending on someone's sense of what counts as stale. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
44Name the format in the prompt, like the three sections here, so every digest comes back in the same readable shape. "Hasn't been touched in three days" is a number, so stalled work surfaces itself instead of depending on someone's sense of what counts as stale. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
4545
4646### Chase an approval
4747
from line 51
5151@Claude every weekday, check the design review discussed in this thread. If it's gone two weekdays with no reviewer reply, nudge them here; when an approval lands, post that it's done. Done means approved, not just commented on.
5252```
5353
54Define what "done" includes; see [the babysit caution](/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done).
54Define what "done" includes; see [the babysit caution](https://claude.com/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done).
5555
5656Code approvals need the code connection. Scheduled follow-ups on repositories use that same GitHub connection, with nothing extra to set up.
5757
5858## Related resources
5959
60> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
60> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
6161>
6262> Schedules and event triggers
6363
64> **[Good habits](/docs/claude-tag/users/good-habits.md)**
64> **[Good habits](https://claude.com/docs/claude-tag/users/good-habits.md)**
6565>
6666> Definitions of done that close threads
6767
claude-tag/users/use-cases/triage-requests Changed · +10 / -10 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 32
3232@Claude remember for this channel: when someone tags you on a request, check whether it duplicates something already reported, answer it directly if the answer exists, and otherwise route it to the right owner with a one-line summary. Track recurring themes.
3333```
3434
35"Remember for this channel" saves the role to [channel memory](/docs/claude-tag/users/memory.md), so it applies to everyone's threads, not just yours. Tell requesters to include `@Claude` when they post; pin the convention or add it to the channel topic.
35"Remember for this channel" saves the role to [channel memory](https://claude.com/docs/claude-tag/users/memory.md), so it applies to everyone's threads, not just yours. Tell requesters to include `@Claude` when they post; pin the convention or add it to the channel topic.
3636
3737**2. Add a weekly rollup so nothing is missed**
3838
from line 40
4040@Claude every Friday at 3pm, post a summary of this week's requests: how many, top themes, and anything still unrouted, including posts that didn't tag you.
4141```
4242
43"Including posts that didn't tag you" turns the recap into a sweep, so requests that arrived without a mention are still caught. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
43"Including posts that didn't tag you" turns the recap into a sweep, so requests that arrived without a mention are still caught. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
4444
45Answers draw on what the channel has already settled, meaning its [memory](/docs/claude-tag/users/memory.md) and its own past threads, and routing gets more accurate as corrections land in channel memory.
45Answers draw on what the channel has already settled, meaning its [memory](https://claude.com/docs/claude-tag/users/memory.md) and its own past threads, and routing gets more accurate as corrections land in channel memory.
4646
4747## Hand a request to the team that owns it
4848
from line 52
5252@Claude !fork #payments-eng take this request: the reporter needs refunds on partial orders, and their screenshots and the duplicate check are in the linked thread.
5353```
5454
55The channel you name must be public, with both you and Claude in it. See [Fork a thread](/docs/claude-tag/users/commands.md#fork-a-thread) for the other rules.
55The channel you name must be public, with both you and Claude in it. See [Fork a thread](https://claude.com/docs/claude-tag/users/commands.md#fork-a-thread) for the other rules.
5656
5757## Give Claude a runbook of standing answers
5858
5959When people keep posting the same questions in a channel, give Claude the team's settled answers instead of leaving it to derive an answer from the channel's history each time. A runbook is the team's own document of those answers, kept in whatever form the team already uses, such as a Google Doc. It can say which requests have a standard answer, which route to an owner, and which the team answers itself.
6060
61To have Claude answer from the runbook, put the standing guidance in the **Channel instructions** field on the channel's [Configure page](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). The field needs no connection, and a short runbook can go in it whole. Claude [reads a channel's untagged messages and replies to some of them on its own](/docs/claude-tag/users/when-claude-responds.md), so name the cases to leave alone as explicitly as the answers.
61To have Claude answer from the runbook, put the standing guidance in the **Channel instructions** field on the channel's [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). The field needs no connection, and a short runbook can go in it whole. Claude [reads a channel's untagged messages and replies to some of them on its own](https://claude.com/docs/claude-tag/users/when-claude-responds.md), so name the cases to leave alone as explicitly as the answers.
6262
63For a runbook kept as a document, Claude can read it when an admin has [connected the app that holds it](/docs/claude-tag/admins/add-connections.md) and the connection's account can see the document. The instruction then points at the document:
63For a runbook kept as a document, Claude can read it when an admin has [connected the app that holds it](https://claude.com/docs/claude-tag/admins/add-connections.md) and the connection's account can see the document. The instruction then points at the document:
6464
6565```text wrap theme={null}
6666Answer requests in this channel from the team's triage runbook: <link to the runbook doc>. Read it before answering. If a request isn't covered there, mention <your on-call person's handle> so they can pick it up.
from line 68
6868
6969The team keeps editing the document where it already lives, and the instruction reaches every new session in the channel.
7070
71A team that wants each change reviewed as a pull request can keep its runbook as a skill in a [skills repository](/docs/claude-tag/admins/skills-repo.md), a git repository an Owner registers and attaches to the channel; a merged pull request syncs the update to your organization automatically, and anyone in the channel can ask Claude to draft that pull request.
71A team that wants each change reviewed as a pull request can keep its runbook as a skill in a [skills repository](https://claude.com/docs/claude-tag/admins/skills-repo.md), a git repository an Owner registers and attaches to the channel; a merged pull request syncs the update to your organization automatically, and anyone in the channel can ask Claude to draft that pull request.
7272
7373When an answer changes, update the runbook where it lives. Edit the document, edit and save the **Channel instructions** field, or merge a pull request in the repository. However you ship the update, check the changed answer in a fresh thread. A thread already underway keeps the instructions and skills it started with.
7474
7575## Related resources
7676
77> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
77> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
7878>
7979> How the weekly rollup runs on a schedule
8080
81> **[What Claude Tag remembers](/docs/claude-tag/users/memory.md)**
81> **[What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md)**
8282>
8383> How the standing role persists and improves
8484
claude-tag/users/use-cases/watch-monitors Changed · +5 / -5 lines
from line 14
1414
1515## Check the channel's connections
1616
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
17Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
1818
1919| Connection | Examples | Why it matters here |
2020| :- | :- | :- |
from line 30
3030@Claude every morning at 7, check the service dashboards and post one line per service: green, or what's off and since when.
3131```
3232
33Name the output format in the schedule, like "one line per service" above, so every post reads the same way. To list or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
33Name the output format in the schedule, like "one line per service" above, so every post reads the same way. To list or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
3434
3535### Investigate a single alert
3636
from line 52
5252
5353## Keep known false alarms out of Claude's checks
5454
55Open the channel's [**Configure** page](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). In the **Channel instructions** field, list the alerts your team already treats as false alarms, so Claude skips them.
55Open the channel's [**Configure** page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). In the **Channel instructions** field, list the alerts your team already treats as false alarms, so Claude skips them.
5656
5757## Related resources
5858
59> **[Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md)**
59> **[Fix bugs](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md)**
6060>
6161> When the investigation should end in a pull request
6262
63> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
63> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
6464>
6565> Schedules and event triggers
6666
claude-tag/users/use-cases/work-with-github Changed · +12 / -12 lines
from line 16
1616
1717> [!NOTE]
1818>
19> An admin [grants a repository to the channels that need it](/docs/claude-tag/admins/attach-to-scope.md), and questions about the code work only in those channels. By default anyone in those channels can ask, and an admin can [restrict who can use Claude](/docs/claude-tag/admins/restrict-access.md#control-who-can-invoke-claude-tag).
19> An admin [grants a repository to the channels that need it](https://claude.com/docs/claude-tag/admins/attach-to-scope.md), and questions about the code work only in those channels. By default anyone in those channels can ask, and an admin can [restrict who can use Claude](https://claude.com/docs/claude-tag/admins/restrict-access.md#control-who-can-invoke-claude-tag).
2020
2121## Check the channel's connections
2222
23Check that the channel has the connection below. Ask `@Claude what can you access from this channel?` and the reply also lists which repositories the channel can reach. An admin can [add a connection](/docs/claude-tag/admins/add-connections.md) the channel is missing.
23Check that the channel has the connection below. Ask `@Claude what can you access from this channel?` and the reply also lists which repositories the channel can reach. An admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) the channel is missing.
2424
2525| Connection | Examples | Why it matters here |
2626| :- | :- | :- |
2727| Code | GitHub | Required. Reads granted repositories and opens draft pull requests |
2828
29The GitHub connection is what lets Claude clone a repository. For GitLab, an admin [connects it with an access token](/docs/claude-tag/admins/connections/gitlab.md), and Claude reads projects, manages issues, and comments on merge requests through the GitLab API.
29The GitHub connection is what lets Claude clone a repository. For GitLab, an admin [connects it with an access token](https://claude.com/docs/claude-tag/admins/connections/gitlab.md), and Claude reads projects, manages issues, and comments on merge requests through the GitLab API.
3030
31If Claude replies that a repository isn't configured, the repository wasn't granted for this channel. An admin can [verify GitHub access](/docs/claude-tag/admins/configure-github.md#verify-github-access). After the grant changes, start a fresh thread and name the repository in the first message.
31If Claude replies that a repository isn't configured, the repository wasn't granted for this channel. An admin can [verify GitHub access](https://claude.com/docs/claude-tag/admins/configure-github.md#verify-github-access). After the grant changes, start a fresh thread and name the repository in the first message.
3232
3333## Prompts to paste
3434
from line 58
5858@Claude subscribe to PR #519 in acme/data-pipeline, the schema migration. When CI finishes or a review arrives, post here, and tag me if anything failed.
5959```
6060
61Claude reads the pull request's workflow runs and logs, so the post says whether checks passed or failed. To list or cancel a subscription later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work). Because the prompt asks for a tag only on failure, passing runs post to the thread without notifying you.
61Claude reads the pull request's workflow runs and logs, so the post says whether checks passed or failed. To list or cancel a subscription later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work). Because the prompt asks for a tag only on failure, passing runs post to the thread without notifying you.
6262
6363### Hand off the change you keep postponing
6464
from line 68
6868@Claude in acme/data-pipeline, the CSV export docs still describe the old date format. Update them to match the code and open a draft PR. Done means CI is green and the PR links back here.
6969```
7070
71Writing a [definition of done](/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done) into the task lets the session check its own work. The change comes back as a draft pull request in your review queue, opened under Claude's own GitHub identity.
71Writing a [definition of done](https://claude.com/docs/claude-tag/users/good-habits.md#give-every-task-a-definition-of-done) into the task lets the session check its own work. The change comes back as a draft pull request in your review queue, opened under Claude's own GitHub identity.
7272
7373### Triage a suspected bug where the report arrives
7474
from line 78
7878@Claude a user reports that exports drop rows with empty dates. In acme/data-pipeline, is that a bug or intended behavior? If it's a bug, open a draft PR with a fix; if it's intended, explain here what the code does.
7979```
8080
81For the full arc from a bug report to green CI, including a standing watch that triages a bug channel, see [Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md). Because the prompt asks for either a fix or an explanation, the thread gets an answer even when the behavior turns out to be intended.
81For the full arc from a bug report to green CI, including a standing watch that triages a bug channel, see [Fix bugs](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md). Because the prompt asks for either a fix or an explanation, the thread gets an answer even when the behavior turns out to be intended.
8282
8383### Hand off a change and follow its pull request in one message
8484
from line 100
100100
101101> [!WARNING]
102102>
103> If you don't want Claude to merge pull requests, turn on branch protection rules that restrict who can merge. These rules apply to Claude too. Claude can't approve a pull request it opened, but the person who asked for it can; to require a second approver, see [Require a second approval on Claude's pull requests](/docs/claude-tag/admins/configure-github.md#require-a-second-approval-on-claude%E2%80%99s-pull-requests). Also write "I do the approving and merging" into the task, as the example does. The task wording states your intent, but it's an instruction Claude can lose track of, not a control. The branch protection rule is what enforces it.
103> If you don't want Claude to merge pull requests, turn on branch protection rules that restrict who can merge. These rules apply to Claude too. Claude can't approve a pull request it opened, but the person who asked for it can; to require a second approver, see [Require a second approval on Claude's pull requests](https://claude.com/docs/claude-tag/admins/configure-github.md#require-a-second-approval-on-claude%E2%80%99s-pull-requests). Also write "I do the approving and merging" into the task, as the example does. The task wording states your intent, but it's an instruction Claude can lose track of, not a control. The branch protection rule is what enforces it.
104104
105105Ask for a post after each push so you can follow the pull request from the thread instead of opening GitHub.
106106
from line 108
108108
109109If your repository has conventions Claude should follow, such as file layout, pull request labels, or dependencies to install, add them to a `CLAUDE.md` file at the repository root. When Claude clones the repository into a session, its `CLAUDE.md`, `.claude/CLAUDE.md`, and `.claude/rules/*.md` files load on the next turn, so the guidance arrives without further prompting. Skills in the repository's `.claude/skills/` folder also load, so Claude can use them in sessions that have the repository. Anyone with repository write access can edit these files, and they reach every session that works in that repository, from any channel.
110110
111Each session runs in an isolated sandbox with a standard set of preinstalled tools. Two threads are two sessions with two separate sandboxes. If the repository needs a tool that the standard set doesn't include, such as a language runtime or a database client, add the install commands to `CLAUDE.md`, and Claude [runs them when its work needs them](/docs/claude-tag/admins/configure-github.md#install-project-dependencies).
111Each session runs in an isolated sandbox with a standard set of preinstalled tools. Two threads are two sessions with two separate sandboxes. If the repository needs a tool that the standard set doesn't include, such as a language runtime or a database client, add the install commands to `CLAUDE.md`, and Claude [runs them when its work needs them](https://claude.com/docs/claude-tag/admins/configure-github.md#install-project-dependencies).
112112
113113> [!NOTE]
114114>
115> A `CLAUDE.md` is guidance rather than a gate. If a pull request must carry a label or pass a check, make that a repository rule. For where `CLAUDE.md` sits among channel memory, channel instructions, and skills, see [Teach Claude something that sticks](/docs/claude-tag/users/good-habits.md#teach-claude-something-that-sticks).
115> A `CLAUDE.md` is guidance rather than a gate. If a pull request must carry a label or pass a check, make that a repository rule. For where `CLAUDE.md` sits among channel memory, channel instructions, and skills, see [Teach Claude something that sticks](https://claude.com/docs/claude-tag/users/good-habits.md#teach-claude-something-that-sticks).
116116
117117## Related resources
118118
119> **[Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md)**
119> **[Fix bugs](https://claude.com/docs/claude-tag/users/use-cases/fix-bugs.md)**
120120>
121121> The full arc from a bug report to a draft pull request and green CI
122122
123> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
123> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
124124>
125125> Pull request subscriptions and other standing work
126126
claude-tag/users/use-cases/your-own-channel Changed · +10 / -10 lines
from line 12
1212
1313A one-to-one DM is the other place to work alone with Claude, and the two surfaces run on different accounts. A DM session runs with your own claude.ai connectors, the work is attributed to you (pull requests excepted; the Claude GitHub App authors those), and usage bills to your seat. What Claude does there sits outside channel and workspace memory.
1414
15Your own channel runs with the connections an admin set for it, usage bills to the organization, and what Claude learns there accumulates as [channel memory](/docs/claude-tag/users/memory.md) that later threads build on. [Routines](/docs/claude-tag/users/proactivity.md) can post there on a schedule. When scratch work turns into a team task, the thread is ready to [hand to a teammate](#hand-a-thread-to-a-teammate).
15Your own channel runs with the connections an admin set for it, usage bills to the organization, and what Claude learns there accumulates as [channel memory](https://claude.com/docs/claude-tag/users/memory.md) that later threads build on. [Routines](https://claude.com/docs/claude-tag/users/proactivity.md) can post there on a schedule. When scratch work turns into a team task, the thread is ready to [hand to a teammate](#hand-a-thread-to-a-teammate).
1616
17Pick a DM for personal tasks on your own connections, or for data that shouldn't run through a shared channel connection. Pick your own channel for standing work, and for anything you might later hand off or show someone. [Pick the right surface](/docs/claude-tag/users/good-habits.md#pick-the-right-surface) compares both against a team channel.
17Pick a DM for personal tasks on your own connections, or for data that shouldn't run through a shared channel connection. Pick your own channel for standing work, and for anything you might later hand off or show someone. [Pick the right surface](https://claude.com/docs/claude-tag/users/good-habits.md#pick-the-right-surface) compares both against a team channel.
1818
1919## Set up the channel
2020
211. Create a Slack channel and add Claude with `/invite @Claude`. Make the channel public unless the work needs to be private, so teammates can find and join the work. Either way, the channel keeps its own [memory](/docs/claude-tag/users/memory.md).
222. Ask `@Claude what can you access from this channel?`. None of the prompts below require a connection, and an admin can [add a connection](/docs/claude-tag/admins/add-connections.md) your work needs, like the issue tracker or GitHub.
211. Create a Slack channel and add Claude with `/invite @Claude`. Make the channel public unless the work needs to be private, so teammates can find and join the work. Either way, the channel keeps its own [memory](https://claude.com/docs/claude-tag/users/memory.md).
222. Ask `@Claude what can you access from this channel?`. None of the prompts below require a connection, and an admin can [add a connection](https://claude.com/docs/claude-tag/admins/add-connections.md) your work needs, like the issue tracker or GitHub.
23233. Tell Claude how the channel should behave and ask it to remember, as in `@Claude remember for this channel: keep replies short, and format digests as tables`. Later sessions in the channel start from what you saved.
2424
2525## Prompts to paste
from line 54
5454@Claude every Friday at 3pm Pacific, post a digest of this channel: what closed this week, what's still open, and what hasn't moved in five days. Skip anything with a ✅ reaction.
5555```
5656
57Give the digest a concrete threshold, like five days without movement, and stalled work shows up without you asking for it. React ✅ to anything you consider done, and the digest drops it. Include the timezone in the message, since schedules run in UTC. To list, edit, or cancel scheduled work later, see [Manage standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work).
57Give the digest a concrete threshold, like five days without movement, and stalled work shows up without you asking for it. React ✅ to anything you consider done, and the digest drops it. Include the timezone in the message, since schedules run in UTC. To list, edit, or cancel scheduled work later, see [Manage standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work).
5858
5959### Hand a thread to a teammate
6060
from line 72
7272@Claude !fork #export-team summarize the export-flow bug for the team: what's been tried, what's decided, and what's still open.
7373```
7474
75The target must be a public channel that both you and Claude are in, and your own channel must be public for the fork to run. See [Fork a thread](/docs/claude-tag/users/commands.md#fork-a-thread).
75The target must be a public channel that both you and Claude are in, and your own channel must be public for the fork to run. See [Fork a thread](https://claude.com/docs/claude-tag/users/commands.md#fork-a-thread).
7676
7777### Chase your open follow-ups
7878
from line 94
9494@Claude I'm out next week and Marta is covering. Where things stand: the billing migration is waiting on legal, the dashboard rebuild is paused until the design review closes, and the onboarding runbook is pinned in this channel. Leave the pricing config alone until I'm back. While I'm out, when anyone asks here, answer from this message and the channel's history. Pause this channel's scheduled posts until I say I'm back.
9595```
9696
97While you're out, a teammate who needs to know where a piece of work stands, or who owns it, tags `@Claude` in your channel and gets the answer from the pinned handoff message, the channel's history, and [channel memory](/docs/claude-tag/users/memory.md). If you set a Slack status or an out-of-office reply, point people to this channel in it.
97While you're out, a teammate who needs to know where a piece of work stands, or who owns it, tags `@Claude` in your channel and gets the answer from the pinned handoff message, the channel's history, and [channel memory](https://claude.com/docs/claude-tag/users/memory.md). If you set a Slack status or an out-of-office reply, point people to this channel in it.
9898
99The pause covers this channel's own routines, like the Friday digest and the Monday sweep this page sets up, so scheduled posts stop piling up unread. Anyone in the channel can [list, edit, or disable its standing work](/docs/claude-tag/users/proactivity.md#manage-standing-work), so a teammate can turn a routine back on early if the coverage needs it.
99The pause covers this channel's own routines, like the Friday digest and the Monday sweep this page sets up, so scheduled posts stop piling up unread. Anyone in the channel can [list, edit, or disable its standing work](https://claude.com/docs/claude-tag/users/proactivity.md#manage-standing-work), so a teammate can turn a routine back on early if the coverage needs it.
100100
101101On your first morning back, ask Claude to catch you up.
102102
from line 108
108108
109109## Related resources
110110
111> **[Set up routines](/docs/claude-tag/users/proactivity.md)**
111> **[Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md)**
112112>
113113> List, edit, or disable the standing work this page sets up
114114
115> **[Good habits](/docs/claude-tag/users/good-habits.md)**
115> **[Good habits](https://claude.com/docs/claude-tag/users/good-habits.md)**
116116>
117117> Pick the right surface and write tasks that close
118118
claude-tag/users/when-claude-responds Changed · +20 / -20 lines
from line 6
66>
77> Claude Tag is in public beta. Features and behavior described here may change before general availability.
88
9Claude replies without an @-mention in one-to-one DMs, in any thread it's already part of, and to channel and group DM messages it judges warrant a reply. In a channel, Claude reads the messages and replies to some of them on its own, so an @-mention is how you guarantee a reply, not a requirement for one. This page covers how Claude decides whether to reply to a message nobody tagged it in, how to turn those replies off for a thread or a whole channel, and which messages never get a reply. Work Claude does on a schedule rather than in reply to a message is a [routine](/docs/claude-tag/users/proactivity.md), which has its own controls.
9Claude replies without an @-mention in one-to-one DMs, in any thread it's already part of, and to channel and group DM messages it judges warrant a reply. In a channel, Claude reads the messages and replies to some of them on its own, so an @-mention is how you guarantee a reply, not a requirement for one. This page covers how Claude decides whether to reply to a message nobody tagged it in, how to turn those replies off for a thread or a whole channel, and which messages never get a reply. Work Claude does on a schedule rather than in reply to a message is a [routine](https://claude.com/docs/claude-tag/users/proactivity.md), which has its own controls.
1010
1111## What triggers a response
1212
from line 17
1717| A one-to-one DM with Claude | Always. Every message is addressed to Claude already |
1818| A thread Claude is already in | Yes, unless you've [quieted the thread](#quiet-one-conversation). Once Claude has joined, every reply there reaches it without another mention |
1919| A channel, top-level | Sometimes. [What Claude does with a channel message](#what-claude-does-with-a-channel-message) describes how it decides. Include `@Claude` to guarantee a reply, or [turn unprompted replies off](#quiet-the-whole-channel) |
20| A group DM that includes Claude, top-level | Sometimes. See [When Claude replies in a group DM](/docs/claude-tag/users/group-dms.md#when-claude-replies-in-a-group-dm) |
20| A group DM that includes Claude, top-level | Sometimes. See [When Claude replies in a group DM](https://claude.com/docs/claude-tag/users/group-dms.md#when-claude-replies-in-a-group-dm) |
2121| A message another app or bot posted | No. Claude reads it as context. To get a reply, have the app include `@Claude` in its message. [Messages from other apps and bots](#messages-from-other-apps-and-bots) covers when that mention goes unanswered |
2222
23When you @-mention Claude in a channel, it reacts to your message with an emoji within a few seconds to show that it picked the message up. The message goes to the channel's own [session](/docs/claude-tag/concepts/glossary.md#session), the session Claude works from at the channel's top level. It then answers in a thread under your message, or starts a [working session](/docs/claude-tag/concepts/how-it-works.md) in that thread when the request needs investigation, tools, or a longer exchange.
23When you @-mention Claude in a channel, it reacts to your message with an emoji within a few seconds to show that it picked the message up. The message goes to the channel's own [session](https://claude.com/docs/claude-tag/concepts/glossary.md#session), the session Claude works from at the channel's top level. It then answers in a thread under your message, or starts a [working session](https://claude.com/docs/claude-tag/concepts/how-it-works.md) in that thread when the request needs investigation, tools, or a longer exchange.
2424
2525Once a working session starts, a working indicator with a **Stop** button appears at the bottom of the thread. A reaction with no indicator means Claude picked your message up and is either still deciding or answering directly in the thread, not that it missed you.
2626
from line 28
2828
2929## What Claude does with a channel message
3030
31Claude reads every top-level message in a channel it belongs to, and the replies in the channel's threads, whether or not anyone tagged it. For each message, it decides what to do from the channel's recent messages, the channel's [memory](/docs/claude-tag/users/memory.md), and any instructions your admin has set or a channel member has asked it to remember, and does one of four things.
31Claude reads every top-level message in a channel it belongs to, and the replies in the channel's threads, whether or not anyone tagged it. For each message, it decides what to do from the channel's recent messages, the channel's [memory](https://claude.com/docs/claude-tag/users/memory.md), and any instructions your admin has set or a channel member has asked it to remember, and does one of four things.
3232
3333* **Nothing.** This is the usual outcome. In a channel where nobody has told Claude which kinds of messages to answer, Claude leaves untagged messages alone. The one exception is a message in which someone states a concrete need Claude can meet; Claude may then reply once, in a thread, offering to do it.
3434* **A short reply in a thread under the message.** Claude replies on its own only when it already has the answer, from the channel's history or its memory, and the answer fits in one message. Replies of this kind carry the plain name **Claude**; see [The name on a reply](#the-name-on-a-reply).
from line 35
3535* **A working session in the message's thread.** When a message needs investigation, tools, or a longer exchange, Claude starts a working session there and posts the work in that thread. For an untagged message, Claude does this only when someone in the channel has told it to pick up that kind of work, as described below the list.
3636* **A hand-off to work already in progress.** When a message adds to something Claude is already working on in another thread, for example a new detail about a bug it's investigating, Claude passes the message to that working session instead of replying. Claude posts nothing in the channel when it does this; anything the new information changes, it reports in the thread where the work is happening.
3737
38To have Claude answer more kinds of untagged messages in a channel, tell it which kinds, in the channel, and ask it to remember. For example, `@Claude remember for this channel: answer questions about the deploy process without waiting to be tagged` saves the instruction to channel memory, and Claude applies it to everyone's messages there. Claude also records in channel memory whether people in the channel act on its unprompted replies or ignore them, and replies less in a channel that ignores them. [What Claude Tag remembers](/docs/claude-tag/users/memory.md) covers how to see and change what it saved.
38To have Claude answer more kinds of untagged messages in a channel, tell it which kinds, in the channel, and ask it to remember. For example, `@Claude remember for this channel: answer questions about the deploy process without waiting to be tagged` saves the instruction to channel memory, and Claude applies it to everyone's messages there. Claude also records in channel memory whether people in the channel act on its unprompted replies or ignore them, and replies less in a channel that ignores them. [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) covers how to see and change what it saved.
3939
4040## Turn automatic replies on or off
4141
from line 48
4848| Where | How |
4949| :- | :- |
5050| In Slack | Ask Claude in the channel, for example "@Claude only respond in this channel when someone @-mentions you" or "@Claude respond to messages here even when nobody mentions you." Claude confirms the change. |
51| The channel's Configure page | Open the **Configure** link in the footer of any Claude reply in the channel, switch the **Respond automatically** toggle, and click **Save**. See [Configure Claude for a channel](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). |
51| The channel's Configure page | Open the **Configure** link in the footer of any Claude reply in the channel, switch the **Respond automatically** toggle, and click **Save**. See [Configure Claude for a channel](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). |
5252| Claude Tag admin settings (Owners and Claude Tag admins) | Go to [**Organization settings > Claude Tag**](https://claude.ai/admin-settings/claude-tag?access=channels), select the channel on the **Channels** tab, and switch **Respond automatically** on the channel's **General** tab. |
5353
54An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) can set [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) to **Block** for a channel, a workspace, or all of Slack. When the setting is **Block**, Claude declines to change **Respond automatically** when anyone asks in Slack, and channel members can't switch the toggle on the channel's Configure page. An Owner or a Claude Tag admin can still change the setting in Claude Tag admin settings, and a [channel manager](/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still switch the toggle on the Configure page of a channel assigned to them.
54An Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) can set [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) to **Block** for a channel, a workspace, or all of Slack. When the setting is **Block**, Claude declines to change **Respond automatically** when anyone asks in Slack, and channel members can't switch the toggle on the channel's Configure page. An Owner or a Claude Tag admin can still change the setting in Claude Tag admin settings, and a [channel manager](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still switch the toggle on the Configure page of a channel assigned to them.
5555
5656The setting covers the channel's messages, not DMs. To quiet a single thread instead of the whole channel, [ask Claude in that thread](#quiet-one-conversation).
5757
from line 59
5959
6060> [!NOTE]
6161>
62> Separately from **Respond automatically**, an Owner or a Claude Tag admin can [turn Claude off in channels](/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
62> Separately from **Respond automatically**, an Owner or a Claude Tag admin can [turn Claude off in channels](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
6363
6464## Messages from other apps and bots
6565
from line 69
6969
7070* The channel's [**Respond automatically**](#turn-automatic-replies-on-or-off) setting is off.
7171* Claude has [stopped reading the channel](#when-claude-stops-reading-a-channel) because of message volume.
72* The channel is a [Slack Connect channel](/docs/claude-tag/admins/restrict-access.md#when-claude-does-not-answer-in-a-slack-connect-channel), shared with another company. Claude reads what apps, bots, and workflows post there as context but doesn't reply to them.
72* The channel is a [Slack Connect channel](https://claude.com/docs/claude-tag/admins/restrict-access.md#when-claude-does-not-answer-in-a-slack-connect-channel), shared with another company. Claude reads what apps, bots, and workflows post there as context but doesn't reply to them.
7373
7474A person's mention reaches Claude in each of these cases.
7575
76Because Claude reads those messages, when a person asks about an alert a bot posted, Claude can answer from it. To have Claude act on what an integration posts, mention it in the channel or in the message's thread. For example, reply to a bot-posted alert with `@Claude triage this`. To have Claude check the channel on a schedule and post what needs attention, set up a [routine](/docs/claude-tag/users/proactivity.md).
76Because Claude reads those messages, when a person asks about an alert a bot posted, Claude can answer from it. To have Claude act on what an integration posts, mention it in the channel or in the message's thread. For example, reply to a bot-posted alert with `@Claude triage this`. To have Claude check the channel on a schedule and post what needs attention, set up a [routine](https://claude.com/docs/claude-tag/users/proactivity.md).
7777
7878## The name on a reply
7979
from line 80
8080Claude doesn't post every reply under the same display name. The name shows which kind of work produced the reply, in two forms:
8181
8282* **Claude**, the name alone: the reply comes from Claude's ambient presence in the channel, including unprompted replies
83* **Claude** followed by a short description of the task in square brackets: the reply comes from a [working session](/docs/claude-tag/concepts/how-it-works.md) handling that task in its thread. The description changes with every task, so a channel might show something like `Claude [reviewing the launch checklist]`, `Claude [debugging a failing deploy]`, or `Claude [summarizing customer feedback]`.
83* **Claude** followed by a short description of the task in square brackets: the reply comes from a [working session](https://claude.com/docs/claude-tag/concepts/how-it-works.md) handling that task in its thread. The description changes with every task, so a channel might show something like `Claude [reviewing the launch checklist]`, `Claude [debugging a failing deploy]`, or `Claude [summarizing customer feedback]`.
8484
8585## Make a channel quieter
8686
from line 94
9494@Claude only respond when I @-mention you
9595```
9696
97Claude stops following that thread, and the rest of the channel is unaffected. This is the fix when one busy thread is the noise. The [`!mute` command](/docs/claude-tag/users/commands#mute-or-unmute-a-thread) goes further and silences the thread entirely; `@Claude !unmute`, or an @-mention that carries a request, turns it back on. Selecting the thumbs-down button under one of Claude's replies also mutes the thread, as [Thumbs-down button and muting](/docs/claude-tag/users/commands.md#thumbs-down-button-and-muting) describes.
97Claude stops following that thread, and the rest of the channel is unaffected. This is the fix when one busy thread is the noise. The [`!mute` command](https://claude.com/docs/claude-tag/users/commands#mute-or-unmute-a-thread) goes further and silences the thread entirely; `@Claude !unmute`, or an @-mention that carries a request, turns it back on. Selecting the thumbs-down button under one of Claude's replies also mutes the thread, as [Thumbs-down button and muting](https://claude.com/docs/claude-tag/users/commands.md#thumbs-down-button-and-muting) describes.
9898
9999### Quiet the whole channel
100100
from line 104
104104@Claude only respond in this channel when someone @-mentions you directly.
105105```
106106
107Claude confirms the change, which is channel-wide, not just for you. You can make the same change with the toggle on the channel's Configure page, and an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) can change it in [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag). If Claude declines because an Owner or a Claude Tag admin has locked the channel's settings, ask one of them to make the change in Claude Tag admin settings, as [Turn automatic replies on or off](#turn-automatic-replies-on-or-off) describes.
107Claude confirms the change, which is channel-wide, not just for you. You can make the same change with the toggle on the channel's Configure page, and an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) can change it in [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag). If Claude declines because an Owner or a Claude Tag admin has locked the channel's settings, ask one of them to make the change in Claude Tag admin settings, as [Turn automatic replies on or off](#turn-automatic-replies-on-or-off) describes.
108108
109Threads Claude already joined keep forwarding replies, so quiet those individually with the in-thread line above. The [`!mute` command](/docs/claude-tag/users/commands#mute-or-unmute-a-thread) quiets one thread at a time and does nothing at a channel's top level.
109Threads Claude already joined keep forwarding replies, so quiet those individually with the in-thread line above. The [`!mute` command](https://claude.com/docs/claude-tag/users/commands#mute-or-unmute-a-thread) quiets one thread at a time and does nothing at a channel's top level.
110110
111111### Remove Claude Tag from the channel
112112
from line 116
116116/remove @Claude
117117```
118118
119Claude can no longer read or post in that channel. Any member can run this unless your Slack admin restricts the command. Admins have further options, through full removal from the workspace, on [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access.md).
119Claude can no longer read or post in that channel. Any member can run this unless your Slack admin restricts the command. Admins have further options, through full removal from the workspace, on [Restrict where Claude Tag operates](https://claude.com/docs/claude-tag/admins/restrict-access.md).
120120
121121## When Claude stops reading a channel
122122
from line 136
136136A few cases produce silence even when the message includes a mention:
137137
138138* **Editing a message to add the mention.** An edit doesn't trigger a response. Delete the message and send a new one with `@Claude` included.
139* **Channels with guest accounts.** By default, Claude is off in channels that include guests; an Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan, or send them [the guest access setting](/docs/claude-tag/admins/restrict-access.md#restrict-guest-channels).
139* **Channels with guest accounts.** By default, Claude is off in channels that include guests; an Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan, or send them [the guest access setting](https://claude.com/docs/claude-tag/admins/restrict-access.md#restrict-guest-channels).
140140* **Channels shared across workspaces connected to different Claude organizations.** Every workspace where Claude runs is connected to a Claude organization, the account a company sets up for Claude. When a channel is shared across workspaces connected to different Claude organizations, Claude won't reply there and posts a refusal message instead. You can't tell from Slack how a workspace is connected; the refusal message itself is the signal. Use a channel that belongs to one workspace, or send Claude a DM.
141* **Slack Connect channels.** By default, Claude is off in [channels shared with another company](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), and a mention there gets no reply and no notice. An Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan to change [**How should Claude work in channels with guests**](/docs/claude-tag/admins/restrict-access.md#slack-connect-channels).
141* **Slack Connect channels.** By default, Claude is off in [channels shared with another company](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), and a mention there gets no reply and no notice. An Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan to change [**How should Claude work in channels with guests**](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels).
142142
143143When the workspaces sharing a channel all belong to one Claude organization, Claude replies there, but with only your organization's default access and settings. The repositories, instructions, and memory set up for that channel or its workspaces don't apply, and Claude posts a notice in the thread explaining this from time to time. The guest check above still applies first where guest access is restricted.
144144
145To confirm a channel's setting, check the **Respond automatically** toggle on its [Configure page](/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). To confirm an instruction Claude saved, ask `@Claude what do you remember about responding in this channel?`, and see [What Claude Tag remembers](/docs/claude-tag/users/memory.md) for where instructions are stored and how to change them.
145To confirm a channel's setting, check the **Respond automatically** toggle on its [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). To confirm an instruction Claude saved, ask `@Claude what do you remember about responding in this channel?`, and see [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) for where instructions are stored and how to change them.
146146
147147## Related resources
148148
149* [Customize Claude Tag](/docs/claude-tag/admins/customize.md): the settings only an admin can change, if channel memory isn't enough
150* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access.md): the admin-side controls, from guest channels to full removal
149* [Customize Claude Tag](https://claude.com/docs/claude-tag/admins/customize.md): the settings only an admin can change, if channel memory isn't enough
150* [Restrict where Claude Tag operates](https://claude.com/docs/claude-tag/admins/restrict-access.md): the admin-side controls, from guest channels to full removal
151151