[Bug] Resumed conversations incorrectly recount context tokens as new usage

Bug Description
I am being charged repeatedly for tokens that I have already paid for. When I shut down my terminal and later resume conversations, the context usage of those conversations is getting counted as NEW token usage.

Example: I close my terminal for the day after a single
coding session with Opus 4.6-1m. At close, the session was at 750k tokens of my 1,000k window. The next morning, I start my computer, open my terminal, and resume yesterday's session. The bug is that yesterday's 750k-token context is counted AGAIN, as if it were 750k tokens of brand new compute — when it is just yesterday's session context being reloaded into the Claude Code CLI from local storage.

Summary: I spend a cumulative 750k tokens on day 1, close my terminal, resume that conversation from local storage on day 2, and day 2's consumption is immediately billed for 750k tokens. My weekly consumption jumps to 1.5m tokens — I'm being charged for my daily consumption plus my CUMULATIVE CONSUMPTION.

Environment Info

• Platform: linux
• Terminal: xterm-256color
• Version: 2.1.70
• Feedback ID: dd157abe-cb0c-4815-b323-2379e1b7dc51

Errors

[{"error":"Error: spawn /data/data/com.termux/files/usr/lib/node_modules/@anthropic-ai/claude-code/vendor/ripgrep/arm64-android/rg ENOENT\n    at ChildProcess._handle.onexit (node:internal/child_process:286:19)\n    at onErrorNT (node:internal/child_process:507:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)","timestamp":"2026-04-10T02:29:40.484Z"}]