Playbooks · Coding
Gemini CLI 0.68 preview: extension checks
Written November 10, 2026
Gemini CLI 0.68 is still a preview, but its headline change is already usable: a validate command that checks an extension before anyone installs it.
The problem
An extension author ships a manifest with a bad version string, an insecure setting, or a misconfigured MCP server, and the failure shows up on someone else's machine, after install, as a confusing error. The 0.68 preview adds a check that runs before that point, on the author's machine.
What the preview adds
The v0.68.0-preview.0 release includes feat(cli): add extension validation command and evaluation tests. The change behind it, pull request 29980, merged October 28, 2026, introduces a gemini extensions validate command that checks a local extension configuration before deployment. It checks three things: that the manifest is secure and correctly formatted, that version numbers follow SemVer, and that the MCP server definitions are valid.
The MCP server checks cover the transports an extension can declare — command, URL, and TCP — and flag the deprecated httpUrl property where it is still used. The same change adds a troubleshooting guide for gallery indexing, to help an author check whether an extension manifest is correctly indexed by GitHub, and evaluation tests for the validation itself.
What it does not check
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, exercise its tools, or prove that a server it points at is safe to connect to. A manifest that passes validation can still point at a server that misbehaves, and a server that is correctly configured can still be the wrong one to trust. Treat a passing check as a formatting gate before shipping, not as a verdict on the extension.
The preview label matters too. This is v0.68.0-preview.0, not a stable release: the latest stable is still 0.67.0. The command name, the checks it runs, and the output format can all change before 0.68.0 ships as stable. Do not build release tooling that depends on the exact output of a preview command.
How to use it
Install the 0.68 preview, then run gemini extensions validate against the extension directory before publishing or sharing it. Fix what it flags — a SemVer violation, a deprecated httpUrl, a malformed manifest — and re-run until it passes. If the extension is meant for the gallery, use the new troubleshooting guide to confirm the manifest is indexed correctly, rather than assuming a successful local check means the gallery picked it up.
Limits
- Preview only: v0.68.0-preview.0 is a pre-release, and the latest stable is 0.67.0. The validation command and its output can change before the stable release.
- No validation run sits behind this page: the command was not run against a real extension here, so the checks above are as described in the release notes and the merged change, not as observed.
- Validation checks configuration, not behaviour. A passing manifest says nothing about what the extension does when it runs.
Related playbooks
- Gemini CLI 0.68 stable: extension checks
- Gemini CLI 0.69.0-preview.0: /stats heatmap for token use
- A trojanized Claude Code extension stole SSH keys
- Gemini CLI 0.67 lists models, fixes a timeout
Sources
- Releases — google-gemini/gemini-cli, GitHub
- Add extension validation command and evaluation tests — Pull request 29980, google-gemini/gemini-cli
Back to: Coding playbooks hub · Also: Gemini CLI 0.67 lists models, fixes a timeout · VS Code 1.145: Agent Host keeps sessions alive