OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core medium common DISPUTE

The Gemini default agent will not install or sign in, and Omarchy has replaced it with Antigravity `agy`

omarchyarchgemini-cliantigravitymise
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Checked every claim against the v4.0.3 tag, the quattro branch, all six cited threads read in full with comments, and this omarchy 4.0.2-1 workstation. The three stable claims hold at the newest tag, not just at v4.0.2. Confirmed from upstream at v4.0.3 (published 2026-09-08): install/user/mise.sh line 4 still runs omarchy-mise-install gemini, the recursive tree carries no migrations/1786719479.sh, and default/omarchy/omarchy-menu.jsonc line 138 still carries setup.default.agent.gemini. v4.0.1 and v4.0.2 are the same. Confirmed on this machine: the same three facts, plus /usr/share/omarchy/bin/omarchy-default-agent accepts gemini and has no agy case so omarchy-default-agent agy hits the usage branch and exits 1, and mise registry maps both agy and antigravity-cli to aqua:google-antigravity/antigravity-cli while gemini maps to npm:@google/gemini-cli. Confirmed PR 6900: merged 2026-08-20T20:28:32Z into quattro as ed7bae4ac5a570e9df307486e0202fdafcc6ee24, touching install/user/mise.sh, bin/omarchy-default-agent, bin/omarchy-agent, default/omarchy/omarchy-menu.jsonc and migrations/1786719479.sh. Read the quattro copies: the menu key became setup.default.agent.agy labelled Antigravity, omarchy-default-agent line 36 resolves agy, antigravity, antigravity-cli, gemini and gemini-cli all to agent=agy, and the migration installs the stub then rewrites a stored default of exactly gemini to agy. PR 8952 is open today against base branch v4-0-2, last updated 2026-09-08, and its body confirms it is the backport of 6900. Two defects. First, the fix block has the channels backwards. It calls dev the thread's confirmed route and calls edge untested. In issue 6889, matheusdmlopes answered treeder with 'In stable branch isnt available yet. On edge channel, yes.' and treeder replied 'got it on edge, thx.' That is edge confirmed by a reporter for exactly this problem. Dev appears only in issue 8553 as GaleasAndres's suggestion, and developercrocodiles never tried it and switched to omp instead. So edge is confirmed and dev is the unconfirmed one. Second, open question Q4 is answerable. Issue 8108's body cites https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/ and I retrieved that page today, HTTP 200, 37445 bytes. It reads 'On June 18, 2026, Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro and Ultra, as well as those using it free of charge using Gemini Code Assist for individuals.' PR 8952's body cites a second URL for the same date. The date belongs in the record with that citation rather than omitted. Smaller corrections folded into the rewrites: I read /usr/share/omarchy/bin/omarchy-mise-install, confirmed the two-argument form <package> [command-name [bin-name]] is supported so omarchy-mise-install antigravity-cli agy is valid, and confirmed it only writes an executable shim at ~/.local/bin/agy and prints nothing. The record made no claim about its output, so nothing needed fixing there, but the shim runs mise use -g --quiet antigravity-cli on every invocation and not only the first, so 'on first use' was reworded. The symptom claimed a report on 4.0.1-1 and no reporter states that version, so the symptom now names what reporters actually gave. The verify block claimed agy --help signs in, which help output does not do. Not exercised: I did not run omarchy-mise-install, omarchy-channel-set or agy, so the stub's behaviour after install and the sign-in with a personal Google account rest on odcpw on issue 8108 and toni-kk on issue 8553, not on me. ~/.local/bin/agy is absent here and ~/.local/bin/gemini is present, so nothing on this machine has run the new path.

The cause above was rewritten on 2026-09-11 to match this note; the fix was corrected by the audit itself.
RISK

Both channel switches replace the packaged omarchy and omarchy-settings with the omarchy-dev and omarchy-settings-dev packages from the edge pacman channel, so they bring unreleased changes with them and set a reboot-required state. omarchy-channel-set dev goes further: it clones the Omarchy source into ~/omarchy, links Omarchy to that checkout with omarchy-dev-link so OMARCHY_PATH stops pointing at /usr/share/omarchy, and its own gum prompt says it is exclusively intended for developers working on Omarchy itself. Prefer the mise stub on a stable machine. If you do switch, edge is the lighter of the two and the one reporters confirmed, and omarchy-channel-set stable unlinks any checkout and puts the packaged tree back.

Symptom

Choosing Gemini in the Omarchy menu under Setup, Defaults, Agent fails in one of two ways.

The mise install fails outright:


mise ERROR no tasks defined in ~/.local/share/mise/installs/gemini/0.56.0/node_modules/.mise/node-pty@1.0.0/node_modules/node-pty. Are you in a project directory?
mise ERROR Failed to install npm:@google/gemini-cli@latest: aube install failed: lifecycle script install failed for node-pty@1.0.0: script `install` exited with code Some(1)
Could not install Gemini with mise

