Skip to content

feat(desktop): add Antigravity as a PATH-probed harness - #6462

Open
sanjay3290 wants to merge 1 commit into
block:mainfrom
sanjay3290:feat/antigravity-harness-id
Open

feat(desktop): add Antigravity as a PATH-probed harness#6462
sanjay3290 wants to merge 1 commit into
block:mainfrom
sanjay3290:feat/antigravity-harness-id

Conversation

@sanjay3290

Copy link
Copy Markdown

Summary

Adds Google Antigravity to the Desktop runtime catalog as a PATH-probed harness. Buzz does not bundle or download a runtime for it — if the agy CLI is on PATH, the harness appears; otherwise the catalog entry shows Not installed with a link to antigravity.google.

The main reason to land this now is ID reservation. antigravity becomes a tier-1 reserved ID, so a user-defined custom harness cannot shadow it, and a future managed or shim integration won't break existing harness IDs.

Why there's no installer or auth probe

Google does not currently publish an ACP endpoint for Antigravity. On the tested binary (agy 1.1.17):

  • Subcommands are agent, mcp, models, plugin, update — there is no acp mode.
  • strings on the binary returns zero matches for agentclientprotocol, agent-client-protocol, session/new, or session/prompt.

So there is nothing to auto-install and nothing to probe for auth. Anything more than PATH probing would be speculative. The README records this explicitly so the next person doesn't have to rediscover it.

Changes

  • Register the antigravity KnownAcpRuntime with agy as its command and google-antigravity / agy-acp-server as aliases
  • Reserve the ID in BUILTIN_IDS; custom harnesses with that ID (any casing) are rejected and dropped by the loader
  • Normalize a .par command suffix alongside .exe / .cmd / .bat
  • Show Antigravity in the onboarding runtime order and readiness selection
  • Add a neutral placeholder mark and record its provenance in CREDITS.md

normalize_agent_args now treats a legacy single acp argument as "use this runtime's defaults" for every non-Goose runtime rather than only for runtimes with empty defaults. Behavior is unchanged for all existing runtimes; Goose still keeps its acp argument.

Follow-up

An ACP shim over agy -p --output-format stream-json is the natural next step. It needs its own design for permissions, tool calls, and cancellation, so it is deliberately not in this PR.

Testing

  • cargo test --manifest-path desktop/src-tauri/Cargo.toml --lib — 2713 passed, 0 failed
  • cargo test -p buzz-acp — 813 passed, 0 failed
  • cargo clippy --all-targets (desktop + buzz-acp) — no warnings
  • cargo fmt --check (desktop + buzz-acp) — clean
  • pnpm test (desktop) — 5195 passed, 0 failed
  • pnpm typecheck — clean

No UI screenshots: this change adds a catalog entry that only renders when agy is installed, and adds no new screen or layout.

@sanjay3290
sanjay3290 requested a review from a team as a code owner August 21, 2026 04:58
Reserves the `antigravity` tier-1 runtime ID and surfaces Google
Antigravity in the Desktop runtime catalog when the `agy` CLI is
found on PATH.

Antigravity is PATH-probed only — Buzz does not bundle or download a
runtime for it. Google does not currently publish an ACP endpoint for
Antigravity: `agy 1.1.17` exposes `agent`, `mcp`, `models`, `plugin`,
and `update` subcommands plus `--print --output-format stream-json`,
with no ACP `session/new` mode. Reserving the ID now keeps a future
managed or shim integration from breaking custom-harness IDs, and
stops a user-defined harness from shadowing `antigravity`.

- Register the `antigravity` KnownAcpRuntime with `agy` as its command
- Reserve the ID in BUILTIN_IDS so custom harnesses cannot claim it
- Normalize `.par` command suffixes alongside `.exe`/`.cmd`/`.bat`
- Show Antigravity in onboarding order and readiness selection
- Add a neutral placeholder mark; record provenance in CREDITS.md

An ACP shim over `agy -p --output-format stream-json` is the natural
follow-up once the wire format is pinned down; it needs its own design
for permissions, tool calls, and cancellation.

Signed-off-by: Sanjay Ramadugu <sramadugu1@gmail.com>
@sanjay3290
sanjay3290 force-pushed the feat/antigravity-harness-id branch from 198e860 to c5f120b Compare August 21, 2026 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant