Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Plan-mode gate for artifact verify/upload consent is a hardcoded constant, not yet a real toggle

A new always-on constant currently broadens when artifact verify/upload/comment actions require live confirmation during plan mode

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaArtifactswhat it touches
KindInternal Changesin v2.1.265,
Group of 3 Under the hood

A new always-on constant currently broadens when artifact verify/upload/comment actions require live confirmation during plan mode

What

  • A new module-level constant (Cdn, currently hardcoded to true) is now combined with plan-mode checks to broaden when certain artifact actions — like verify and upload_asset — require per-action confirmation rather than being covered by a session-wide approval. This matters because plan mode can admit third-party text into the conversation.
  • The helper AA(e) that makes this decision resolves to Cdn && ue(e).mode === "plan", and is used together with another helper (Au()) throughout the new artifact consent code, including deciding whether comments or reads need a live confirmation prompt.
  • A sibling helper, vU, resolves to (e.ask && e.basis === "unattended") || (EDe && ue(t).mode === "plan"), where EDe is a second constant currently set to true, gating a related plan-mode branch.

Why Both gating constants are hardcoded on rather than driven by a real setting, so today this behavior is effectively always active in plan mode: artifact verify/upload/comment/read actions get an explicit confirmation prompt rather than relying on a broader session approval, since plan mode can bring in untrusted third-party text.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtthe finding doesn't fully specify which plan-mode scenarios are newly covered, only that the gating was broadened

See this entry in the whole of v2.1.265 →

Feedback