fix(web): stop usage summary requests reporting slow RPCs by juliusmarminge · Pull Request #9358 · pingdotgg/t3code

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

juliusmarminge · 2026-09-03T05:56:32Z

What Changed

Usage summary RPC requests are now excluded from slow RPC acknowledgment tracking, matching the existing behavior for other intentionally untracked request types.

Added a focused test covering serverGetUsageSummary so it does not appear in getSlowRpcAckRequests() after the slow acknowledgment threshold passes.

Why

Usage summary requests can run in the background and should not surface as slow RPC warnings in the web client. Treating them as latency-tracked requests creates noisy slow request state without giving users or maintainers useful signal.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Narrows slow-RPC tracking for one WS method only; behavior matches other intentionally untracked RPCs with no auth or data-path changes.

Overview
Usage summary RPCs are no longer tracked for slow acknowledgment warnings, alongside existing exclusions like preview automation connect.

serverGetUsageSummary is added to untrackedRpcAckMethods in requestLatencyState.ts, so background usage fetches that exceed the 15s threshold will not populate slow RPC UI state. A unit test asserts getSlowRpcAckRequests() stays empty after the threshold when that method is tracked.

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

Note

Exclude `usage-summary` RPC from slow request ack tracking

Adds the server usage-summary RPC method to the set of methods whose acknowledgements are not tracked for slow-request reporting, so getSlowRpcAckRequests no longer returns them. Adds a test in requestLatencyState.test.ts confirming usage-summary requests stay excluded even after twice the slow-ack threshold elapses.

^{Macroscope summarized 08b7806.}

github-actions · 2026-09-03T05:59:20Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.6 KiB	−170 B (−1.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−6 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.6 KiB	−164 B (−2.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	57.1 KiB	−1.4 KiB (−2.4%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.8 KiB	+166 B (+1.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+4 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.7 KiB	+162 B (+2.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	59.3 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: 08b7806 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

fix(web): stop usage summary requests reporting slow RPCs
08b7806

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

juliusmarminge merged commit 9f9359b into mainSep 3, 2026
22 checks passed

juliusmarminge deleted the t3code/disable-usage-summary-latency branch September 3, 2026 05:59

berghtho mentioned this pull request Sep 3, 2026
chore(upstream): sync 2026-09-03 berghtho/t3code#23
Merged