Repository navigation
Install the Antigravity CLI 1.5.2 for Gemini legs - #25
Merged
Merged
Conversation
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
… tokens The sandbox image installs agy from its 1.5.2 release tarball, checked against its sha256, as /usr/local/bin/agy outside the per-run HOME mount, with AGY_CLI_DISABLE_AUTO_UPDATE set. gemini-cli stays for archived campaigns. agy reaches the Gemini API through the proxy's /gemini passthrough, so it needs no new alias; gemini-3.8-flash, which agy's flash-tier subagents call, gains its cached-input rate. probe-a-new-cli.md gains an agy line, example-campaign.yaml an antigravity-cli leg, and the CHANGELOG lists the move to agy as landing with the next synth-lib pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh
…he pin install-and-first-run.md lists antigravity-cli's effort levels, low, medium and high, the levels of agy's Gemini models, and says agy refuses at launch a level the model lacks: Gemini 4 Argon's top level is high. The CHANGELOG entry says the image install is built here and the harness side lands with the next synth-lib pin, and that the proxy does not meter Google Search grounding fees. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh
Thykof
force-pushed
the
build/antigravity-cli
branch
from
November 9, 2026 10:55
0222e67 to
634c158
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.
Stacked on #24. Engine side: synthdataco/synth-lib#90.
Why
The next campaign's Gemini leg runs Gemini 4 Argon at its top reasoning level on Google's own agent CLI:
medium. Its compression and utility calls also go to older, unpriced models.agy). Since June, it is also where Google's free and AI-plan users go.agyhas a Gemini-API-key mode whose endpoint can be overridden. That is the same route gemini-cli uses through our proxy, so the leg stays metered through the/geminipassthrough.The adapter (launch and resume flags,
--effort, the env and the provisionedsettings.json) lands in a companion synth-lib PR. This PR is the deployment side. It is stacked on the Kimi Code 2.5.2 branch.Merge order. This PR merges after the synth-lib stack, once a pin-bump commit to the merged synth-lib lands on
build/kimi-code-2. On the current pin,campaigns/example-campaign.yamlfails to load withunknown cli: 'antigravity-cli', and so does the preflight loop indocs/operate-a-campaign.md, which loads every campaign yaml. The pin bump makes the leg load.What
sandbox/Dockerfileagy1.5.2 from its release tarball, checked against its sha256, as/usr/local/bin/agy, with auto-update offmetering/litellm_config.yamlgemini-3.8-flashgainscache_read_input_token_cost($0.075 / 1M)docs/probe-a-new-cli.mdagyline in the headless probe: the passthrough,modelProvider: "gemini",--modeland--effortdocs/install-and-first-run.mdeffortlevels,low,medium,high, and Argon's top,highcampaigns/example-campaign.yamlantigravity-clileg ongemini-3.8-flashCHANGELOG.mdThe install.
1.5.2, assetagy_cli_linux_x64.tar.gz. It holds one dynamically linked glibc binary,antigravity, about 244 MB, which needs glibc ≥ 2.26. The base image has 2.39.da696a8d…62711, and it matches a fresh download./usr/local/bin, likeuv, because the per-run HOME is mounted over/root.install.shis not used, for three reasons: it takes no version, it installs to$HOME/.local/bin, and it then edits shell profiles.Auto-update. Unless
AGY_CLI_DISABLE_AUTO_UPDATEis set,agyupdates itself in the background and relaunches on the new version. The image sets it, and the synth-lib adapter sets it again in the leg's env.The proxy.
agycalls/v1beta/models/<id>:streamGenerateContentwithx-goog-api-key, the same request gemini-cli sends, and the/geminipassthrough forwards it verbatim.modelmust be a real Google id, andgemini-4-argonis already priced.Effort. agy's Gemini models take
low,mediumandhighat most; only its Claude variants carrymax.agyrefuses at launch a level the model lacks, so an Argon leg setseffort: high.Calls that leave the leg's model.
selfandprosubagentsflash-tier subagentsGoogle charges grounding at $14 per 1,000 searches after 5,000 free a month. On the API-key route, no documented setting pins the flash tier or the search model to the leg's model.
Tests
uv run black --check .uv run pytest -qdocker build --check sandbox/antigravitylitellm_config.yamlparsed with PyYAMLgemini-3.8-flashloads with its three ratesexample-campaign.yamlloaded with the synth-lib adapterantigravity-clileg loadsexample-campaign.yamlloaded on the current pinunknown cli(see Merge order)Not run: the image build, and anything that executes
agy:/v1beta/models/gemini-4-argon:streamGenerateContentwithx-goog-api-key;http://base URL is accepted;generationConfig.thinkingConfig.thinkingLevelis"HIGH"with--effort high;-ccarries the first run's turns;init,step_updateandresult;AGY_ERRORlines and soft-denied tools.Open:
agy's telemetry off in a headless run. Google documents it as an account setting, and the API-key route has no account. The capture above lists whether it reachesplay.googleapis.com.--dangerously-skip-permissionsno longer auto-approvesagy's built-in list of protected commands, which Google does not publish. In-pthey are soft-denied and the run continues.🤖 Generated with Claude Code
https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh