Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

One-off scheduled runs are always documented in /schedule

Use it now
Useful3 Signal2
Scheduled Runs

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

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 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: on

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

/schedule
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.246 →