Fix: Improve real-time rendering of streaming messages #17
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.
This Pull Request addresses an issue where messages were rendered incorrectly when receiving a streaming response from the Gemini CLI. Previously, each data chunk of the response was incorrectly displayed as a new message with its own timestamp.
This update ensures that streaming responses are smoothly and correctly appended to a single message through the following changes:
gemini-responseevent handler to append subsequent data chunks to the last message instead of creating new ones.