Plan mode has an artifacts-first switch wired up, but nothing in this build ever turns it on.
The artifactsFirst plan-reminder field has full reentry and telemetry handling, but its supplying helper returns nothing so the branch never runs.
What's wrong with this entry?
Plan mode reminder attachments carry a new artifactsFirst field with full reentry, refresh and telemetry handling, but nothing in this build ever sets it.
- 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_activetelemetry 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
artifactsFirstis always undefined and the branch never activates. The gate that would set it appears to have been folded out at build time.
plan_artifacts_first_active
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.
-
v2.1.235
Very large plans cannot be approved
Both mention plan mode
-
v2.1.235
Plans over 200,000 characters cannot be approved
Both mention plan mode
-
v2.1.239
Resuming a session that was in plan mode puts you back in plan mode
Both mention plan mode