Playbooks · Coding tasks
Gemini CLI 0.69.0-preview.0: /stats heatmap for token use
Written November 13, 2026
/stats gains a heatmap for daily token use in the 0.69.0 preview, with standalone theme.json support and a long list of reliability fixes.
What changed
Gemini CLI 0.69.0-preview.0 is a preview release, not a stable one. It follows the 0.68 line and carries the next set of changes in preview form, so the stable release covered in the 0.68 page remains the one most people run day to day. The preview list is long and mostly made of fixes. Two changes add new surface: a heatmap view inside the stats command, and support for a standalone theme file. The rest of the list works on failures that interrupt a session, corrupt a prompt, hang a load, or lose part of a tool result.
That mix matters for how to read the release. There is no new model, no new agent mode, and no change to how Gemini CLI is installed in these notes. A person who installs the preview gets a better view of their own token use, a simpler way to carry a custom theme, and a set of repairs aimed at long or awkward sessions.
A heatmap for daily token use
The headline addition is a /stats heatmap subcommand for daily token usage. Token use is easy to lose track of in a terminal agent, because each session feels small while the total across a week can be large. A heatmap puts the daily pattern in one picture: heavy days stand out, quiet days recede, and a reader can see whether their use is steady, spiky, or climbing, without adding up session totals by hand.
The notes give the feature in a single line and do not describe its range, its colours, or how far back it looks. So the honest summary is the shape, not the detail: daily token usage, shown as a heatmap, inside the existing stats command rather than in a separate tool.
Standalone themes and a stricter /model
The second addition supports a standalone theme.json configuration for custom themes. A theme kept in its own file is easier to share, copy between machines, and keep under version control than theme settings buried inside a larger configuration. The same list also adds missing active and focus keys to the custom theme schema, which suggests the theme work in this preview is about making custom themes complete as well as portable.
Nearby, the /model command now validates model names and supports direct arguments. A mistyped name that fails early is kinder than one that fails later as a puzzling request error. The list also preserves the selected model across a transient fallback, a cancel, and a rewind, and preserves an explicit gemini-2.5-flash choice in dynamic model resolution. Together, those lines address a familiar complaint: the tool quietly ending up on a different model from the one the person picked.
The reliability list
Most of the preview is repairs, and they cluster in useful places:
- Prompts and templates. Literal
$characters survive template placeholder replacement, aGCLI_EXPAND_TARGETcollision in environment expansion is prevented, and$-patterncorruption in prompt templates is fixed. Dollar signs are common in real code and shell text, so these are correctness fixes, not polish. - Sessions that stall or break. Silent multi-minute loading hangs on network failures are prevented, terminal model-turn errors on resume are addressed, piped input now waits for its end instead of losing its stream, and a pending tool confirmation survives leaving an editor selection.
- Large and mixed tool results. Multi-part tool outputs are bounded and older inline data is evicted, multimodal tool responses keep their shape, and PDF and telemetry buffers no longer retain memory in the same way.
- Quotas and timeouts. Multi-hour quota retries are prevented and the client is told about retry attempts, and the 60-second API headers timeout can be overridden across auth modes with
model.requestTimeoutMsorGEMINI_API_HEADERS_TIMEOUT_MS. - Platform edges. Windows PowerShell substitution, folder trust before the macOS sandbox, file watcher errors, and a leaked file handle on macOS terminal sessions all get fixes, alongside headless runs that now kill child processes and keep the signal exit code on abort.
Together they describe a preview spent on where a daily terminal tool wears out: input handling, resumption, memory, and the boundary with the operating system.
What to do, and the limits
- Install the preview only if you want the heatmap or the theme file now, or if one of the listed fixes names a failure you keep hitting. It is labelled a preview for a reason, and the stable line is still 0.68.
- Try
/statson a machine with real history first. A heatmap is only useful if it covers enough of your past use to show a pattern, and the notes do not state its range. - If you maintain a custom theme, the standalone
theme.jsonroute is the change to test, along with the added active and focus keys in the schema. - Do not carry the 0.68 features forward as new here. Extension validation arrived in the 0.68 preview and reached stable in 0.68; this page covers only the 0.69 preview delta.
- The notes are one line per change, with no settings guide for the new subcommand and no stated heatmap range. Plan to explore the command rather than to configure from the release list.
Related playbooks
- Gemini CLI 0.68 preview: extension checks
- Antigravity CLI 1.5.5: swarms in preview
- Gemini CLI 0.67 lists models, fixes a timeout
- Gemini CLI 0.68 stable: extension checks
Sources
- Release v0.69.0-preview.0 — google-gemini/gemini-cli on GitHub
- Releases — google-gemini/gemini-cli on GitHub
Back to: Coding playbooks hub · Also: Gemini CLI 0.68 stable: extension checks · Gemini 4 Hydrogen is GA; there is no 4 Pro