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

Claude Code v2.1.305 ·

Workflow parallel() and pipeline() keep separate state for each item

Each item run by the workflow parallel() and pipeline() helpers now keeps its own state, which is merged back afterwards

Under the hood Internal Changes
JSON All of v2.1.305
Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
Internal ChangesKind: in v2.1.305,
Internal ChangesSection of the release

Unclear It is not clear what this changes in how workflows behave.

What

The parallel() and pipeline() helpers in workflows now run each item in its own slot. A slot is a separate space that keeps that item's state apart from the others. When the items finish, their state is merged back together. Before, items ran directly with no per-item state.

Why

This may affect the order in which workflow agents run or how their results are traced back to them.

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 doubtIt is not clear what this changes in how workflows behave.
Anthropic's release notes agreeFixed Workflow resume re-running already-completed pipeline() and parallel() agents instead of serving them from the run's journal

See this entry in the whole of v2.1.305 →

Feedback