Or the install succeeds and the sign-in fails in a full-screen terminal with no way to cancel, every time, after the browser half completes:


Failed to sign in. Message: This client is no longer supported for Gemini Code
Assist for individuals. To continue using Gemini, please migrate to the
Antigravity suite of products: https://antigravity.google

The manual says agy installs itself when run, but on stable agy is command not found and the menu still offers Gemini. Reporters gave omarchy 4.0.0-1, 4.0.2-1 and a fresh 4.0.2 install. The v4.0.1, v4.0.2 and v4.0.3 tags all carry the same menu entry and the same omarchy-mise-install gemini line, so every 4.0.x stable release is affected. Super+Ctrl+Shift+A and omarchy refresh applications reach the same failure.

Cause

Google stopped serving Gemini CLI requests for individual Google accounts on 2026-06-18 and withdrew the Login with Google path for them, which is what the sign-in error says. Google's own announcement reads: "On June 18, 2026, Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro and Ultra, as well as those using it free of charge using Gemini Code Assist for individuals." Gemini CLI now needs a paid API key or an enterprise licence. Omarchy's menu entry still installs and selects it.

The maintainer replaced Gemini with Antigravity CLI (agy) in PR #6900, merged to quattro on 2026-08-20 as merge commit ed7bae4ac. That change makes install/user/mise.sh install antigravity-cli as agy, renames the menu key to setup.default.agent.agy labelled Antigravity, keeps gemini and gemini-cli as aliases resolving to agy in omarchy-default-agent, and adds migration 1786719479.sh, which creates the lazy agy stub, rewrites a stored default of exactly gemini to agy, and removes the old ~/.local/bin/gemini wrapper. Issues #6889, #8108, #8456 and #8553 were all closed as implemented on quattro, which the maintainer spelled out is not the same as shipped.

The stable package still has none of it. The backport is PR #8952, open against the v4-0-2 branch as of 2026-09-11 and last updated 2026-09-08. v4.0.3 was published on 2026-09-08 without it, so the newest release is still affected. Checked at the v4.0.3 tag and on an omarchy 4.0.2-1 install: install/user/mise.sh still runs omarchy-mise-install gemini, there is no migrations/1786719479.sh, and omarchy-menu.jsonc still lists setup.default.agent.gemini. The v4.0.1 and v4.0.2 tags match.

Fix

**On stable, today.** Install the same stub the migration installs, then launch it by name. One reporter confirmed this on 4.0.2-1:


omarchy-mise-install antigravity-cli agy
agy

omarchy-mise-install takes <package> [command-name [bin-name]], so that call writes an executable shim at ~/.local/bin/agy and prints nothing. The shim exports MISE_MINIMUM_RELEASE_AGE=0, runs mise use -g --quiet antigravity-cli on every invocation, which installs the tool the first time and is a no-op after that, then runs exec mise x antigravity-cli -- agy "$@". The mise registry already maps both agy and antigravity-cli to aqua:google-antigravity/antigravity-cli, so no extra plugin is needed. omarchy-default-agent agy will not work yet: the packaged omarchy-default-agent has no agy case, so it prints its usage line and exits 1 until PR #8952 lands.

**On a build that carries PR #6900.** Update, and migration 1786719479 installs the stub and rewrites a gemini default to agy:


omarchy update
omarchy-default-agent agy

Then Omarchy menu, Setup, Defaults, Agent, Antigravity. The thread's confirmed route to such a build is the **edge** channel, which swaps the omarchy and omarchy-settings packages for omarchy-dev and omarchy-settings-dev and leaves the packaged layout in place:


omarchy-channel-set edge

Two reporters on issue #6889 confirmed the Antigravity agent works on edge and is still missing on stable. The dev channel reaches the same code and was suggested on issue #8553, but nobody in the threads confirmed it for this, so treat dev as untested here. Both commands also sit behind Super+Space, Update, Channel. Return to the packaged tree later with:


omarchy-channel-set stable

Gemini's own configuration and credentials under ~/.gemini are left in place either way. The migration does delete ~/.local/bin/gemini, but only when that file is Omarchy's own generated wrapper, so a hand-written gemini launcher survives.

Verify


ls -l ~/.local/bin/agy                                          # the stub omarchy-mise-install wrote
agy --help                                                     # installs antigravity-cli on first run, then prints help
grep -n 'antigravity' "$OMARCHY_PATH"/install/user/mise.sh     # on a build carrying PR #6900
ls "$OMARCHY_PATH"/migrations/1786719479.sh
cat ~/.config/omarchy/defaults/agent                           # agy once the migration has run

Signing in happens on a real agy run rather than on --help. One reporter on the fixed tree confirmed agy installs, signs in with a personal Google account and runs, and that the Agent submenu shows Antigravity checked.

Sources

default-agent-gemini-fails-antigravity-replacement