A real run, start to finish
One report from our own queue, from sentence to merged fix.
Reported
Aug 3, 2026“When i tap the Approve button up top, it 'flashes' and remains there, the Status in the Details. The In Progress in the sidenav increments +1 but the Inbox doesn't increment -1 and the status/progress of this item don't update on the page”
Triaged
Approve button fails to update item status/counts on activity detail page
Root cause
RunLogAction.tsx (the Approve button on the activity detail page) called router.refresh() after a successful approve, but RunDetailLive.tsx renders its status/counts from an SWR cache (/api/v1/dashboard/runs/[id]) with fallbackData, not from the server-rendered props. router.refresh() re-runs the RSC tree — which is why the sidebar's In Progress count (a server-rendered prop) updated — but it never revalidates the SWR cache the detail page's own status/action actually reads from, so the button flashed and reverted and the item's status/Inbox count stayed stale.
Fix
src/app/[owner]/[repo]/activity/[id]/RunLogAction.tsx: added mutate(/api/v1/dashboard/runs/${id}) (from useSWRConfig, the same pattern already used by PreviewPanel in RunDetailLive.tsx) alongside the existing router.refresh(), so both the SWR-backed page content and the server-rendered sidebar update together.
Verified
1m 14sTypecheck, lint and 624 tests passed before the pull request opened.
Diff
…/[id]/RunLogAction.tsxsrc/app/[owner]/[repo]/activity/[id]/RunLogAction.tsx+11−2@@ -17,6 +17,7 @@ import type { RunDetailItem } from "./types";*/export function RunLogAction({ id, state }: { id: string; state: ItemActionState }) {const router = useRouter();+ const { mutate } = useSWRConfig();const [busy, setBusy] = useState(false);const [error, setError] = useState(false);@@ -25,8 +26,16 @@ export function RunLogAction({ id, state }: { id: string; state: ItemActionStatesetError(false);const res = await approveItem(id);setBusy(false);- if (res.ok) router.refresh();- else setError(true);+ if (res.ok) {+ // The page's live status/counts render from the SWR cache for this run+ // (see RunDetailLive), not from the server-rendered tree — router.refresh()+ // alone re-runs the RSC but never touches that cache, so the button+ // "flashed" and reverted while the sidebar (which reads elsewhere) moved.+ mutate(`/api/v1/dashboard/runs/${id}`);+ router.refresh();+ } else {+ setError(true);+ }}return <ItemAction state={state} size="sm" approving={busy} errored={error} onApprove={approve} noActionFallback="none" />;
Merged
Aug 3, 2026Reviewed and merged as the agent wrote it, with no follow-up commits.
fdbck’s repository is private, so pull request #55 is reproduced here: description and diff exactly as the agent wrote them.
How it got there
The fix was written by a coding agent running on our own machine, with our own credentials, in an isolated worktree. fdbck stores no model keys. How the worker works