claude-code - 💡(How to fix) Fix Phantom ~22K tokens per session on one account vs another — same machine, same project [1 comments, 2 participants]

TL;DR

Investigate account-specific settings or claude.ai backend differences to address the ~22K token discrepancy between Login #1 and Login #2.

Guidance

• Verify that all account settings, including those not explicitly mentioned, are identical for both logins to rule out any overlooked configuration differences.
• Check with claude.ai support to see if there are any known issues or differences in how tokens are calculated or billed for different accounts, especially considering the "Max subscription" status.
• Attempt to replicate the issue on a different machine or environment to determine if the problem is specific to the WSL2 Linux setup or if it's account-related.
• Review the documentation for Claude Code and claude.ai to ensure that all features and settings are fully understood, particularly those related to token usage and billing.

Example

No specific code snippet can be provided without more details on the API or the exact implementation of the Claude Code and claude.ai integration. However, any debugging efforts should focus on comparing the API requests and responses for both logins to identify any differences that could explain the token discrepancy.

Notes

The issue seems to be related to the difference in how tokens are billed or calculated for the two logins, rather than a problem with the Claude Code or WSL2 setup itself. The fact that disabling certain features and connectors did not resolve the issue suggests that the root cause might be related to the accounts or the claude.ai backend.

Recommendation

Apply workaround: Since the exact cause is not clear and seems related to account-specific settings or backend differences, the best immediate action might be to use Login #2 (new account) for critical tasks to avoid the extra token consumption, while continuing to investigate the root cause with claude.ai support.