Skip to content

Native Grok Build Usage Import Missing - CC Switch Usage

Quick fix

Most related issues remain unresolved. Upgrade to v3.19.0 for automatic Grok Build usage import in official OAuth mode;

Error output
Grok Build 没有任何原生用量通道
English translation

Grok Build has no native usage channel.

The report noted that in CC Switch 3.16.4, the Usage native session importer and app filter did not cover Grok Build. Users could only use an external script to write to the CC Switch database, then view usage under “All”. The maintainer confirmed that v3.19.0 adds automatic usage reading from `~/.grok/sessions` (including archives) `updates.jsonl` for official OAuth mode, per-turn ID deduplication, debouncing to prevent duplicate counting with proxy records, and a Grok Build filter in the Usage panel. It also fixes duplicate cache cost calculation during Grok Build cost backfilling.

The pricing request in this issue remains unresolved: built-in pricing for `grok-composer-2.5-fast`, especially the `cache_read` unit price, has not been added. Marking prices as estimates and recalculating historical costs after price changes remain feature requests to track.

  1. Upgrade CC Switch to v3.19.0, then verify that Grok Build usage in official OAuth mode is automatically shown as “Grok Build (Session)”.

  2. For `grok-composer-2.5-fast`, manually maintain pricing in Usage pricing settings for now. The original post provides no verifiable solution for an “estimate” label or one-click historical cost recalculation.

ToolCC Switch Usage
Versionv3.19.0(已修复原生导入)
PlatformsWindows
Will Grok Build usage receive native support, or are community external import solutions accepted?
The maintainer stated that v3.19.0 supports automatic usage import in official OAuth mode; the external Python script was the reporter’s personal workaround.
How should Usage display data when the official Composer cache_read unit price is not published?
The original post treats this as a feature request for discussion; `grok-composer-2.5-fast` still requires manual maintenance in Usage pricing settings.
Can historical costs be recalculated by data_source with one click after a price change?
Not yet implemented; the maintainer said this feature suggestion would continue to be tracked.

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.