Playbooks · Coding
Gemini CLI 0.68 stable: extension checks
Written November 11, 2026
Gemini CLI 0.68.0 shipped as a stable release on November 10, 2026. The headline is the extension validation command from the preview, now stable — plus smoother Windows paths, rate-limit countdowns, and rootless Podman sandboxing.
The problem
An extension author waiting for 0.68 to ship could use the validation command only as a preview feature: the command name, the checks, and the output could all change before the stable release. The stable release settles that. The rest of the release is smaller fixes that remove daily friction — waiting on a rate limit with no countdown, and sandboxing that needed root.
What the stable release adds
The v0.68.0 release notes carry the extension validation command into stable: feat(cli): add extension validation command and evaluation tests. Running gemini extensions validate checks a local extension before anyone installs it — that the manifest is secure and correctly formatted, that version numbers follow SemVer, and that the MCP server definitions are valid, covering command, URL, and TCP transports and flagging the deprecated httpUrl property. The same change adds evaluation tests for the validation itself and a troubleshooting guide for gallery indexing. The preview page for this release covers the validation command in detail.
The stable release also ships:
- Rate-limit countdowns. When the CLI hits a 429 rate limit, the loading indicator now shows the cool-down and a countdown, instead of leaving you waiting with no sense of how long the wait is.
- Rootless Podman sandboxing. The sandbox passes
--userns=keep-idfor rootless Podman, so sandboxed runs work without root. - Smoother Windows paths. Path handling is now case-insensitive on Windows where it needs to be, the IDE process lookup falls back to PowerShell CIM, and Windows file-stat reporting is fixed — the class of small path bugs that made Windows sessions behave differently from macOS and Linux.
- Smaller fixes. Serialized concurrent extension installs with a per-extension lock, stream failures during extension release downloads are handled, and interrupted Whisper model downloads are no longer treated as installed.
The preview, v0.68.0-preview.0, shipped November 4. The stable release is the same 0.68.0 line, six days later.
What to do
Update to 0.68.0 and run gemini extensions validate against any extension before publishing or sharing it, the same way the preview asked — only now the command is stable, so release tooling can depend on it. If you run Gemini CLI in a Podman sandbox, the rootless setup now works without extra flags. And if a rate limit hits, the loading indicator tells you how long the cool-down lasts instead of leaving you guessing.
Limits
- This page covers the stable 0.68.0 release. The validation command itself is covered in detail on the preview page; this page does not repeat that detail.
- Validation is a configuration check, not a security audit. It confirms the manifest is well-formed, the versions parse, and the MCP server settings are valid — it does not run the extension or prove that a server it points at is safe.
- Nothing here was run by us: the CLI was not updated and the validation command was not run against a real extension for this page. The claims are the release notes', as published.
Related playbooks
- Gemini CLI 0.68 preview: extension checks
- Gemini CLI 0.67 lists models, fixes a timeout
- Gemini CLI 0.69.0-preview.0: /stats heatmap for token use
- Antigravity CLI 1.5.3: subagent models, sandbox fix
Sources
- Release v0.68.0 — google-gemini/gemini-cli, GitHub
- Gemini CLI Release Notes: Latest v0.68.0 — Havoptic
Back to: Coding playbooks hub · Also: Gemini CLI 0.68 preview: extension checks · Gemini CLI 0.67 lists models, fixes a timeout · Antigravity CLI 1.5.5: swarms in preview