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

Claude Code v2.1.246 ·

One-off scheduled runs are always documented in /schedule

/schedule now always documents one-time runs and how to re-arm one that already fired.

Use it now Improvements
JSON All of v2.1.246
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Scheduled RunsArea: what it touches
ImprovementsKind: in v2.1.246,
What probably matters to youSection of the release
What

The scheduled-runs command no longer hides one-time runs behind a flag; every session sees that a routine can be scheduled to fire once, and that a run reported as having ended for reason run_once_fired can be re-armed by setting a new one-shot time.

Details
  • The flag that previously gated this, tengu_mocha_barista, is gone from the build entirely.
  • The command itself still requires the gate tengu_surreal_dali (off unless the server says otherwise), the allow_remote_sessions permission, and a non-cloud session.
Evidence

run_once_fired

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/schedule
Feature flag
tengu_mocha_barista On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.246: not a boolean we can read

tengu_surreal_dali Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.246: off

Read once, for one account on one subscription tier, against v2.1.246. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Common workflows touched a line naming /schedule after this was published. | [`/loop`](/docs/en/scheduled-tasks) | The current CLI session | Quick polling while a session is open. `--resume` and `--continue` restore unexpired fixed-interval loops. | common-workflows see the edit
Confirmed since Anthropic's documentation has since written up /schedule, on Schedule recurring tasks in Claude Code Desktop. | | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | desktop-scheduled-tasks see the edit
What has happened since
Flag reading moved The flag server now returns on for tengu_mocha_barista, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_mocha_barista, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /schedule, on Schedule recurring tasks in Claude Code Desktop.

See this entry in the whole of v2.1.246 →

Feedback