feat(desktop): add Antigravity as a PATH-probed harness - #6462
Open
sanjay3290 wants to merge 1 commit into
Open
Conversation
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
force-pushed
the
feat/antigravity-harness-id
branch
from
August 21, 2026 05:55
198e860 to
c5f120b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
agyCLI is onPATH, the harness appears; otherwise the catalog entry showsNot installedwith a link to antigravity.google.The main reason to land this now is ID reservation.
antigravitybecomes 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):agent,mcp,models,plugin,update— there is noacpmode.stringson the binary returns zero matches foragentclientprotocol,agent-client-protocol,session/new, orsession/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
antigravityKnownAcpRuntimewithagyas its command andgoogle-antigravity/agy-acp-serveras aliasesBUILTIN_IDS; custom harnesses with that ID (any casing) are rejected and dropped by the loader.parcommand suffix alongside.exe/.cmd/.batCREDITS.mdnormalize_agent_argsnow treats a legacy singleacpargument 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 itsacpargument.Follow-up
An ACP shim over
agy -p --output-format stream-jsonis 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 failedcargo test -p buzz-acp— 813 passed, 0 failedcargo clippy --all-targets(desktop + buzz-acp) — no warningscargo fmt --check(desktop + buzz-acp) — cleanpnpm test(desktop) — 5195 passed, 0 failedpnpm typecheck— cleanNo UI screenshots: this change adds a catalog entry that only renders when
agyis installed, and adds no new screen or layout.