Gemini CLI session history will not display - Gemini CLI
Quick fix
Gemini CLI 0.39.1 changed the history path. With the consumer service being retired, the old path will not be fixed — wait for Antigravity CLI support.
Symptom
Section titled “Symptom”里面会是空白It comes up blank
From version 0.39.1, Gemini CLI moved session history storage from `.gemini\history` to `\.gemini\tmp`, so CC Switch still reads the old path and history sessions and token consumption come up blank. Google has also announced the consumer Gemini CLI is migrating to Antigravity CLI, with service for free and consumer users ending 2026-06-18. CC Switch therefore decided not to fix this path change for the older Gemini CLI and to prioritise Antigravity CLI support instead.
Note the CC Switch import and sync module has had several independent problems recently: besides the Gemini history path, orphaned database records left after deleting a skill by hand (#2279), and cloud sync wrongly overwriting the local session import cursor (#6138). Each is being tracked separately or already merged into another PR.
Consumer users (free, Google AI Pro/Ultra): do not troubleshoot on the older Gemini CLI. Wait for a later CC Switch version to support Antigravity CLI (see issue #2959).
Enterprise-licensed or paid API key users: if you still need CC Switch to support history import from the older Gemini CLI, reopen the original issue on GitHub or file a new one explaining the enterprise case.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 4 real issues
- Why can I not see token consumption either?
- Token consumption data also depends on reading the session history files, and the path change makes it unavailable. With the consumer service being retired, the old reading logic is no longer maintained.
- A skill I deleted by hand is still in the client. How do I fix it?
- That is an orphaned record: the UI count reads the database without reconciling against the local source-of-truth directory. Back up `~/.cc-switch/cc-switch.db`, delete it, and restart CC Switch to clear the leftovers.
- Does cloud sync overwrite the local session import cursor?
- Yes — `session_log_sync` was wrongly included in the remote SQL payload, losing the cursor. That was merged into #6129 for a fix, so cloud sync skips it and preserves local cursor state.
Related problems
Section titled “Related problems”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.