Phantom ~22K tokens per session on one account vs another — same machine, same project

Two Claude Code Max subscriptions on the same machine (WSL2 Linux), same project, same settings, same CC version. The only difference: which claude.ai account is logged in.

What happens

On every prompt (even simple 1+1), Login #1 (old account) consumes ~22K more tokens than Login #2 (new account). This is visible in the status bar (real API billing), not just /context.

The extra tokens do not appear in any /context category — they're invisible. All categories sum correctly on Login #2 but leave a ~22K gap on Login #1.

| | Login #1 (old) | Login #2 (new) |
|---|---|---|
| Status bar (simple 1+1) | higher | lower |
| /context header | ~78.9K | ~56.2K |
| /context category sum | ~56.2K | ~56.2K |
| Phantom gap | ~22K unaccounted | ~0 |

Categories sum to ~56.2K on both logins — but Login #1's header reports ~78.9K. The ~22K difference is invisible in the breakdown.

Screenshots

/context side-by-side + simple prompt test:

<img width="2359" height="1017" alt="Image" src="https://github.com/user-attachments/assets/3ae2a9ff-f4ec-4a8c-a3c7-b79af07bac1c" />

Settings comparison (identical on both) + math test:

!Image

What we ruled out

| Hypothesis | Test | Result |
|---|---|---|
| claude.ai MCP connectors (Asana 47 tools, Gmail, Calendar, n8n) | Disabled all on Login #1 | Gap stayed |
| claude.ai Memory | Disabled + cleared on both | No change |
| Grove / "Help improve Claude" | Checked — identical on both | Not the cause |
| CC local settings | Diffed — identical | Not the cause |
| JSONL user content | Compared — identical payload | Not the cause |
| Deferred tool schemas | Same hash, same 196 tools, 71 skills | Not the cause |

Environment

• Claude Code v2.1.97, Linux (WSL2), same machine
• 12 project MCP servers (identical config on both logins)
• Login #1 additionally has 4 claude.ai connectors (but disabling them didn't close the gap)
• Both accounts: Max subscription, claude.ai Memory OFF

Impact

~22K phantom tokens per session = ~2% of 1M context window consumed by something invisible and uncontrollable. On long sessions with many turns, the cumulative overhead grows. Users have no way to see what these tokens are or reduce them.