The Gemini CLI release v0.67.0-nightly.20261030.gb633c0703 introduces a new extension validation command, according to the official release notes.reported This feature, added by contributor @tadipavan in pull request #29980, also includes evaluation tests for extensions.reported The release focuses on stabilizing the core and CLI components with numerous fixes.
The figures
The release tag is v0.67.0-nightly.20261030.gb633c0703.reported It follows the previous nightly build v0.67.0-nightly.20261028.gfa5c17365.reported The changelog lists numerous pull requests, including #29995, #29904, #29993, #29999, #29982, #29980, #29987, #29994, #29998, #29989, #30006, #30012, #30013, #30023, #30035, #29965, #30041, and #30031.
Behind the figures
The release notes detail specific code changes attributed to various contributors. For instance, @jvargassanchez-dot addressed inline history re-rendering and VS Code companion disposables. @diegogodinezr handled surrogate pairs in display sanitization and anchored .git suffix removal. @duvanka-prasad fixed case-insensitivity on Windows and prevented pattern corruption in LLM prompt templates.
What it means for your stack
Developers using the Gemini CLI on Windows will see improved reliability. The core now uses a PowerShell CIM fallback for Windows IDE process lookup, as fixed by @tadipavan. Additionally, the `isWithinRoot` check is now case-insensitive on Windows, according to @duvanka-prasad.reported These changes address platform-specific inconsistencies that could disrupt workflow.
Building on this
Inference engineers can now validate their Gemini CLI extensions using the new command introduced in this build. This allows for testing extension integrity before deployment. The fix for recognizing dotted Gemini 3 models in `supportsMultimodalFunctionResponse` ensures broader model compatibility.reported Developers working with multimodal function responses should note this expanded support for Gemini 3 model variants.reported
Why it matters
- The extension validation command provides a concrete method for developers to test their custom tools within the Gemini CLI ecosystem.
- Windows users gain stability through case-insensitive root checks and improved IDE process lookup via PowerShell CIM fallback.
- The fix for surrogate pairs in `sanitizeForDisplay` prevents display errors when handling complex Unicode characters in terminal output.
- Surface rate-limit cool-downs in the loading indicator give users better visibility into API throttling events.
Topics: Gemini CLI, Google, developer tools, Windows, extensions
Updated
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
What new feature is added to the Gemini CLI in this release?
A new extension validation command and evaluation tests are added to the CLI.
Which operating system gets specific fixes in this update?
Windows receives fixes for case-insensitive root checks and IDE process lookup.
Does this release support Gemini 3 models?
Yes, it recognizes dotted Gemini 3 models in multimodal function response support.
Connected stories
Reading receipt
- Version 0.67.0-nightly.20261030.gb633c0703 of the Gemini CLI was released.
- A new command allows developers to validate extensions and run evaluation tests.
- Fixes address Windows IDE process lookup, surrogate pair handling, and rate-limit countdowns.