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.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Second-generation local workflow runs cannot be paused, only stopped

You'll notice
Useful3 Signal3
Workflows

Pausing a workflow on the newer local runtime stops it outright instead of parking it for resume.

What

A locally running workflow can now be backed by a newer runtime, and pausing one of those stops it outright: the task moves to killed and the run is terminated, rather than parking in a paused state you can resume.

Details
  • Only applies to tasks that carry a handle to the newer runtime; older runs pause as before.
  • The resume telemetry event task_local_workflow_resume is emitted only for older-runtime runs.
  • What turns the newer runtime on is not set anywhere visible in this build.
Evidence

task_local_workflow_resume

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.239 →