Repository navigation
fix: refresh run details after durable events - #6
Merged
Merged
Conversation
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.
What
model.deltaframes from detail refetchesWhy
The live event stream updated the Activity timeline but did not refresh
GET /runs/{run_id}. A lifecycle change made by the CLI, wake worker, or another UI could therefore leave the header, composer, and control buttons on a stale Run status indefinitely because focus refetching is disabled.Impact
Run-scoped controls converge on server-authoritative status after streamed or Desktop-polled durable events. The bounded delay avoids one detail request per event burst, and high-frequency model deltas remain excluded.
Checks
npm test(56 files, 213 tests)npm run typechecknpm run check:apinpm run buildnpm audit --audit-level=moderategit diff --checkAll checks ran with Node 24.19.0. Vite retains the repository's existing large-chunk warning.