Summary

Fixes TUI showing stale token counts (e.g., 92k) after /new session reset, when the actual count should be near 0.

Problem

After /new reset:

The 92k appears consistently after reset regardless of previous session size.

Root Cause

1. sessions.reset creates a new entry but omits inputTokens/outputTokens/totalTokens instead of explicitly setting them to 0
2. TUI doesn't clear its local sessionInfo immediately — shows cached values until refreshSessionInfo() completes

Changes

1. Backend (src/gateway/server-methods/sessions.ts)

const nextEntry: SessionEntry = {
  // ... existing fields ...
  // Reset token counts to 0 on session reset (#1523)
  inputTokens: 0,
  outputTokens: 0,
  totalTokens: 0,
};

2. TUI (src/tui/tui-command-handlers.ts)

case "new":
case "reset":
  try {
    // Clear token counts immediately to avoid stale display (#1523)
    state.sessionInfo.inputTokens = null;
    state.sessionInfo.outputTokens = null;
    state.sessionInfo.totalTokens = null;
    tui.requestRender();

    await client.resetSession(state.currentSessionKey);
    // ...

Testing

• ✅ npm run lint — 0 warnings, 0 errors
• ✅ tsc --noEmit — passes

Related

• May also help Session totalTokens and context percentage stuck at 0 #1516 (session token tracking shows 0) — similar root cause

🤖 AI-Assisted

• Tool: Claude (Opus 4.5) via Clawdbot
• Testing: Lightly tested (lint + tsc pass, no runtime test)
• Understanding: Yes — sessions.reset was creating new entries without token fields, causing fallback to stale cached values; TUI held onto old sessionInfo until async refresh completed

Fixes #1523