Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Finished workflow tasks can carry their progress history

When a workflow task ends, its final progress rows can now be passed on as workflow_progress and workflow_progress_omitted, behind tengu_rippling_orbit

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

Unclear Which app shows this information, and whether you can see it at all, is not clear.

What

When a task finishes, Claude Code passes its final data on to programs built on Claude Code, such as the desktop app or the SDK (the kit for building on Claude Code). That data now includes result, workflow_progress and workflow_progress_omitted. Before, only usage, resource links and hand-back details were passed on.

When a local workflow task ends, its final progress rows are stored as workflow_progress and workflow_progress_omitted. This happens only when the tengu_rippling_orbit setting is on and the script is not held back from SDK events. That setting counts as off when no value is available. The flag server returned off for this site's account and for an anonymous baseline, and no reading has been taken under this release yet.

A new setter, setDesktopWorkflowLimitWait, also appears.

Why

Tools that watch Claude Code can see how a finished workflow got to its end, not just its final summary.

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 doubtWhich app shows this information, and whether you can see it at all, is not clear.

See this entry in the whole of v2.1.319 →

Feedback