Antigravity

ACT supports Antigravity through the shared Gemini-family skill target at ~/.gemini/skills.

Install

cd ~/.agentic-coding-toolkit && ./scripts/install.sh --tool antigravity

Compatible Gemini CLI users can use the same skill target with:

cd ~/.agentic-coding-toolkit && ./scripts/install.sh --tool gemini

What Gets Installed

Location	Includes
`~/.gemini/skills/`	ACT skills

ACT installs skills for Antigravity. It does not install legacy slash-command files, agents, hooks, plugins, or implementation-plan artifacts for Antigravity.

Verify

Start Antigravity from the same environment where you installed ACT:

agy

Then run:

/skills

Confirm ACT skills appear in the list.

Skills

Invoke ACT skills directly by name:

/act-interview "add a settings screen"
/act-create-spec
/act-create-issues ai_specs/0001-settings/spec.md
/act-implement ai_specs/0001-settings/work-items/01-settings-screen.md
/act-git-push-make-pr

Permissions

For the strategy comparison, see Permissions & Safety.

Strategy 1: Permission rules

Configure Antigravity from Settings first. Use this Antigravity Permission Baseline when testing ACT:

Setting	Value
`Sandbox Mode`	`on`
`Tool Permission`	`proceed-in-sandbox`
`Non-Workspace Access`	`on`
`Artifact Review`	`asks for review`

Turn Non-Workspace Access on only when ACT needs to inspect or edit files outside the opened workspace. The tested local baseline used Non-Workspace Access: on because verification crossed workspace boundaries.

For CLI sessions, launch with:

agy --sandbox

This keeps CLI sessions aligned with the Antigravity Permission Baseline. For desktop or IDE sessions, use Settings instead of CLI flags.

Advanced CLI settings can be inspected here:

Platform	Settings file
macOS/Linux	`~/.gemini/antigravity-cli/settings.json`
Windows	`%USERPROFILE%\.gemini\antigravity-cli\settings.json`

The verified settings keys for this guidance are allowNonWorkspaceAccess and trustedWorkspaces.

Strategy 2: DSP / yolo + non-sudo account

Antigravity supports skipping normal permission prompts with:

agy --dangerously-skip-permissions

Use this only from a dedicated non-sudo account or another isolation boundary that does not contain personal files, broad SSH keys, production credentials, or unrelated project secrets.

Remote machines and containers

You can run Antigravity CLI workflows on a remote machine where that fits your setup. Treat the remote host as the isolation boundary.

Docker support depends on your Antigravity or Gemini CLI environment. See Permissions & Safety for the generic Docker strategy rather than treating containerized Antigravity as tested ACT guidance.

Troubleshooting

Recheck Settings for Sandbox Mode, Tool Permission, Non-Workspace Access, and Artifact Review.
For CLI sessions, restart with agy --sandbox after changing relevant settings.
Use agy --dangerously-skip-permissions only for the DSP / yolo strategy, not for the normal Permission Baseline.