{"version":"2.1.319","anchor":"task-terminal-results-now-carry-result-and-workflow-progress","canonical_anchor":"task-terminal-results-now-carry-result-and-workflow-progress","heading":"Finished workflow tasks can carry their progress history","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/task-terminal-results-now-carry-result-and-workflow-progress","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Finished workflow tasks can carry their progress history\n\nWhen a workflow task ends, its final progress rows can now be passed on as workflow_progress and workflow_progress_omitted, behind tengu_rippling_orbit\n\n**Unclear.** Which app shows this information, and whether you can see it at all, is not clear.\n\n**What**\n\nWhen 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.\n\nWhen 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.\n\nA new setter, `setDesktopWorkflowLimitWait`, also appears.\n\n**Why**\n\nTools that watch Claude Code can see how a finished workflow got to its end, not just its final summary.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}