Google's agy terminal coding agent as a mixin -- the CLI in an overlay, with the proxy-managed Ge...
191
Google's agy terminal coding agent as a mixin -- the CLI in an overlay, with the proxy-managed Gemini credential, Google's egress, and the settings and MCP seeds the agent needs. Layer it onto a shell base and run `agy`.
antigravity| Type | Required | Description | |
|---|---|---|---|
com.docker.sandbox/network-policy@1 | Required | — | |
com.docker.sandbox/credential@1 | Optional | Gemini API key for Antigravity's headless API-key mode | |
com.docker.sandbox/lifecycle@1 | Required | — | |
com.docker.sandbox/agent-context@1 | Required | — | |
deb/jqsbx run <agent> --kit sbx/antigravity-mixin:latestRun the following command to install sbx on your machine.
brew install docker/tap/sbxwinget install Docker.sbxNote
Experimental: Sandbox Kit v3This kit uses the experimental Sandbox Kit specification, specifically v3. The format and runtime behavior may change before v3 is stable.
The mixin form of the antigravity kit: Google's agy
terminal coding agent in an overlay that lands on a shell workload, instead of
a whole sandbox of its own.
A kind: mixin kit carrying the Antigravity CLI as a filesystem delta, with
the same declarations the workload makes — the proxy-managed Gemini
credential, the Google and Antigravity runtime allow list, BROWSER=xdg-open,
and both startup hooks (API-key mode selection and MCP-gateway registration).
Google's install.sh resolves its target from a manifest it fetches itself
and offers no staging prefix, so antigravity-mixin.dockerfile runs the
unmodified install in a build stage on the workload's own base and copies
/home/agent/.local into a FROM scratch overlay at the path it was built
for.
$ sbx create --kit <shell-workload> --kit ./antigravity-mixin
$ agy --dangerously-skip-permissions
ENTRYPOINT: the base workload's stays, and
agy is something you run from its shell — which is also where
--dangerously-skip-permissions, carried by the standalone kit's CMD, has
to be passed by hand.com.docker.sandboxes.start-docker because it owns a base that carries an
engine. An overlay setting it would ask for Docker mode over a base that may
have nothing to run, so the base declares it.AGENTS.md profile, sbx@1 and the sandbox identity, and the
platform floor — bash, the agent user, git, a CA store.antigravity and antigravity-mixin both provide antigravity, so they are
alternatives: composing the two together is refused, one capability having one
provider.