Omniscio

Anti-Gravity Provider

Anti-Gravity (agy) is a selectable provider alongside claude, codex and gemini — how to enable it, the dedicated virtual project and per-project default, the model story, the gap and error states, and how each turn runs under the hood.

On this page

What it is

Omniscio supports spawning Claude-Code-style sessions backed by Google's Anti-Gravity CLI (agy) as one of its selectable providers, alongside claude (the default), codex, gemini, and the rest of the pickable set. Anti-Gravity is Google's next-gen agentic CLI and a potential replacement for Gemini in this app — both wired up so users can pick whichever feels better.

What the user sees

An Anti-Gravity session looks identical in the sidebar and main pane to a Claude session — same status dots, same streaming bubbles, same Ctrl+Enter to send. The only user-visible differences:

  • The session header shows the official upward-pointing "A" chevron mark (rendered in the brand blue #3186FF), with no text label, instead of nothing. Every started session shows its engine mark next to the title — Claude included, in its brand orange (only logo-less internal engines like OpenClaw / orchestrator show nothing). The per-launch provider dropdown on a fresh session shows the same mark next to each row, also in full brand color.
  • Streaming is block-mode: the agent's reply appears as one chunk when the turn completes, not token-by-token as it generates. (agy v1.0.9 in headless mode emits nothing incrementally — Omniscio reads the finished reply from agy's on-disk transcript at end-of-turn. See "How it works under the hood".)
  • Tool use auto-approves during a turn, and runs outside agy’s own sandbox. agy 1.5 starts headless runs in Auto mode, which forces its terminal sandbox: a repository’s .git folder becomes read-only and the network is blocked, so the agent could not commit and could not reach Omniscio (no replies to the session that started it, and long messages arrived as a summary it could not open). Omniscio passes --dangerously-skip-permissions on every turn (the --mode=default flag it also passed was dropped on 2026-11-20: agy 1.5 rejects it and falls back to its default mode anyway): agy’s sandbox stays off unless your own agy settings turn it on, and agy still blocks its built-in list of dangerous commands. The worktree Omniscio isolates each session in is the boundary; on a patch-road computer it is a Windows write sandbox instead (below). These flags apply only to turns Omniscio runs; agy you run yourself is unchanged.
  • The turn's tool activity (file reads, searches, subagents) shows as a compact ▸ step list folded into the message — so a multi-step run shows its work, like Claude/Cursor. agy 1.5 writes almost every tool result as a generic record, so each step is named from the tool call that asked for it: commands, edits and file writes show as steps too, not only reads and searches. And if a turn is interrupted (e.g. the model is briefly overloaded and returns a 429, or stops before finishing), you get an honest, retryable "…was interrupted before finishing — re-send to retry" row instead of a stray half-sentence.

Where to find it

How to enable

Master toggle required first. Anti-Gravity, Gemini, and Codex are alternative providers — on a fresh install Anti-Gravity is already visible (the master toggle is ON by default since 2026-10-03); on a profile that last saved before that setting existed the entire Anti-Gravity setup section stays hidden in Settings → Accounts until you flip it on. Flip Settings → Accounts → Show alternative AI providers to ON and the Anti-Gravity panel appears. With the master off, the per-project "Default provider" radio collapses to a single Claude row and the session header's provider switcher (ChangeProviderButton) hides Anti-Gravity — it effectively does not exist in the UI even if every gate below is configured. Your "Allow Anti-Gravity sessions" toggle and per-project defaults are preserved across master-toggle flips.

You need both of these in place:

  1. Anti-Gravity CLI binary — install from https://antigravity.google/download#antigravity-cli. The installer drops the binary at %LOCALAPPDATA%\agy\bin\agy.exe (Windows, via irm install.ps1 | iex) or ~/.agy/bin/agy (POSIX, via curl install.sh | bash). Omniscio discovers it on PATH first, then falls back to those install locations. The Settings panel shows Anti-Gravity CLI: Installed with the binary's live version (e.g. v1.0.9) in green or Not installed with a download link. The version is re-read each time the panel opens, so a self-updated agy is never shown stale.
  2. Settings → Account → Allow Anti-Gravity sessions toggle — off by default; same security stance as the API-key spawn guard.

