Skip to content

Install the Antigravity CLI 1.5.2 for Gemini legs - #25

Merged
Thykof merged 2 commits into
mainfrom
build/antigravity-cli
Nov 9, 2026
Merged

Thykof merged 2 commits into
mainfrom
build/antigravity-cli

Conversation

@Thykof

@Thykof Thykof commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

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:

  • No gemini-cli release knows a Gemini 4 model. It sends no thinking level for Argon, so campaign-6's leg ran at the API's default, medium. Its compression and utility calls also go to older, unpriced models.
  • gemini-cli's README now points Gemini 4 users to the Antigravity CLI (agy). Since June, it is also where Google's free and AI-plan users go.
  • agy has 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 /gemini passthrough.

The adapter (launch and resume flags, --effort, the env and the provisioned settings.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.yaml fails to load with unknown cli: 'antigravity-cli', and so does the preflight loop in docs/operate-a-campaign.md, which loads every campaign yaml. The pin bump makes the leg load.

What

File Change
sandbox/Dockerfile agy 1.5.2 from its release tarball, checked against its sha256, as /usr/local/bin/agy, with auto-update off
metering/litellm_config.yaml gemini-3.8-flash gains cache_read_input_token_cost ($0.075 / 1M)
docs/probe-a-new-cli.md An agy line in the headless probe: the passthrough, modelProvider: "gemini", --model and --effort
docs/install-and-first-run.md antigravity-cli's effort levels, low, medium, high, and Argon's top, high
campaigns/example-campaign.yaml An antigravity-cli leg on gemini-3.8-flash
CHANGELOG.md Under "Planned, not built": the image is built here, the harness lands with the pin; grounding fees go unmetered

The install.

  • Release 1.5.2, asset agy_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.
  • The sha256 is GitHub's asset digest, da696a8d…62711, and it matches a fresh download.
  • The binary sits in /usr/local/bin, like uv, because the per-run HOME is mounted over /root.
  • Google's install.sh is not used, for three reasons: it takes no version, it installs to $HOME/.local/bin, and it then edits shell profiles.
  • gemini-cli 0.61.0 stays on the npm line for archived campaigns.

Auto-update. Unless AGY_CLI_DISABLE_AUTO_UPDATE is set, agy updates 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.

  • No new alias. agy calls /v1beta/models/<id>:streamGenerateContent with x-goog-api-key, the same request gemini-cli sends, and the /gemini passthrough forwards it verbatim.
  • The leg's model must be a real Google id, and gemini-4-argon is already priced.
  • Gemini 4 Argon's introductory rates end on 2026-11-30 and double on 2026-12-01. The existing comment already says so.

Effort. agy's Gemini models take low, medium and high at most; only its Claude variants carry max. agy refuses at launch a level the model lacks, so an Argon leg sets effort: high.

Calls that leave the leg's model.

Call Model Metered
Main agent, self and pro subagents the leg's model yes
flash-tier subagents Gemini 3.8 Flash yes, now with its cached rate
Web search its own model, plus Google Search grounding tokens: yes; grounding fees: no

Google 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

Check Result
uv run black --check . 11 files unchanged
uv run pytest -q 42 passed
docker build --check sandbox/ no warnings
sha256 of the 1.5.2 tarball, and its members matches the pinned digest; one member, antigravity
litellm_config.yaml parsed with PyYAML gemini-3.8-flash loads with its three rates
example-campaign.yaml loaded with the synth-lib adapter the antigravity-cli leg loads
example-campaign.yaml loaded on the current pin unknown cli (see Merge order)
Gemini API pricing page 3.8 Flash cached input $0.075 / 1M to 2026-12-31; Argon doubles on 12-01

Not run: the image build, and anything that executes agy:

  • A local capture, with the binary pointed at a plain-http stand-in for the Gemini API. It should confirm:
    • requests reach /v1beta/models/gemini-4-argon:streamGenerateContent with x-goog-api-key;
    • an http:// base URL is accepted;
    • generationConfig.thinkingConfig.thinkingLevel is "HIGH" with --effort high;
    • -c carries the first run's turns;
    • stream-json has init, step_update and result;
    • which other hosts it calls (telemetry, the updater).
  • One real call through the proxy. It should show the spend on the key at Argon's price and cached tokens at the cached rate.
  • The smoke leg at $2 / 30 min. It should list the models in the key's spend logs, and count AGY_ERROR lines and soft-denied tools.

Open:

  • Telemetry. No documented setting turns 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 reaches play.googleapis.com.
  • Protected commands. Since 1.5.2, --dangerously-skip-permissions no longer auto-approves agy's built-in list of protected commands, which Google does not publish. In -p they are soft-denied and the run continues.

🤖 Generated with Claude Code

https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@Thykof
Thykof added this pull request to stack #28 November 9, 2026 10:54
Base automatically changed from build/kimi-code-2 to main November 9, 2026 10:55
Thykof and others added 2 commits November 9, 2026 11:55
… 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
Thykof force-pushed the build/antigravity-cli branch from 0222e67 to 634c158 Compare November 9, 2026 10:55
@Thykof
Thykof merged commit a92220a into main Nov 9, 2026
4 checks passed
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