GeminiCLI.com Feedback: valid tagged extension missing from gallery — objekts-production-desk

peach420fuzz

### URL of the page with the issue https://geminicli.com/extensions/ ### What is the problem? objekts Production Desk is not appearing in the Gemini CLI Extensions Gallery or the public extensions.json registry, although the extension meets the documented gallery requirements and passes the official validator. Repository: https://github.com/peach420fuzz/objekts-production-desk Root manifest: https://github.com/peach420fuzz/objekts-production-desk/blob/main/gemini-extension.json The public repository has the required GitHub topic: gemini-cli-extension. Official validation result on 2026-10-03: ``` npx -y @google/gemini-cli extensions validate . Extension . has been successfully validated. ``` A direct check of https://geminicli.com/extensions.json currently returns 2108 entries and contains neither objekts nor peach420fuzz/objekts-production-desk. ### What did you expect to happen? Because the repository is public, correctly tagged, has a root gemini-extension.json, and passes gemini extensions validate, it should be discovered by the daily gallery crawler and appear in the public gallery / extensions.json. ### Additional context The extension connects Gemini CLI to a hosted remote MCP server at https://mcp.objekts.ai/mcp and provides production preflight/diagnosis for AI/VFX, CGI, motion, animation and commercial visual production. It can already be installed directly: ```sh gemini extensions install https://github.com/peach420fuzz/objekts-production-desk ``` Could the gallery crawler/indexer please re-check this repository, or indicate whether another listing requirement is missing?

gemini-cli[bot]

**Effort Analysis:** The issue involves a missing entry for `objekts-production-desk` in the public gallery registry at `https://geminicli.com/extensions.json`. This URL is referenced as a default setting in `packages/cli/src/config/settingsSchema.ts` and `schemas/settings.schema.json`. According to `docs/extensions/releasing.md`, the gallery relies on an automated system that crawls repositories with the `gemini-cli-extension` topic and a `gemini-extension.json` manifest. A comprehensive codebase search confirms that the crawler logic and the static `extensions.json` file are not hosted within this repository (no crawler scripts were found in `scripts/` or `.github/workflows/`). Because the root cause resides in an external or out-of-band indexing service and resolving the user's request only requires a manual operational check or a backend triage (rather than modifying the CLI's architecture or TypeScript source code), the codebase complexity is negligible. This aligns perfectly with the `effort/small` category, which encompasses issues requiring trivial or no codebase logic changes.

gemini-cli[bot]

👋 @rajputdivyanshu81, 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).