fix(pull-requests): keep cached PR chrome on reopen by maria-rcks · Pull Request #9294 · pingdotgg/t3code

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

maria-rcks · 2026-09-03T00:30:04Z

Summary

Reopening a thread's linked pull request was painting a full-tab skeleton and asking GitHub again for title, author, and the rest. Last-known metadata now stays on screen, and a refresh only replaces fields that actually moved — especially diff counts.

A later strict summary (including auto-settle) is no longer overwritten by the stale detail snapshot served on reopen. Snapshot IO keys off the pull request identity, not the inline reference object.

Verified with focused server and web unit tests for reuse, stale-while-revalidate detail, settlement-over-stale-reopen, and snapshot hydration.

Evidence

Test plan

Open a thread whose branch already has a linked PR, wait for the PR tab to load, switch away, then reopen it — chrome (title, author, icon, counts) should stay, not a full-tab skeleton
After a later refresh, only changed fields such as +/- counts update in place
First-ever open of an unseen PR can still show the loading ghost
Sidebar linked-PR status does not re-hit GitHub for title/state on every remount

Cursor Grok 4.6 via T3 Code

Note

Medium Risk
Caching changes what clients see and when host APIs are called; incorrect staleness rules could show outdated title/state, though merged-state and updatedAt guards mitigate regression.

Overview
Reopening a linked pull request no longer flashes a full-tab skeleton or re-fetches title/state from the host when nothing meaningful changed.

Server (PullRequestService) adds serveHeld on the last-good cache: display summaries reuse held data without another host call; detail returns the held snapshot immediately and revalidates in the background. Detail refreshes only update the linked summary when shouldReplaceHeldSummary allows it (respects merged state and updatedAt) so a stale detail reopen cannot regress a fresher strict summary.

Web persists the last PullRequestDetail in localStorage (schema-validated, keyed by environment + PR identity) and resolveDisplayedPullRequestDetail prefers live data but paints the snapshot while the query is pending—ghost UI only when there is no cached or live detail.

Tests cover reuse counts, stale-while-revalidate detail, summary settlement vs stale reopen, and snapshot hydration edge cases.

^{Reviewed by Cursor Bugbot for commit 89359f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Reopening a linked pull request was painting a full-tab skeleton and asking GitHub again for title and author. Serve last-known metadata immediately and only replace fields such as diff counts when the refresh lands. Co-authored-by: Cursor <cursoragent@cursor.com>

macroscopeapp · 2026-09-03T00:40:45Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes production pull-request reads across the server and web layers: summaries are reused, details revalidate in the background, and complete validated detail snapshots are persisted to localStorage and shown during reopen. These changes materially affect host-call timing, staleness, and what users see across sessions, so the caching behavior merits human review.

Not approved because:

Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

Record last-known summary from the host read, not the stale snapshot served immediately, and key snapshot IO on the pull request identity instead of the inline reference object. Co-authored-by: Cursor <cursoragent@cursor.com>

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef4fe09. Configure here.}

A still-valid detail cache entry can be older than auto-settle. Do not copy that title and state back into last-known summary. Co-authored-by: Cursor <cursoragent@cursor.com>

@juliusmarminge

## What's Changed * chore(ci): only run check-run agents on vouched contributors by @juliusmarminge in pingdotgg/t3code#9298 * fix(web): stop remounting markdown on every activity delta by @juliusmarminge in pingdotgg/t3code#9306 * fix(pull-requests): keep cached PR chrome on reopen by @maria-rcks in pingdotgg/t3code#9294 * feat(environments): draw each environment as the machine it runs on by @juliusmarminge in pingdotgg/t3code#9299 * feat(web): apply and remove labels from the pull request tab by @juliusmarminge in pingdotgg/t3code#9313 * fix(sidebar): collapse settled and snoozed shelves by default by @maria-rcks in pingdotgg/t3code#9314 * refactor(media): unify file and media previews across clients by @juliusmarminge in pingdotgg/t3code#9253 * fix(chat): keep live tool labels in present tense by @maria-rcks in pingdotgg/t3code#9316 * chore: audit lint directives and move plugin allowlists into config by @juliusmarminge in pingdotgg/t3code#9300 * chore(ci): narrow the Effect conventions check-run agent by @juliusmarminge in pingdotgg/t3code#9321 * refactor(mobile): style plain views with Uniwind classes instead of the theme bridge by @juliusmarminge in pingdotgg/t3code#9322 * fix(dev): share dev servers on the loopback Vite actually binds by @juliusmarminge in pingdotgg/t3code#9324 * fix(web): line up the titlebar wordmark label and version pill by @tristanmanchester in pingdotgg/t3code#9255 * fix(web): make the diff layout toggle a persisted setting by @juliusmarminge in pingdotgg/t3code#9326 * chore: dedupe lightningcss and tailwind node bindings by @juliusmarminge in pingdotgg/t3code#9331 * chore: upgrade vite-plus to 0.3.0 by @juliusmarminge in pingdotgg/t3code#9327 * feat(web): add a file tree to the diff panel and pull request code tab by @juliusmarminge in pingdotgg/t3code#9330 * feat(web): add PageUp/PageDown chat navigation by @Yash-Singh1 in pingdotgg/t3code#9315 * fix(web): collapse PR header actions to icons when narrow by @maria-rcks in pingdotgg/t3code#9334 * fix(web): resolve Vite sourcemap and supports warnings by @juliusmarminge in pingdotgg/t3code#9343 * feat(web): choose whether links open in the default browser or in T3 Code by @juliusmarminge in pingdotgg/t3code#9339 * fix(web): add press feedback to buttons by @maria-rcks in pingdotgg/t3code#9349 * feat(web): add customizable project icons by @saphid in pingdotgg/t3code#9137 * fix(mobile): stop indented code overflowing Android chat bubbles by @Adamulek123 in pingdotgg/t3code#9347 * fix(web): let the pull request list use wide screens by @juliusmarminge in pingdotgg/t3code#9351 * feat: display native app and browser icons in work logs by @Yash-Singh1 in pingdotgg/t3code#9093 ## New Contributors * @tristanmanchester made their first contribution in pingdotgg/t3code#9255 **Full Changelog**: pingdotgg/t3code@v0.0.39-nightly.20260903.1262...v0.0.39-nightly.20260903.1265 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.39-nightly.20260903.1265

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Sep 3, 2026