There is no API key step. Anti-Gravity authenticates via Google Sign-In, and the credentials live inside the binary's OS keyring — Omniscio never touches them. To sign in:

  • Click Sign in with Anti-Gravity in the Settings panel. Omniscio opens agy --prompt-interactive "Hello" in a new, visible terminal window (a fresh Windows console; macOS Terminal) that you own — it stays open after Omniscio quits and after agy exits, so you can read the result. Complete the Google sign-in in the browser that opens, type /exit to close the interactive prompt, and you're done. The next session Omniscio spawns will reuse those credentials silently. (On Linux there's no in-app launcher — run agy --prompt-interactive Hello in a terminal yourself.)

Once toggle + binary are green, you can launch an Anti-Gravity session three ways:

  • Per-launch override — on a fresh (zero-message) session, the ChangeProviderButton in the new session's main panel (the launch-config pickers on a fresh session) lets you pick a one-off provider before sending the first message. Non-ready providers appear aria-disabled with a "Set up…" / "Install…" suffix and deep-link to Settings.
  • Per-project default — Edit Project dialog (three-dot menu → Edit) has a "Default provider" section with one radio per pickable provider. Pick Anti-Gravity and the project's sidebar "+ New Session" button spawns Anti-Gravity automatically.
  • Programmatically — anything that creates a session with provider: 'antigravity' (recipes, agent-driven sessions, the API). Same readiness gates apply on the backend.

Dedicated __antigravity__ virtual project

Just like Gemini and Codex have their own virtual projects in the Omniscio sidebar group, Anti-Gravity has one too — gated behind Settings → Account → Enable dedicated Anti-Gravity project (off by default). Flip it on and an Anti-Gravity entry appears in the sidebar group below the existing Gemini and Codex rows. Sessions launched from there bypass the global "Allow Anti-Gravity sessions" toggle (being inside the dedicated VP is itself the affirmation that you want to use the provider). The binary check still applies.

Per-project default

