Repository navigation
fix(dashboard): Refresh the details panel when conversation detail changes - #2667
Merged
Merged
Conversation
…anges Co-Authored-By: Thomas Jiang <20501235+thomasjiangcy@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
thomasjiangcy
approved these changes
Nov 4, 2026
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
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.
Follow-up to #2655.
The details panel fell behind the transcript. Subagents stayed "running" after the transcript showed them Completed, and new Review items took a long time to reach "Needs you". Only the detail report polls. The panel's child agents, Watches, memories, and Review items load from their own endpoints and refreshed only on remount or window focus.
Now, when a detail poll returns a new ETag, the detail
queryFninvalidates those reads. Only mounted reads refetch, so a closed panel adds no requests. Since #2655, unchanged polls are 304s, so the panel refetches only when the Conversation changed. The new ETag comes after the data the panel reads:recordSubagentEndedwritessubagent_endedafter the invocation is terminal, and Review items and Watches exist before their tool result events are written.The panel query keys now come from one
conversationSideReadQueryKeyhelper, so the refresh list and the hooks cannot drift. The archive mutation moved toconversationArchive.tswith no change, becausequeries.tswent over the 1,000-line limit.via @thomasjiangcy.
--
View Session [Sentry]