clients: Gemini CLI is dead (410 since 2026-06-18) - update the gemini/antigravity client registry for Antigravity CLI (agy) #226

New issue

Closed

opened 2026-07-17 18:07:42 +00:00 by hexajon · 1 comment

hexajon commented

2026-07-17 18:07:42 +00:00

(Migrated from codeberg.org)

Google shut down Gemini CLI on 2026-06-18 and replaced it with the closed-source Antigravity CLI (agy), sharing the agent harness with the Antigravity 2.0 desktop app. Only Gemini Code Assist Standard/Enterprise licenses (and paid API keys) retain working gemini CLI access; everyone else gets HTTP 410. The migration also renames MCP url to serverUrl (a silent failure for remote servers) and shifts the config layout.

madtea impact:

The gemini client (mcp-config printer + madtea install --mcp-client gemini, which shells out to gemini mcp add): now targets a dead CLI for most users. Decide: keep with a "requires an enterprise Code Assist license" caveat in the snippet/wiring output, or retire the client value with the deprecation etiquette (hidden, refuses with a pointer for one cycle).
The antigravity client (writes ~/.gemini/antigravity-cli/mcp_config.json): verify the path and JSON shape against current Antigravity 2.0 / agy - the migration notes say the layout shifted; check whether stdio server entries are affected by the url->serverUrl rename (they may not be) and whether agy now has a native mcp add that wiring should shell out to instead of writing the file directly.
Detection: agy on PATH should probably detect as the antigravity client; today detection looks for the desktop app config dir.
Docs: clients guide + COMPARISON/COMPAT rows updated to the post-shutdown reality; the migration guide is at antigravity.google/docs/gcli-migration.

Acceptance criteria:

The antigravity wiring verified against current agy/Antigravity docs (or a live install where possible); config path/shape corrected if drifted; a test pins the written shape.
The gemini client's fate decided and implemented (caveat text or deprecation), with the reasoning in one line of the clients guide.
agy detection wired if it is the current binary name.
COMPARISON/COMPAT + reference docs regenerated; deprecation etiquette followed for any removed client value.

Google shut down Gemini CLI on 2026-06-18 and replaced it with the closed-source Antigravity CLI (`agy`), sharing the agent harness with the Antigravity 2.0 desktop app. Only Gemini Code Assist Standard/Enterprise licenses (and paid API keys) retain working gemini CLI access; everyone else gets HTTP 410. The migration also renames MCP `url` to `serverUrl` (a silent failure for remote servers) and shifts the config layout. madtea impact: - The `gemini` client (mcp-config printer + `madtea install --mcp-client gemini`, which shells out to `gemini mcp add`): now targets a dead CLI for most users. Decide: keep with a "requires an enterprise Code Assist license" caveat in the snippet/wiring output, or retire the client value with the deprecation etiquette (hidden, refuses with a pointer for one cycle). - The `antigravity` client (writes ~/.gemini/antigravity-cli/mcp_config.json): verify the path and JSON shape against current Antigravity 2.0 / agy - the migration notes say the layout shifted; check whether stdio server entries are affected by the url->serverUrl rename (they may not be) and whether `agy` now has a native `mcp add` that wiring should shell out to instead of writing the file directly. - Detection: `agy` on PATH should probably detect as the antigravity client; today detection looks for the desktop app config dir. - Docs: clients guide + COMPARISON/COMPAT rows updated to the post-shutdown reality; the migration guide is at antigravity.google/docs/gcli-migration. Acceptance criteria: - The antigravity wiring verified against current agy/Antigravity docs (or a live install where possible); config path/shape corrected if drifted; a test pins the written shape. - The gemini client's fate decided and implemented (caveat text or deprecation), with the reasoning in one line of the clients guide. - `agy` detection wired if it is the current binary name. - COMPARISON/COMPAT + reference docs regenerated; deprecation etiquette followed for any removed client value.

hexajon commented

2026-07-17 19:29:01 +00:00

(Migrated from codeberg.org)

Pinning the one open sub-decision so this stays workable: the gemini client value follows the deprecation etiquette rather than keep-with-caveat - hidden, always refusing with a pointer for one release cycle, then removed. Rationale: the gemini CLI returns 410 for everyone outside enterprise Code Assist licenses, so a working --mcp-client gemini is now the exception rather than the rule, and a wiring path that fails for most users at the target CLI's own front door is the silent-green-light shape the install rework just eliminated. The refusal names the enterprise carve-out (licensed users can still paste the printed snippet, which stays available via mcp-config) and points at the antigravity client as the successor. If keep-with-caveat is preferred instead, say so here and the builder flips one branch.

The antigravity-side verification (current agy config path/shape, whether stdio entries are hit by the url to serverUrl rename, whether agy has a native mcp add) is doable against the public migration docs; no live install needed for the config-shape check.

Pinning the one open sub-decision so this stays workable: the gemini client value follows the deprecation etiquette rather than keep-with-caveat - hidden, always refusing with a pointer for one release cycle, then removed. Rationale: the gemini CLI returns 410 for everyone outside enterprise Code Assist licenses, so a working `--mcp-client gemini` is now the exception rather than the rule, and a wiring path that fails for most users at the target CLI's own front door is the silent-green-light shape the install rework just eliminated. The refusal names the enterprise carve-out (licensed users can still paste the printed snippet, which stays available via mcp-config) and points at the antigravity client as the successor. If keep-with-caveat is preferred instead, say so here and the builder flips one branch. The antigravity-side verification (current agy config path/shape, whether stdio entries are hit by the url to serverUrl rename, whether agy has a native mcp add) is doable against the public migration docs; no live install needed for the config-shape check.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sixfold-space/madtea#226

No description provided.

Rows
Columns