Skip to content
CC Switch WikiUnofficial Community Wiki

When current usage is 0 and weekly usage is not 0, cc-switch appears to show reversed values in Claude Code

Quick fix

This is a confirmed GLM usage-display bug. The original post said it was fixed, but no verifiable fixed version was provided.

Symptom

Section titled “Symptom”
Error output
当前用量为0，周用量不为0时，cc-switch展示的数额好像显示反了
English translation

When current usage is 0 and weekly usage is not 0, cc-switch appears to display the values in reverse.

Cause

Section titled “Cause”

Reports show that the 5-hour usage and weekly usage for the GLM Token Plan can be displayed in reverse. The issue was reported in v3.14.1; a maintainer said it was fixed in v3.15.0, but a v3.15.0 user later still reported that the weekly and 5-hour quotas were reversed. Therefore, v3.15.0 cannot be treated as a verified fixed version.

A troubleshooting comment noted that `parse_zhipu_token_tiers` infers whether two `TOKENS_LIMIT` entries correspond to five_hour or weekly_limit from the order of `nextResetTime`. When current 5-hour usage is 0% and `nextResetTime=null`, this heuristic puts it last and maps the displayed values incorrectly. The comment later said it was fixed, but provided no release version or user verification.

Fix

Section titled “Fix”

  1. The original post confirmed this as a bug and said it was fixed. Because no verifiable fixed version was provided, check later release information in the relevant issue before upgrading to verify.

  2. If the issue remains after upgrading, add the latest version, reproduction steps, and relevant logs to the source issue as requested by the maintainer.

Affected Versions

Section titled “Affected Versions”
ToolClaude Code
Version3.14.1 - 3.15.0（受影响报告）
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
Should the weekly usage be displayed here?
Related reports indicate that the weekly quota and 5-hour quota may be displayed in reverse; the original post did not provide a verifiable final release version.
When current usage is 0 and weekly usage is not 0, the 5-hour usage and weekly usage shown on the cc-switch main screen are reversed.
This has been confirmed as a bug. A troubleshooting comment linked it to the `TOKENS_LIMIT` sorting logic when `nextResetTime=null`, and said it was fixed.
Section titled “Related problems”
CC-Switch Cannot Recognize Antigravity Sessions, Token Statistics Are 0This is an unresolved feature request; no merged and verifiable solution is available yet.1 issues mergedcc-switch Usage Statistics Differ from DeepSeek Official Site / Stop UpdatingUpgrade to v3.19.2 or later, then run “Rebuild Codex Usage” once on the “Usage Statistics” page to correct historical overcounts or missing records.22 issues merged/branch sessions: parent session hard to find in Session ManagerTry claude --resume or claude -r <sessionId> as the proposed workaround. The original post provides no verifiable Session Manager fix.1 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.