Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 14 Oct 2026
One change · claude-code

Automate work with routines changedroutines

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

Upstream edited this page at 14 Oct 2026 02:48 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 14 Oct 2026 03:07 UTC.

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

### When a run publishes an artifact without asking

The whole hunk

from line 44, old and new numbered
/
lines
from line 44
4444 
4545The creation form sets up the routine's prompt, repositories, environment, connectors, and triggers.
4646 
47Routines run autonomously as full Claude Code cloud sessions: there is no permission-mode picker, and the session runs shell commands, uses [skills](/docs/en/skills) committed to the cloned repository, and calls any connectors you include, all without stopping for approval apart from some [artifact](/docs/en/artifacts) actions.
47Routines run autonomously as full Claude Code cloud sessions: there is no permission-mode picker, and the session runs shell commands, uses [skills](/docs/en/skills) committed to the cloned repository, and calls any connectors you include, all without stopping for approval apart from some [artifact actions](#when-a-run-publishes-an-artifact-without-asking).
4848 
4949What a routine can reach is determined by the repositories you select, the [environment's](/docs/en/cloud-environments) network access and variables, and the connectors you include. Scope each of those to what the routine actually needs.
5050 
51When the routine's schedule or **Run now** starts a run, Claude republishes an existing artifact without asking only when all of these hold:
52 
53* You can edit the artifact and it belongs to your own organization
54* The artifact isn't shared publicly
55* If the artifact is shared with specific people or your organization, its viewers don't automatically see each new version
56* The publish carries only the page, with no supporting files or anything else added, and doesn't force over a newer version
57* The page holds no grant that reaches beyond the page, such as [connector calls](/docs/en/artifacts#pull-live-data-with-mcp-connectors)
58 
59In every other case, including publishing a new artifact, Claude asks first. When a routine's job is to keep a page current, give it an artifact you already published.
60 
6151Routines belong to your individual claude.ai account. They are not shared with teammates, and their runs count against your account's [usage and limits](#usage-and-limits). Anything a routine does through your connected GitHub identity or connectors appears as you: commits and pull requests carry your GitHub user, and Slack messages, Linear tickets, or other connector actions use your linked accounts for those services.
6252 
6353### Create from the web
from line 329
339329When you create a routine, all of your currently connected connectors are included by default. Remove any that aren't needed to limit which tools Claude has access to during the run. You can also add connectors directly from the routine form.
340330 
341331To manage or add connectors outside of the routine form, visit [claude.ai/customize/connectors](https://claude.ai/customize/connectors) or use `/schedule update` in the CLI.
332 
333### When a run publishes an artifact without asking
334 
335When a routine's schedule or **Run now** starts a run, Claude can publish a new [artifact](/docs/en/artifacts) without asking. The new artifact is visible only to you until you [share it](/docs/en/artifacts#share-an-artifact). If the publish declares runtime capabilities for the page, such as [connector calls](/docs/en/artifacts#pull-live-data-with-mcp-connectors) or [file downloads](/docs/en/artifacts#offer-a-file-download), Claude asks first.
336 
337In those runs, Claude republishes an existing artifact without asking only when all of these hold:
338 
339* You can edit the artifact and it belongs to your own organization
340* If the publish carries more than the page, such as supporting files, you own the artifact
341* The artifact isn't shared publicly
342* If the artifact is shared with specific people or your organization, its viewers don't automatically see each new version
343* The publish doesn't force over a newer version
344* The publish doesn't declare runtime capabilities for the page
345* The existing page holds no grant that reaches beyond the page, such as [connector calls](/docs/en/artifacts#pull-live-data-with-mcp-connectors)
346 
347In every other case, including a run that an API or GitHub trigger starts, Claude asks first.
348 
349When a routine's job is to keep a page current, give it an artifact you already published.
342350 
343351### Environments and network access
344352 
Feedback