Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · claude-docs

Set up routines changedclaude-tag/users/proactivity

Nearest release: v2.1.314, published 3 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 29 Oct 2026 20:56 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 29 Oct 2026 21:07 UTC.

Upstream edited
Recorded here
Lines+2added
Lines−2removed
From line 104 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits11to this page, all time

The whole hunk

from line 104, old and new numbered
/
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 
Feedback