Skip to content

fix: refresh run details after durable events - #6

Merged
pppolf merged 1 commit into
mainfrom
agent/refresh-run-details-on-events
Aug 12, 2026
Merged

pppolf merged 1 commit into
mainfrom
agent/refresh-run-details-on-events

Conversation

@pppolf

@pppolf pppolf commented Aug 12, 2026

Copy link
Copy Markdown
Member

What

  • refresh the exact authoritative Run detail query after durable Run events
  • coalesce event bursts and exclude transient model.delta frames from detail refetches
  • add focused hook coverage for refresh, burst coalescing, and delta exclusion

Why

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 typecheck
  • npm run check:api
  • npm run build
  • npm audit --audit-level=moderate
  • git diff --check

All checks ran with Node 24.19.0. Vite retains the repository's existing large-chunk warning.

@pppolf
pppolf marked this pull request as ready for review August 12, 2026 10:19
@pppolf
pppolf merged commit d67e31f into main Aug 12, 2026
4 checks passed
@NanaseInori
NanaseInori deleted the agent/refresh-run-details-on-events branch September 16, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant