fix(tarko-agent-ui): prevent empty state during historical events loading#1718
Open
fix(tarko-agent-ui): prevent empty state during historical events loading#1718
Conversation
…ding - Add loadingSessionEventsAtom to track when historical events are being loaded - Create LoadingState component to show while events are loading - Update ChatPanel to show LoadingState instead of EmptyState during loading - Prevent 'Start a conversation' state from showing during session initialization
✅ Deploy Preview for tarko ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for agent-tars-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
Users see "Start a conversation" empty state when switching to existing sessions due to async loading race condition.
Root Cause
Session navigation triggers setActiveSessionAction which checks local messages, finds none, starts async getSessionEvents, but UI shows empty state before loading completes.
Solution
Added granular loading state tracking with loadingSessionEventsAtom to handle the "loading history" intermediate state.
Technical Changes
Architecture Benefits
Files Changed
Testing
Verified smooth navigation between sessions with proper loading indicators.