You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cbb5d21
Browse filesBrowse the repository at this point in the historyBrowse files
fix(kiro): round-trip the redactedContent reasoning blob
Kiro never returns plaintext reasoning for its Sol-family models. Its
`reasoningContentEvent` carries a KMS-encrypted `redactedContent` blob, and
`gpt-5.6-sol`'s `additionalModelRequestFieldsSchema` accepts only
`reasoning.effort` — there is no display or summary opt-in. Kiro's own CLI
replays that blob on the matching `assistantResponseMessage.reasoningContent`
to preserve model reasoning across turns.
The adapter read only `reasoningContentEvent.text`, which is absent on this
wire, so the blob was dropped and never replayed. Every turn therefore
restarted without the previous turn's reasoning.
- kiro-events: parse `redactedContent`; add the previously unhandled
`contextUsageEvent` (Kiro reports context pressure there, not in
`metadataEvent`, which carries only `stopReason`).
- Carry the blob through the existing `ocxr1:` envelope as `krc` on an
envelope-only reasoning item, so it round-trips while staying invisible in
the app — the same contract the hidden-thinking path already uses.
- Pair it backwards: Kiro emits the event at the END of a turn, after content
and tool calls, so a krc-only item belongs to the assistant turn that already
closed. Folding it forward would attach turn N's blob to turn N+1. With no
assistant turn to own it, the blob is dropped rather than mis-paired.
- Replay it on `assistantResponseMessage.reasoningContent`.
Verified against kiro-cli 2.14.1 and 2.16.0 request/response captures.
0 commit comments