Skip to content

Document the Gemini CLI extension install in the README #252

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bompus merged 1 commit into from
Nov 11, 2026
Merged

Document the Gemini CLI extension install in the README #252

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 9 additions & 10 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,16 +162,15 @@ fails until every folder in `packages/` is named in this section.
emails the submitter when the listing is approved. It is not known how to
change an approved listing, or whether it shows a version, so check both once
it is approved.
- Gemini CLI extensions gallery (not submitted; pending until the repository
has the `gemini-cli-extension` topic): the `gemini-extension.json` at the
repository root, which adds the `swarmail` MCP server through
`npx -y swarmail-mcp`. People install it with `gemini extensions install
https://github.com/bompus/swarmail`. Gemini CLI installs the latest GitHub
release when a repository has one, so the command works only once a release
contains the file. After the first release that contains it, add the topic
and the install line to the README. The gallery's crawler finds the
repository by the topic and validates the manifest. The manifest's `version` is set in step 1
of Releasing; `bun run check` fails until it matches.
- Gemini CLI extensions gallery (pending until the gallery lists it): the
`gemini-extension.json` at the repository root, which adds the `swarmail` MCP
server through `npx -y swarmail-mcp`. People install it with `gemini
extensions install https://github.com/bompus/swarmail`; the README says so.
Gemini CLI installs the latest GitHub release when a repository has one, so a
change to the manifest reaches users with the next release. The gallery's
crawler finds the repository by its `gemini-cli-extension` topic and
validates the manifest. The manifest's `version` is set in step 1 of
Releasing; `bun run check` fails until it matches.
- Claude Code plugin marketplace: this repository, through
`.claude-plugin/marketplace.json` and the plugin in
`packages/claude-plugin/`. People add it with
Expand Down
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,12 @@ please open an issue.
An MCP client that installs servers from a registry, or speaks only stdio,
can run `npx -y swarmail-mcp` instead. That
[relay](packages/mcp-relay/README.md) forwards each request to the server
from step 2 and installs nothing itself.
from step 2 and installs nothing itself. Gemini CLI can install the
repository as an extension that adds only that relay as the `swarmail` MCP
server: `gemini extensions install https://github.com/bompus/swarmail`.
Swarmail's hooks do not cover Gemini CLI (the `.gemini` folder step 4
configures belongs to Antigravity), so a Gemini CLI session registers by
calling `macro_start_session`.

4. Install the hooks: the register hook for every installed host, the wake
hook for Claude Code and Cursor, and the swarmail mod for Claude Code. A
Expand Down
Loading