Product case study · November 5, 2026
Gemini CLI Extensions: Review Before You Install
Inspect a Gemini CLI extension with a synthetic local fixture, find a missing MCP server, and write an evidence-based install or hold decision.

Review the extension's files and executable entry points before deciding whether to install it.
A useful-looking extension can bring more than a prompt into your agent session. Gemini CLI extensions can package context, MCP servers, commands and hooks. Before adding one, make a small inventory of what it will load and what you still need to inspect. Official extension overview
This exercise ends with an installation decision backed by file paths. You will inspect an authored package with a deliberately missing server file. You will not install it, start its server or need an API key.
Sources checked November 5, 2026. This is a documentation-backed tutorial. The Bash fixture and Python inventory were tested locally. Gemini CLI is not installed in the authoring environment; installation, activation and authenticated model behavior were not tested. The expected review below is an answer key, not a captured agent response.
Make a package you can inspect without running it
You need Bash, Python 3 and a plain-text editor. Use Linux, macOS or a Linux shell in WSL. Keep the same terminal open throughout these steps.
Create a fresh directory outside your working repositories:
extension_lab=$(mktemp -d "${TMPDIR:-/tmp}/gemini-extension-review.XXXXXX")
cd "$extension_lab"
mkdir review-fixture
cat > review-fixture/gemini-extension.json <<'JSON'
{
"name": "review-fixture",
"version": "0.0.1",
"contextFileName": "GEMINI.md",
"mcpServers": {
"review-helper": {
"command": "node",
"args": ["${extensionPath}/server.js"]
}
}
}
JSON
cat > review-fixture/GEMINI.md <<'CONTEXT'
This is a synthetic extension review exercise.
When reviewing a release, distinguish supplied evidence from missing checks.
Never describe a test as passed without a recorded result.
CONTEXT
The extension reference documents the root manifest, context file and MCP configuration. Here, review-helper declares a Node program at server.js. We deliberately did not create that file. Valid JSON alone cannot tell you whether the package is complete or appropriate for your task.
Read the inventory and follow each executable path
Run this from the lab directory:
python3 - <<'PY'
import json
from pathlib import Path
root = Path("review-fixture").resolve()
manifest = json.loads((root / "gemini-extension.json").read_text())
print("Package:", manifest["name"], manifest["version"])
print("Files:")
for path in sorted(root.rglob("*")):
if path.is_file():
print(" -", path.relative_to(root))
context = root / manifest.get("contextFileName", "GEMINI.md")
print("Context present:", context.is_file())
for name, server in manifest.get("mcpServers", {}).items():
print("Server:", name)
print("Executable:", server.get("command", "not declared"))
for argument in server.get("args", []):
print("Argument:", argument)
if argument.startswith("${extensionPath}/"):
target = root / argument.removeprefix("${extensionPath}/")
print("Referenced file present:", target.is_file())
PY
The expected findings are review-fixture 0.0.1, two files, Context present: True, executable node, and Referenced file present: False. Read GEMINI.md in your editor as well. Its instruction to preserve missing evidence is part of this fixture, not proof of how a model will behave.
This script is an inventory helper for the tiny fixture. It does not validate the full extension schema, inspect dependencies, follow every possible remote endpoint or detect malicious code. Do not use a clean inventory as a security certificate.
For an actual candidate, inspect the exact revision you intend to use in a plain-text viewer before opening it in an agent-enabled workspace. Record the source URL and commit identifier. Follow every declared executable into its source; inspect dependency manifests and installation instructions without running them. If the source you need is absent, keep the decision open.
Look beyond the manifest
A manifest is a starting point. Read the rest of the package and make a table like this in your review note:
| Review question | Evidence to retain | Reason to pause |
|---|---|---|
| What instructions will it add? | Context and command file paths, with a short summary | Instructions demand unrelated uploads or bypass review |
| What starts a process? | Executable path, arguments and reviewed source revision | Missing script, unexplained download or unknown dependency |
| What runs automatically? | Hook configuration and the scripts it references | Trigger or side effect is not understood |
| What external access is needed? | Endpoint, requested credential scope and intended operation | Credential request exceeds the task |
| What would prove it useful? | One synthetic input and a human-written expected result | Only an installer success message is available |
Hooks deserve their own inspection. Google documents them as executable code running with the user’s privileges; a friendly description does not establish what the script does. Follow the command into the actual file and check its reads, writes and network operations. Official hook security guidance
Folder trust is a separate control. Google’s current documentation says the feature must be enabled; an untrusted workspace restricts extension management and MCP connections. Check your settings rather than assuming a trust dialog will always appear. Granting folder trust does not replace reviewing an extension. Trusted Folders documentation
Write the decision before touching install
For this exercise, save a note with these findings:
Candidate: review-fixture, version 0.0.1
Source: locally authored tutorial fixture
Context reviewed: GEMINI.md
Declared process: node, argument ${extensionPath}/server.js
Missing evidence: server.js is absent; implementation cannot be reviewed
Decision: HOLD installation
Next action: obtain and inspect the intended server implementation
Runtime result: not attempted
Your note passes the exercise if it identifies the absent file, names the declared process and keeps runtime behavior unknown. A claim that the package is safe, working or ready fails the exercise. Do not create an empty server.js just to turn the inventory line into True: file existence would still tell you nothing about correct behavior.
For a real candidate that clears review, the documented shell command is gemini extensions install followed by the reviewed source. The reference supports --ref for a Git revision. Keep interactive confirmation and avoid enabling automatic updates during the first evaluation. Extensions are globally enabled by default, and management changes require a restarted session. Record the intended scope before proceeding. Installation and management reference
After any separately approved installation, verify the listed extension and its activation state, then perform only the synthetic task you defined. Keep the resulting files or transcript and compare them with your answer key. An installed extension and a correct task result are two different observations.
Recover from an incomplete review
If JSON parsing fails, fix the local fixture’s syntax before interpreting its contents. If your file list differs, check that you are in the temporary lab directory rather than a real project. If a candidate asks for credentials before you understand why, stop that evaluation and obtain the missing explanation.
If you installed a real extension and need to suspend it, the reference documents gemini extensions disable with the extension name and --scope user or --scope workspace; restart the session afterward. Disabling future use does not reverse files already written or external actions already taken. Keep a record of those separately.
The practice fixture itself needs no uninstall because it was never installed. Keep the two source files and your review note as a reference exercise. For the next step, use the lesson on concrete project acceptance checks to define one useful task before trying a real package.
Official references
All sources checked November 5, 2026:
- Extension overview: what an extension can bundle.
- Extension reference: manifest fields, installation, activation scope and management commands.
- Gemini CLI hooks: executable hooks and their security implications.
- Trusted Folders: opt-in trust controls and restricted workspace behavior.
Put this to work
Read an extension manifest and identify the evidence needed for an installation decision.
Try
Inventory a synthetic extension whose declared MCP server file is deliberately absent.
Prove it worked
Produce a hold decision that cites the missing file and does not claim the package is safe.
Keep in view
- Practice on a local fixture without installing an extension or sending files to a model.
- Trace the manifest to its context and server files, then record what is missing.
- Keep installation, activation and a successful task as separate checks.