[Bug] Token usage calculation incorrect for *non-peak* hours with 2 small sessions #40845

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   area:cost

   platform:linuxIssue specifically occurs on LinuxIssue specifically occurs on Linux

   on Mar 30, 2026
2. yurukusa commented on Mar 30, 2026

   

   yurukusa

   on Mar 30, 2026

   More actions

   The 29% usage with only 90K tokens across 2 sessions suggests either:

   1. Background processes consuming tokens — check for running subagents or MCP servers:

   ps aux | grep -i claude | grep -v grep
   ls /tmp/claude-* 2>/dev/null

   2. Previous sessions still counting — the usage window may include earlier sessions from the same period:

   ls -lt ~/.claude/projects/*/sessions/*.jsonl | head -10

   3. Non-peak hours window may not be what you expect — verify your timezone and the actual peak/non-peak boundaries for your region.

   LOGFILE="$HOME/.claude/token-usage-$(date +%Y%m%d).log"
   echo "$(date +%H:%M:%S) tool_call session=${CLAUDE_SESSION_ID:-unknown}" >> "$LOGFILE"
   exit 0

   This lets you correlate actual tool calls with reported usage to identify phantom token consumption.
3. marlvinvu commented on Apr 3, 2026

   

   marlvinvu

   on Apr 3, 2026

   More actions

   My Claude says your 29% usage with only 90K tokens across 2 small sessions matches the root cause found in #40584: the client-side rate limiter multiplies estimated context tokens by the number of concurrent sessions. So 2 sessions × your context size = double the token count against your budget. This is counted CLIENT-SIDE before any API call — model: "", input_tokens: 0. The simplest workaround: run one session at a time instead of two concurrent ones. See #40584 for the full analysis with log evidence.
4. github-actions

   added

   staleIssue is inactiveIssue is inactive

   on Apr 28, 2026
5. github-actions commented on May 12, 2026

   

   github-actionsBot

   on May 12, 2026 – with GitHub Actions

   More actions

   Closing for now — inactive for too long. Please open a new issue if this is still relevant.
6. github-actions

   closed this as not plannedon May 12, 2026
7. github-actions commented on Jul 1, 2026

   

   github-actionsBot

   on Jul 1, 2026 – with GitHub Actions

   More actions

   This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
8. github-actions

   locked as resolved and limited conversation to collaborators on Jul 1, 2026