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.
tengu_rippling_orbit Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.319: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.319. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_rippling_orbit