Skip to content
CC Switch WikiUnofficial Community Wiki

No new usage record is created — Antigravity usage statistics are missing

Quick fix

Most related issues remain unresolved. Upgrade to a cc-switch version containing the #7740 fix for Gemini streaming usage parsing and model attribution.

Symptom

Section titled “Symptom”
Error output
No new usage record is created for the successful streaming request.

Cause

Section titled “Cause”

Antigravity’s native Gemini streaming request `streamGenerateContent` can be forwarded successfully, but cc-switch does not write the corresponding usage record. The reported logs show no `[response_processor]` or `[gemini] 插入日志` entry after the stream ends.

The maintainers confirmed two defects: the streaming pre-filter only passes through events containing `usageMetadata`, while `modelVersion` appears only in the first chunk; also, `usageMetadata` token counts returned by Vertex AI may be strings, and when `as_u64()` cannot parse them, no record is visible on the statistics page. Both issues are addressed in the fix described in #7740. If the upstream stream does not pass through `usageMetadata` at all, the proxy-side behavior still needs to be confirmed.

Fix

Section titled “Fix”

  1. Upgrade cc-switch to a version containing the #7740 fix; the issue does not specify a release version.

  2. After upgrading, resend an Antigravity `streamGenerateContent` request and check for the corresponding usage log and statistics record.

Affected Versions

Section titled “Affected Versions”
ToolAntigravity
Version3.20.4（已报告受影响；修复版本未说明）
PlatformsWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”
What should I confirm after upgrading?
Capture a `streamGenerateContent` usage row again and confirm that the streaming request produced a statistics record.
What if the stream has no `usageMetadata` chunk at all?
This may happen when New API records usage for some upstreams but does not pass the usage data through. Confirm this further on the proxy side.
Section titled “Related problems”
cc-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 mergedNative Grok Build Usage Import Missing - CC Switch UsageMost related issues remain unresolved. Upgrade to v3.19.0 for automatic Grok Build usage import in official OAuth mode;1 issues mergedKimi balance query unavailableUpdate cc-switch to the latest version; the backend has automatically fixed Kimi balance recognition.2 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.