fix(cli): clarify background Task orchestration - #13362
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by grok-4.6 · Input: 70.8K · Output: 4.9K · Cached: 154.6K Review guidance: REVIEW.md from base branch |
marius-kilocode
enabled auto-merge
August 24, 2026 11:53
WebReflection
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background Task execution already returns immediately and automatically retriggers the parent when a result arrives. The issue was ambiguous guidance that did not clearly distinguish work that can run independently from work whose result is needed before the parent proceeds.
This change makes the Task guidance generic:
The change intentionally does not alter the Task lifecycle, notification payloads, runtime finish behavior, or add a tracking registry. The investigation and public-harness comparison are documented in #13360.