fix(chat): render blocked reason after prose#320
Merged
Conversation
cniska
changed the title
cniska
force-pushed
the
blocked-reason-render
branch
from
July 16, 2026 15:52
ff6ed70 to
8f37a4a
Compare
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
1 participant
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.
Motivation
A
signal_blockedturn delivers its reason via the signal argument, not as streamed prose. The client rendered the reason as a fallback bubble only when no prose had streamed — so any narration suppressed it, and a correct block showed as an empty-looking turn (tool rows + "Worked", nothing else).Summary
outputStreamedon the reply so the client knows whetheroutputalready reached the screen as deltasoutputStreamed, replacing the "any prose streamed" row-count proxy that misread narration as the answerbun run dogfoodso the client log is captured while dogfooding