Repository navigation
Show cache reuse and sample coverage in session performance - #4413
Yuxin-Qiao wants to merge 1 commit into
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex review: needs real behavior proof before merge. What this changesThis PR moves cache reuse into the primary session metrics and displays first-token and cache sample coverage beside their measurements. Example: A Codex session has three timed turns, each with 0.8-second first-token latency and 80% cached input.
Review scores
ProductKind: Preference · Worth it: Yes · Fix scope: Complete Merge readiness⛔ Blocked before merge - 1 item remains Keep open: this PR implements the maintainer-requested presentation change, and no definite functional or security defect was found. Priority: P3 Before merge
FindingsNone. Tests
Agent review detailsHow this fits togetherUsage & Spend receives filtered native Codex turn summaries and renders session measurements beneath the existing cost-ranked session headers. flowchart TD
A[Native Codex turn observations] --> B[Existing range and day filters]
B --> C[Session performance summary]
C --> D[Primary metric strip]
C --> E[Expandable performance details]
D --> F[Session row]
E --> F
Technical reviewBest possible solution: Expose the existing measurements and coverage in the session view while preserving their calculation, filtering, and billing contracts. Do we have a high-confidence way to reproduce the issue? This is an approved presentation improvement rather than a reported defect; current-main source confirms the existing placement of cache reuse and coverage. Is this the best way to solve the issue? The narrow move reuses existing summaries, translations, and layouts, removes the replaced cache detail, and avoids the scoring layer the maintainer declined. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 6e118bdb5782. Provenance checked
TestingProof path: in-process harness. SecurityNone. EvidenceWhat I checked:
Likely related people:
Review metrics
LabelsLabel changes:
Label justifications:
Rank-up movesOptional improvements that raise the rating; they are not merge blockers.
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed October 10, 2026, 12:10 PM ET / 16:10 UTC. |
Session rows currently hide cached-input reuse inside Performance details and first-token coverage in a tooltip. Move cached-input reuse into the existing primary metric strip and show first-token and cache sample counts beside their measurements, following the requested session-performance scope.
The change reuses the existing summaries, selected-range/day filters, translations and responsive layouts. Missing cache records remain unavailable, while measured zero cache reuse displays 0%. Existing median first-token latency, turn duration, whole-turn output, timed-turn count and model/effort details retain their current calculations. Cache reuse is shown once. The patch is limited to the existing view and its regression tests; it adds no scoring or aggregation layer.
Validation:
make check: passed, zero lint violations.make test-fast FILTER='SpendSessionPerformanceTests|CostUsageTurnPerformanceTests|CostUsageTurnPerformanceDetailsTests': 31 tests passed../Scripts/test.sh --direct-workers 2: all 1,654 discovered selections included in 150 groups; every group passed on the first attempt, with zero retries or timeouts. Execution: 605.4 seconds.Synthetic native component previews for source commit
864db64a7: the fixture includes the session rows, the existing privacy variant and unchanged detail components. These are not installed-app screenshots or real-account/frame-rate evidence. Evidence manifest.