One read of Claude Documentationclaude-docs-20261029T210708Z
5 pages moved out of 280 read.
Pages moved
5
significant first
Pages read
280
in this capture
Captured
21:07 UTC
Corpus hash
577d611ae7b0
corpus-hash
What this read moved
1-5 of 5claude-tag/users/commands Changed · +8 / -6 lines
from line 8
88
99A command is `@Claude` followed immediately by one of a few exact words starting with `!`. Claude matches the message against that word and runs a fixed action instead of starting a normal turn.
1010
11`!help`, `!configure`, `!restart`, `!status`, `!mute`, and `!unmute` must stand alone: adding extra words, as in `!restart` with words tacked on, makes the message an ordinary prompt instead. `!fast` runs alone or with `on` or `off`. `!feedback`, `!routines`, and `!fork` accept text after the command, covered below.
11`!help`, `!configure`, `!restart`, `!status`, `!mute`, and `!unmute` must stand alone: adding extra words, as in `!restart` with words tacked on, makes the message an ordinary prompt instead. `!fast` runs alone or with `on` or `off`. `!feedback` and `!fork` accept text after the command, and `!scheduled` accepts a channel mention or ID.
1212
1313## See the commands available to you
1414
from line 156
156156## List the routines in a channel
157157
158158```text wrap theme={null}
159@Claude !routines
159@Claude !scheduled
160160```
161161
162162Claude 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
164* **For the current channel**, run `!routines` in that channel.
165* **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.
164* **For the current channel**, run `!scheduled` in that channel.
165* **For another channel**, add the channel mention or its ID, as in `@Claude !scheduled #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.
166166
167If the single word after `!routines` isn't a channel mention or ID, Claude replies with how to use the command. Adding two or more words makes the message an ordinary prompt that starts a normal turn instead.
167If the single word after `!scheduled` isn't a channel mention or ID, Claude replies with how to use the command. Adding two or more words makes the message an ordinary prompt that starts a normal turn instead.
168168
169`!routines`, the command's earlier name, works the same way.
170
169171## Fork a thread
170172
171173```text wrap theme={null}
from line 192
190192
191193## Related resources
192194
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
195* [Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md): the standing work `!scheduled` lists, and how to create, edit, or disable it
194196* [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
195197* [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
196198
claude-tag/concepts/glossary Changed · +1 / -1 lines
from line 65
6565
6666A scheduled or run-once task Claude runs on its own, such as a daily digest or a channel watch. Anyone in a channel can ask Claude to set one up, list what's scheduled, or disable one. Routines run with the channel's access, not the creator's.
6767
68Claude Code also has a feature named routines. Those run under an individual user's account; Claude Tag routines run under the agent identity.
68Claude Code has a separate feature, [cloud scheduled tasks](https://code.claude.com/docs/en/routines), formerly named routines. Cloud scheduled tasks run under an individual user's account; Claude Tag routines run under the agent identity.
6969
7070## Rule
7171
claude-tag/users/proactivity Changed · +2 / -2 lines
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`](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.
107* **List.** Ask "what routines do you have set up in this channel?", or send [`@Claude !scheduled`](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 `!scheduled`, which lists the channel's routines wherever you send it. Add a channel mention or its ID, as in `@Claude !scheduled #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 116
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.
117117* 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`](https://claude.com/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 !scheduled`](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.
121121* 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
claude-tag/users/prompt-library Changed · +1 / -1 lines
from line 108
108108@Claude what routines do you have set up in this channel?
109109```
110110
111**Why it works**: schedules are channel state, and someone else may have set them up. Check what exists before you create a duplicate digest. When you ask in plain language from inside a thread, Claude lists that thread's routines first and may leave out the rest of the channel's, so send `@Claude !routines` there instead.
111**Why it works**: schedules are channel state, and someone else may have set them up. Check what exists before you create a duplicate digest. When you ask in plain language from inside a thread, Claude lists that thread's routines first and may leave out the rest of the channel's, so send `@Claude !scheduled` there instead.
112112
113113```text wrap theme={null}
114114@Claude disable the daily digest job.
government/deploy-claude-code/configure Changed · +1 / -1 lines
from line 161
161161* Where the Claude Code extension for VS Code is used, have users remove an earlier claude.ai sign-in with `claude auth logout` or the extension's **Claude Code: Logout** command before they sign in through the gateway, not after: both commands clear every credential Claude Code has stored, the gateway sign-in included.
162162* To take a device out of this setup, have its users sign out with `claude auth logout` before you remove the settings.
163163* After sign-in, the organization's settings turn off the Claude Code settings that run a helper command (`apiKeyHelper`, `proxyAuthHelper`, `awsAuthRefresh`, `awsCredentialExport`, `gcpAuthRefresh`, `otelHeadersHelper`), wherever it is set. If your devices reach the network through a proxy that needs a helper command to authenticate, raise this with your Anthropic representative before you deploy.
164* With Claude for Government, the command-line tool has no access to Claude Code features that [require a claude.ai account](https://code.claude.com/docs/en/feature-availability#features-that-require-a-claude-subscription), such as cloud sessions, Remote Control, and routines. [Fast mode](https://code.claude.com/docs/en/fast-mode) isn't available either.
164* With Claude for Government, the command-line tool has no access to Claude Code features that [require a claude.ai account](https://code.claude.com/docs/en/feature-availability#features-that-require-a-claude-subscription), such as cloud sessions, Remote Control, and cloud scheduled tasks. [Fast mode](https://code.claude.com/docs/en/fast-mode) isn't available either.
165165* With these settings Claude Code does not check for or install updates in the background. Distribute new versions through your software deployment tooling, or have users run `claude update` (standard installer) or their package manager.
166166* Code sessions inside Claude Desktop sign in through Claude Desktop, not through these settings, but the `env` block applies to them too. For the other settings that govern them on a device that also has these managed settings, see [Code in Claude Desktop](https://claude.com/docs/government/security/security-and-data-handling.md#code-in-claude-desktop).
167167