Gemini CLI v0.69.0 adds a /stats token-usage heatmap and a batch of fixes
Google's Gemini CLI 0.69.0 adds a /stats heatmap of daily token usage, along with many bug fixes for the CLI, core and VS Code extension.
Google's Gemini CLI 0.69.0 adds a /stats subcommand that shows daily token usage as a heatmap. The release also includes a standalone theme.json file for custom themes and a long list of bug fixes. The release notes on the project's GitHub page list the changes as pull requests.
The /stats heatmap comes from pull request #30135, titled "feat(cli): add /stats heatmap subcommand for daily token usage." The release page gives only that title. It does not explain how the heatmap is drawn, what period it covers, or whether input and output tokens are counted together. The release also adds support for a standalone theme.json configuration, described in similar terms. It does not say where the file must live, apart from a check on the home directory that a later pull request fixed.
Users can now pass a model name directly on the command line, according to pull request #30137. The same change adds validation, so model names are checked. The release page does not say what error a rejected name produces.
The most specific change is the timeout override. Pull request #30183 lets users override the API headers timeout, which defaults to 60 seconds. The override works through either the model.requestTimeoutMs setting or the GEMINI_API_HEADERS_TIMEOUT_MS environment variable, across all auth modes. The release page gives no measured figures for how often the 60-second limit was hit.
A group of fixes targets headless use, where the CLI runs from scripts instead of an interactive terminal. Pull request #30163 changes piped input so the CLI waits for end-of-file on stdin and no longer destroys process.stdin. Pull request #30204 kills child processes, records cancelled tools, and preserves the signal exit code when a headless run is aborted.
Two pull requests address memory handling. Pull request #30180 bounds multi-part tool outputs and evicts older multimodal inlineData. Pull request #30217 deals with PDF inlineData and telemetry buffers that were kept in memory. Inline data is binary content, such as images or PDFs, embedded directly in a request rather than referenced by file. Holding onto older copies of it can make memory use grow. The release page does not give sizes or limits for either change.
Several other fixes address specific areas. Pull request #30214 recognizes TortoiseGitPlink as a PuTTY-family SSH client. Pull request #30211 limits read-many-files so it inlines only the binary assets a user explicitly requested. Pull request #30184 closes an orphan /dev/ptmx master file descriptor that leaked on macOS during pseudo-terminal spawn. Pull request #30189 makes MessageBus.request() reject immediately when publish fails.
Several entries change sandboxing and trust behavior. Pull request #30164 resolves folder trust before the CLI enters the macOS Seatbelt sandbox. Pull request #30143 permits FSEvents in the macOS permissive sandbox while handling file watcher errors. On Windows, pull request #30110 addresses PowerShell substitution false positives and policy handling.
What changed
Gemini CLI v0.69.0 adds a /stats subcommand that shows daily token usage as a heatmap, plus a standalone theme.json configuration and command-line model names.
Type: New capability · Applies to: Gemini CLI v0.69.0, /stats
Why it matters
Teams that run Gemini CLI in scripts or headless pipelines get fixes for stdin handling, aborts and hangs on network failures. The configurable timeout also matters for slow or unreliable connections.
What you can do
If you run Gemini CLI in automated or headless jobs, check the stdin and abort fixes before upgrading to v0.69.0.
Original source
Where we saw it
Gemini CLI releases
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works