fix(web): show agent messages immediately regardless of scroll position - #228
Merged
Merged
Conversation
When the user was scrolled up from the bottom, all incoming messages (including AI responses) were queued in the pending buffer and only flushed when the user scrolled back down or sent a new message. This caused AI replies to appear delayed by N turns: each user message sent would flush one pending AI response rather than triggering a real response, creating the illusion that the AI was lagging 3 sentences behind. Fix: in ingestIncomingMessages, bypass the atBottom gate for agent messages so they are always merged into the visible window immediately. User messages from other clients remain in the pending queue to avoid disrupting scroll position during history review.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
tiann
approved these changes
Feb 27, 2026
Unintendedz
referenced
this pull request
in Unintendedz/hapii
Mar 3, 2026
SeeFlowerX
pushed a commit
to SeeFlowerX/hapi
that referenced
this pull request
Apr 1, 2026
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
2 participants
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.
When the user was scrolled up from the bottom, all incoming messages (including AI responses) were queued in the pending buffer and only flushed when the user scrolled back down or sent a new message.
This caused AI replies to appear delayed by N turns: each user message sent would flush one pending AI response rather than triggering a real response, creating the illusion that the AI was lagging 3 sentences behind.
Fix: in ingestIncomingMessages, bypass the atBottom gate for agent messages so they are always merged into the visible window immediately. User messages from other clients remain in the pending queue to avoid disrupting scroll position during history review.
#226