From e133acd299719a9fb720037dee9598fe1c8d4b25 Mon Sep 17 00:00:00 2001 From: christine betts Date: Wed, 3 Sep 2025 16:19:08 -0700 Subject: [PATCH] Remove command from extension docs (#7675) Co-authored-by: cornmander --- docs/extension.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/docs/extension.md b/docs/extension.md index 8c5f0a1ae6..b807524651 100644 --- a/docs/extension.md +++ b/docs/extension.md @@ -75,19 +75,6 @@ For example, if both a user and the `gcp` extension define a `deploy` command: - `/deploy` - Executes the user's deploy command - `/gcp.deploy` - Executes the extension's deploy command (marked with `[gcp]` tag) -## Installing Extensions - -You can install extensions using the `install` command. This command allows you to install extensions from a Git repository or a local path. - -### Usage - -`gemini extensions install | [options]` - -### Options - -- `source positional argument`: The URL of a Git repository to install the extension from. The repository must contain a `gemini-extension.json` file in its root. -- `--path `: The path to a local directory to install as an extension. The directory must contain a `gemini-extension.json` file. - # Variables Gemini CLI extensions allow variable substitution in `gemini-extension.json`. This can be useful if e.g., you need the current directory to run an MCP server using `"cwd": "${extensionPath}${/}run.ts"`.