Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.223 ·

Plan mode artifacts-first field is present but inert

Plan mode has an artifacts-first switch wired up, but nothing in this build ever turns it on.

Nothing to try yet Notable In Development
JSON All of v2.1.223
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Plan ModeArea: what it touches
In DevelopmentKind: in v2.1.223,
What probably matters to youSection of the release

The artifactsFirst plan-reminder field has full reentry and telemetry handling, but its supplying helper returns nothing so the branch never runs.

What

Plan mode reminder attachments carry a new artifactsFirst field with full reentry, refresh and telemetry handling, but nothing in this build ever sets it.

Details
  • A change in the value forces a full rather than sparse plan_mode reminder, and a new predicate detects whether a prior attachment carried it.
  • A plan_artifacts_first_active telemetry event fires when the value is set but no attachment has carried it yet.
  • The helper that would supply the value declares its locals and returns them unassigned, so artifactsFirst is always undefined and the branch never activates. The gate that would set it appears to have been folded out at build time.
Evidence

plan_artifacts_first_active

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

See this entry in the whole of v2.1.223 →

Feedback