Greptile Summary

This PR fixes the /usage slash-command in the Control UI so it displays the current context-window snapshot instead of the misleading cumulative inputTokens + outputTokens total. When no fresh snapshot is available the command now shows n/a rather than an inflated number. Two regression tests are added to cover both scenarios.

Key changes:

• slash-command-executor.ts: total is now derived from session.totalTokens only when session.totalTokensFresh !== false and the value is a finite number; otherwise falls back to null → "n/a". The context-usage percentage is updated to use the total snapshot tokens rather than just input tokens.
• slash-command-executor.node.test.ts: Existing test expectation updated (30% → 38% to match the new percentage logic); new test added for the stale/missing-snapshot path.

Issue found:

• totalTokensFresh is referenced in slash-command-executor.ts (line 306) and passed as Partial<GatewaySessionRow> in the test (line 341), but GatewaySessionRow in ui/src/ui/types.ts does not declare this field. TypeScript's excess-property checking will reject both call-sites with a compile error. The fix requires adding totalTokensFresh?: boolean to GatewaySessionRow in ui/src/ui/types.ts.

Confidence Score: 2/5

• Not safe to merge — missing type definition causes TypeScript compilation to fail.
• The fix logic is sound and the test coverage is good, but the PR is incomplete: totalTokensFresh is used in both the implementation and the tests without being added to the GatewaySessionRow type. This produces hard TypeScript compilation errors in both files and blocks the build.
• ui/src/ui/types.ts — must have totalTokensFresh?: boolean added to GatewaySessionRow before this PR can compile.

This is a comment left during a code review.
Path: ui/src/ui/chat/slash-command-executor.ts
Line: 306

Comment:
**`totalTokensFresh` missing from `GatewaySessionRow` type**

`session.totalTokensFresh` is accessed here, but `totalTokensFresh` is not declared in the `GatewaySessionRow` type in `ui/src/ui/types.ts`. TypeScript will reject this with _"Property 'totalTokensFresh' does not exist on type 'GatewaySessionRow'"_, causing compilation to fail.

The same problem surfaces in the test file at line 341, where `{ totalTokensFresh: false }` is passed as `Partial<GatewaySessionRow>` to the `row()` helper — TypeScript's excess-property check will also reject that.

`GatewaySessionRow` needs `totalTokensFresh?: boolean` added before this code can compile:

```
// ui/src/ui/types.ts  (GatewaySessionRow)
  inputTokens?: number;
  outputTokens?: number;
  totalTokens?: number;
+ totalTokensFresh?: boolean;
  model?: string;
  modelProvider?: string;
  contextTokens?: number;
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: 5800b59}

Follow-up complete on this branch:

• rebuilt from upstream/main and cherry-picked f159d4770cc9a73a783345019c0fdc1358480ee8 + 592312a5c0373b7155f65d23b80fe625ee25bc09
• kept /usage total on cumulative input + output tokens while still using totalTokens only for the fresh context snapshot percentage
• added a regression test covering the case where cumulative usage differs from the context snapshot
• verification: NODE_OPTIONS='--max-old-space-size=8192' npx tsc --noEmit

Closing this as implemented after Codex review.

Current main already implements the requested Control UI /usage behavior: it keeps the total line cumulative, uses the current context snapshot only for the context percentage, handles stale snapshots via totalTokensFresh, and has regression tests covering the reported mismatch. This PR is superseded by the implementation already on main and by later closed replacements referenced in the PR timeline.

What I checked:

• Current /usage logic matches requested behavior: executeUsage now computes cumulative total from inputTokens + outputTokens, computes the context percentage from totalTokens only when totalTokensFresh !== false, and hides the context line when the snapshot is stale. (ui/src/ui/chat/slash-command-executor.ts:380, 151befb90b90)
• Regression tests cover fresh, stale, and differing snapshot cases: Tests assert 38% for a fresh snapshot, ~1.5k with no context line for stale snapshots, and 31% context while preserving 1.5k cumulative total when snapshot and cumulative usage differ. (ui/src/ui/chat/slash-command-executor.node.test.ts:490, 151befb90b90)
• Earlier PR review blocker is already resolved on main: GatewaySessionRow now includes totalTokensFresh?: boolean, so the type error noted in PR review no longer applies. (ui/src/ui/types.ts:433, 151befb90b90)
• Core contract distinguishes context snapshot from cumulative usage: deriveSessionTotalTokens documents that totalTokens is a prompt/context snapshot and intentionally excludes completion/output tokens, which is exactly why current main uses it for context percentage but not for the total line. (src/agents/usage.ts:242, 151befb90b90)
• Session freshness contract supports the UI behavior: resolveFreshSessionTotalTokens drops stale totals when totalTokensFresh === false, and session usage persistence comments say lastCallUsage is stored so context-window utilization reflects the current context rather than accumulated run totals. (src/config/sessions/types.ts:426, 151befb90b90)
• PR timeline already points to later closed replacements: The timeline cross-references closed PRs #71297 (Fix Control UI context freshness and compaction CTA) and #71462 (fix(ui): use current context usage in Control UI), which is consistent with this PR being superseded by work already present on main.

So I’m closing this as already implemented rather than keeping a duplicate issue open.

Review notes: reviewed against 151befb90b90.