Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.292 ·

Workflows that withhold their script from SDK events resume with the unedited script

Workflow runs with withholdScriptFromSdkEvents now record the script's hash, offer resuming only with the unedited script, and are refused for v2 runs

Group of 2 You'll notice No documentation found Internal Changes
JSON All of v2.1.292
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
Internal ChangesKind: in v2.1.292,
What probably matters to youSection of the release

What

A workflow is a scripted multi-step run. The withholdScriptFromSdkEvents setting keeps a workflow's script out of the events sent to programs built on the SDK. Its handling changed.

  • Starting a v2 workflow run with withholdScriptFromSdkEvents set now fails with "A workflow v2 run cannot withhold its script".
  • When the script is withheld, its sha256 hash (a fingerprint of the file) is stored for each run id.
  • The v1 runner gets a withholdScript option, replacing indexLabelsForUnlabelledAgents, which was set from the same value before.
  • With the setting on, workflow notifications say "To resume with the unedited script" and drop the hint about re-running with edits. Before, they always said "To resume after editing the script". Adopted workflows carry the setting.

Why

When a script is hidden from SDK events, the program watching cannot see or edit it, so resuming is offered only with the original script. Hosts that set this on a v2 run will now get an error.

Read from
Names in the bundlewithholdScriptFromSdkEvents

See this entry in the whole of v2.1.292 →

Feedback