### Page affected
https://geminicli.com/extensions/
### Extension
- Repository: https://github.com/suhaib81/url-shortener-by-aaf
- Root manifest: https://github.com/suhaib81/url-shortener-by-aaf/blob/main/gemini-extension.json
- Public repository on the `main` default branch
- GitHub topic: `gemini-cli-extension`
- Manifest name: `url-shortener-by-aaf`
### Expected behavior
Per the [Gemini CLI extension release guide](https://github.com/google-gemini/gemini-cli/blob/main/docs/extensions/releasing.md), public repositories with the topic and a root manifest are crawled daily and listed in the gallery if they pass validation. We would expect this extension to appear, or an actionable validation error to be available.
### Actual behavior
As of 2026-10-02 13:03 UTC, https://geminicli.com/extensions.json returned HTTP 200, but contained neither `suhaib81/url-shortener-by-aaf` nor `url-shortener-by-aaf`. Daily checks from Sep 25 through Oct 2 also found no match. We have not received a gallery validation error.
### Request
Could you check whether this repository was discovered by the gallery crawler? If it was, please let us know whether it failed validation, was skipped, or is affected by indexing/cache lag, and provide the specific validation error or required change. We are not asking for manual placement ahead of other extensions.
The extension gallery crawler is an external service not present in the gemini-cli codebase.
Please provide your CLI version.
**Effort Analysis:**
Extensive searches across the repository using `grep_search` and `glob` (e.g., searching for 'gallery', 'crawler', 'gemini-cli-extension', and 'extensions.json') confirm that the extension gallery crawler and the generation of `https://geminicli.com/extensions.json` are managed by an external backend service, not within the `gemini-cli` codebase itself. The `.github/workflows/docs-rebuild.yml` workflow simply triggers an external webhook for website builds, and `docs/extensions/releasing.md` describes the crawler as an automated system. Because the actual crawler logic is external to this repository, there is no architectural complexity within the `gemini-cli` codebase to debug or refactor. The resolution will involve investigating the external service's logs, fixing an external configuration, or updating the documentation (e.g., `docs/extensions/releasing.md`). As this does not require debugging React state, PTY handling, or core MCP protocols within this repo, it maps to the `effort/small` category, which covers external investigations, documentation updates, and trivial configuration.
Thanks for the response. This issue concerns discovery of a public extension repository by the server-side gallery crawler, not the behavior of a locally installed CLI. Gemini CLI is not installed or available on PATH in the environment I can check, so I cannot provide a CLI version from it.
Could the gallery team check whether `suhaib81/url-shortener-by-aaf` was discovered and, if so, whether it failed validation or was skipped? If the CLI version is still needed for this server-side indexing issue, please explain which installation/version would be relevant.
Adding another reproducible instance for `arcmira/mcp`, with a passing CLI validation result. I maintain the Arcmira integration.
- Public repository, not archived, disabled or a fork: https://github.com/arcmira/mcp
- `gemini-cli-extension` topic is present. GitHub search `topic:gemini-cli-extension repo:arcmira/mcp` returns one result.
- Current root manifest: https://github.com/arcmira/mcp/blob/master/gemini-extension.json. The validation below was performed October 3, 2026, on the version stated below; this current link does not represent a new validation run.
- Manifest version `0.10.1`, remote `httpUrl`, and the referenced context file exists. Default branch is `master`.
Local validation with Gemini CLI **0.61.0** from the official npm package, published September 24:
```text
$ node cli-0.61.0/bundle/gemini.js --version
0.61.0
$ node cli-0.61.0/bundle/gemini.js extensions validate source-e6692f33
Extension source-e6692f33 has been successfully validated.
```
At October 3, 2026, 23:07 UTC, `https://geminicli.com/extensions.json` contained 2,110 records and no case-insensitive `arcmira` match. Its `Last-Modified` header was `Sat, 03 Oct 2026 22:15:31 GMT`. The topic/root-manifest setup was already present in our October 2 check. The catalog has changed since then, so this is not merely the same saved file.
Could the gallery team check this repository's discovery/validation result and expose any rejection reason? Local validation does not prove the external crawler accepts it, and I have not established the cause. This reports gallery absence, not an authenticated MCP installation test or a request for preferential placement.
👋 @Sandeep332005, thanks for your interest in this issue! We're reserving self-assignment for issues that have been marked with the `help wanted` label. Feel free to check out our list of [issues that need attention](https://github.com/google-gemini/gemini-cli/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22).