Repository navigation
fix(kiro): preserve opaque reasoning activity through stream translation - #16121
Merged
diegosouzapw merged 1 commit intoOct 10, 2026
Merged
Conversation
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
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.
Kiro can send native
reasoningContentEventframes containing an opaque signature before any text. The executor previously consumed those frames without forwarding a progress signal, so the downstream content-stall watchdog could abort an active reasoning stream.Preserve that activity as an empty
reasoning_contentdelta only for native reasoning events with a nonblank signature. The signature is never exposed or counted as generated content. Existing text extraction is moved to a small helper; metadata, empty/unknown signatures, timeout limits, cancellation, EOF policy and account health keep their existing behavior.Validation:
The reproduction uses synthetic AWS frames through the real executor/readiness/pipe path with mocked fetch and isolated storage. It does not certify a live Kiro account, HTTP/chatCore/combo/cooldown, or native terminal proof. A separate configurable content-stall timeout remains an optional issue follow-up outside this patch.
Refs #15260. Keep the issue open for merge and the remaining scope disposition.