fix: simplify streamed answer presentation - #66
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
|
Intent: Render streamed agent text in the normal answer area and enforce the project punctuation rule in generated responses. |
This branch was successfully deployed
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.
Problem / Motivation
Streamed answers were placed inside a separate Draft box with a label and warning border. The extra treatment made the answer look like a second interface instead of text arriving in the normal response.
The response prompt also lacked the project's explicit rule against em dashes and substitute punctuation.
Why it matters
Streaming should change when text appears, not where it appears. Final answers should also follow the same punctuation rules as the rest of the product writing.
What changed
Streamed Markdown now renders in the normal answer area. The Draft label, border, and dedicated container are gone. Incoming snapshots reveal at 110 characters per second, with updates capped near 30 frames per second to avoid reparsing Markdown on every display frame. Reduced-motion users receive each snapshot immediately. The copy action still appears only after the validated answer replaces the stream.
Shared answer guidance now tells the model to end the sentence or use a comma instead of an em dash. It also rejects parentheses and en dashes as substitutes and points to
writing-style.md.Tests
Manual verification
Open the Vercel preview, start an agent run, and confirm streamed text appears as a normal answer without a Draft label or border.
Screenshots / video
Pending the Vercel preview generated by this PR. The browser regression captures
streaming-answer.pngduring CI.Issue link
no linked issue: requested as follow-up feedback after PR #64 merged.