Each project remembers a default provider in the projectDefaultProviders setting (a Record<projectId, ProviderId> — the value accepts any of the registry's pickable provider ids, 20 today, and the set grows automatically as new pickable providers ship). Empty by default — every project falls back to Claude. Change it from the project's three-dot menu → Edit → Default provider radios; the change persists immediately.

When a project's default is set to Anti-Gravity but Anti-Gravity isn't ready (toggle off or binary missing), an Inbox card names the project and provider and says in plain words what is missing. Its button opens the Settings screen where the gap is fixed, and the card clears itself once the provider is usable. The project's sidebar row itself carries no readiness marker.

How it behaves

Choosing the model

Anti-Gravity has a Model and an Effort picker, like the other engines. The agy CLI (1.5 and later) takes --model and --effort in print mode, so Omniscio passes your pick on every turn.

  • The models are the ones agy acp lists for a signed-in Google AI Ultra account (measured 2026-11-19): Gemini 4 Neon, Carbon, Argon and Hydrogen; Orchestrator (Neon), (Carbon) and (Argon); Gemini 3.8 Flash; Claude Opus 5.5 and Claude Sonnet 5.5; and GPT-OSS 120B. Each is stored as antigravity/<agy id> (for example antigravity/gemini-4-neon), and Omniscio strips the prefix before it calls agy --model.
  • The levels follow what agy accepts for each model: Neon and Hydrogen take Low, Medium, High and Extra High; Carbon, Argon, Flash, Opus and Sonnet take Low, Medium and High; the Orchestrators and GPT-OSS take none (agy refuses --effort on them with "--effort is not supported for model").
  • No pick sends neither flag, so agy runs the account's own default model and level. The Effort picker stays empty until a model is chosen, so --effort is never sent alone.
  • Inherited levels reach the turn exactly as the picker shows them: the session's level, then the project default, then the per-model or per-provider default from Settings. A level the chosen model does not take is dropped before the turn starts.
  • A model your plan does not include (a cheaper Google plan may lack Claude or Neon) makes agy exit with "invalid model selection", which shows as the turn's error row.

The list lives in ANTIGRAVITY_MODEL_SPECS in src/shared/providers/provider-models.ts; the flags are built by antigravityModelFlags in antigravity-turn-runner.ts; the level is resolved by resolveTurnEffort in the shared one-shot engine base. See start-a-new-session.md.

Error states and fixes

Three gap codes — fewer than Gemini / Codex because there's no API key step:

Gap What it means Click-to-fix lands you at…
toggle-off "Allow Anti-Gravity sessions" is OFF in Settings Settings → Account → Allow Anti-Gravity sessions toggle
binary-missing agy CLI not on PATH or in known install paths Settings → Account → Anti-Gravity CLI binary panel
sign-in-missing agy is installed but has no stored Google credential Settings → Account → Anti-Gravity sign-in card

If you're inside the dedicated __antigravity__ virtual project, the toggle-off gate is bypassed automatically — binary-missing and sign-in-missing can still stop the spawn there.

On a Windows computer that takes the patch road (no worktrees), Anti-Gravity runs inside a Windows write sandbox instead of a worktree: it can read the whole project, but Windows refuses every write outside its own session folder, so it cannot commit or land a change itself. Instead it leaves land/change.patch (a unified diff) and land/land.json (slug, one-line message, roadmap feature id, optional tests) in that folder, and when the turn ends cleanly Omniscio lands it on local master for it: it moves the pair out of the folder first (so a patch lands at most once), cuts a patch/agy-auto-* branch with the patch launcher, records the hand-off, and lands it, after the named tests pass or, with none named, untested under the owner's recorded approval for exactly this road. The session gets one row saying whether it was handed to the lander or why not, with the log kept under the app's data folder (antigravity-auto-land/<session>/). A patch that touches package.json or a lockfile is refused. Its turns run one agy program per message there (not the ACP chat), from a private copy of its agy settings folder. On macOS and Linux it is still refused on the patch road, because it needs a worktree as its safety boundary. That refusal comes the moment you pick the engine — when you start a session or switch an existing one to Anti-Gravity — never after you have typed your first message. A session that already has its own worktree keeps it and may switch. (Until 2026-11-20 switching an existing session skipped this check, so the switch went through and every message was then refused.)

The gates run in that order, so a switched-off or uninstalled provider always reports the reason that comes first rather than a misleading sign-in notice.

The signed-in check (sign-in-missing)

A signed-out launch used to be discovered only after it wasted a turn: agy --print would run its own silent auth, wait, and die. Now Omniscio asks the OS credential store whether agy's entry exists before anything spawns, and refuses immediately with "{provider} needs you to sign in once."

  • It reads presence only. Omniscio runs cmdkey /list and matches the entry name (gemini:antigravity), never its value. No token is read, stored or transmitted, and the address shown on the card comes from agy's own log line, not from the credential.
  • The match is exact. A lookalike entry (gemini:antigravity-backup) is not read as a sign-in.
  • It fails open, always. An unsupported platform, a missing command, a timeout, or output it cannot parse all answer "unknown" — and only a positive "signed out" refuses. A probe that cannot tell never blocks a person who is really signed in.
  • The answer is memoised for 15 seconds on the launch path, because the readiness ladder runs on the picker, the models endpoint and every launch. The account card reads the live three-state answer instead, so it never shows a stale line.
  • It can be switched off. antigravitySignInGateEnabled (on by default) is the escape hatch: with it off, a launch is never refused on sign-in state, so a machine whose credential the probe cannot see is never trapped. Only an explicit false turns the check off — an older install that has never written the setting keeps it on.

What the Anti-Gravity card shows

The Settings → Accounts → Anti-Gravity card carries a state line under its Sign in button:

What the probe found The line
A credential is stored "Signed in as <address>." (or "Signed in." if no address is known)
No credential is stored "Not signed in yet. Use Sign in above, then this line updates."
The probe could not tell "Could not read the sign-in state on this computer."

While the person is signed out the card re-reads every 15 seconds and stops once they are signed in, so finishing the Google step in the terminal updates the card without re-opening Settings. An unknown answer is never phrased as a signed-out one.

Usage numbers are not shown, and this is deliberate. agy keeps no quota figures on disk — its log records doRefreshQuota: starting reload with nothing after it — so the card shows the account and never a percentage it did not actually read. There is also no Sign out button: agy offers /logout only inside its interactive terminal, and no non-interactive path has been proven.

On a Windows computer that takes the patch road (no worktrees), Anti-Gravity runs inside a Windows write sandbox instead of a worktree: it can read the whole project, but Windows refuses every write outside its own session folder, so it cannot commit or land a change itself. Instead it leaves land/change.patch (a unified diff) and land/land.json (slug, one-line message, roadmap feature id, optional tests) in that folder, and when the turn ends cleanly Omniscio lands it on local master for it: it moves the pair out of the folder first (so a patch lands at most once), cuts a patch/agy-auto-* branch with the patch launcher, records the hand-off, and lands it, after the named tests pass or, with none named, untested under the owner's recorded approval for exactly this road. The session gets one row saying whether it was handed to the lander or why not, with the log kept under the app's data folder (antigravity-auto-land/<session>/). A patch that touches package.json or a lockfile is refused. Its turns run one agy program per message there (not the ACP chat), from a private copy of its agy settings folder. On macOS and Linux it is still refused on the patch road, because it needs a worktree as its safety boundary. That refusal comes the moment you pick the engine — when you start a session or switch an existing one to Anti-Gravity — never after you have typed your first message. (Until 2026-11-20 switching an existing session skipped this check, so the switch went through and every message was then refused.)

Signed out at turn time (no reply / empty bubble)

The two gaps above are checked before a spawn. A different failure happens during a turn: if agy is installed and the toggle is on but you are not signed in to Antigravity, agy --print launches an interactive Google sign-in, waits ~30 seconds, then exits "successfully" with no output at all (the auth error goes only to agy's own log). Earlier Omniscio builds showed this as a blank reply that quietly went back to "needs you" — no explanation.

Now any one-shot turn that finishes cleanly but produces zero output is surfaced as a real error row instead of a blank, and for Antigravity specifically Omniscio reads agy's own log and, when it sees the not-signed-in signature, shows: "Antigravity isn't signed in — open Settings → Accounts to sign in again." That row carries an "Open Anti-Gravity settings" button — clicking it jumps straight to Settings → Accounts → Anti-Gravity and flashes the row, so you don't navigate the named path by hand; click Sign in with Anti-Gravity there and re-send. The same one-tap "Open …" affordance appears on every provider sign-in/setup notice (Codex / Cursor / Pi / OpenCode / Claude "sign in again" / the Anthropic-compatible no-key rows) — see provider-setting-link-contract.md. This protects every one-shot engine (Cursor / OpenCode / Anti-Gravity) from the silent-empty-turn failure mode (Hermes migrated to persistent-external ACP 2026-08-01 and uses a different stall-detection path).

Signed out, newer agy (exit 1 with "Authentication required")

Newer agy builds report a sign-out on stderr and exit 1 (after waiting about 60 seconds for a pasted sign-in code). Omniscio reads that stderr too, so the row shows the same "Antigravity isn't signed in" line and its Open Anti-Gravity settings button instead of a generic "check that the agy CLI is installed and signed in" guess.

"Could not be started" on the first turn

A session started from the CLI (POST /project/:name/new) sends a much longer first prompt than the chat bubble shows, because project docs and coaching notes ride along invisibly. When that prompt would not fit on a Windows command line, Omniscio hands it to agy over stdin instead, so the turn starts normally. If Windows ever refuses to launch an engine at all, the row now says the engine could not be started and that the key and sign-in are not the cause, rather than calling it a process-tree safety stop.

MCP servers — not available

Anti-Gravity sessions get none of your MCP servers, and this is an honest gap rather than a setting you are missing: agy is Google's own binary, so it does not read the .mcp.json Claude's spawn writes, and it exposes no MCP flag, config file or protocol field for Omniscio to translate into. The registry declares mcp: false for it, and the wiring grid's feature-mcp row marks it missing rather than pretending otherwise.

This is one of five engines in that position today — see no-channel-is-declared in provider-mcp-connector-contract.md, which lists each with the evidence for why. It is not the same defect that made managed tool servers invisible on the seven engines that do have a channel (Cursor, Codex, Gemini, Grok, Kimi Code, Hermes, DeepSeek Harness); that one was fixed 2026-09-28.

Comparison with Gemini

Anti-Gravity is Google's successor to Gemini CLI. From Omniscio's perspective:

Concern Gemini Anti-Gravity
Auth Google sign-in, or an optional API key Google Sign-In via OS keyring (no env injection)
Streaming Live over ACP (gemini --acp), word by word Block mode (full reply at end-of-turn)
Multi-turn resume Native ACP session (session/load) Native ACP session (agy acp); switch off → prior turns re-sent in each prompt
Readiness gates 2 (toggle + binary); auth is checked at the turn 3 (toggle + binary + sign-in)
Binary install path npm / volta / nvm Standalone installer (%LOCALAPPDATA%\agy\bin / ~/.agy/bin)
Icon Four-point blue-purple-pink bloom Blue "A" chevron

If you've used Gemini in Omniscio, the only behavior differences you'll notice in chat are (1) replies appear all-at-once instead of streaming, and (2) there is no API-key option — Anti-Gravity always uses your Google sign-in.

  • gemini-provider.md — comparable provider with native NDJSON streaming and API-key auth
  • codex-provider.md — same launcher / readiness model, different binary (JSON-RPC long-lived child)
  • openclaw-provider.md — separate "alternative provider" model (remote WebSocket gateway, not a local CLI)

Last verified 2026-10-06