Follow up Antigravity CLI upstream updates: persisted Agent Mode execution-mode key (v1.1.0) unauthorable in permissions override

[dyoshikawa]

Summary

One Antigravity CLI gap as of v1.1.8 (2026-07-28): the persisted default execution mode ("Agent Mode", added v1.1.0) in ~/.gemini/antigravity-cli/settings.json cannot be authored — rulesync's antigravity-cli permissions override copies exactly four autonomy keys and silently drops an execution-mode key that the looseObject schema happily accepts.

Window reviewed: CLI 1.0.4 (2026-06-01) → 1.1.8 (2026-07-28) via the canonical CHANGELOG, plus the current /docs/cli/* pages. All other dimensions verified at parity (see non-gaps).

Gaps

permissions — persisted default execution mode ("Agent Mode") unauthorable (global)

• Upstream: v1.1.0 (2026-07-08) added an Agent Mode option to /settings persisting a default execution mode (default, accept-edits, plan) into settings.json, explicitly so users need not pass --mode on startup; v1.1.4 (2026-07-18) made headless -p runs honor persisted settings.json policies (permissions, file access, sandbox mode, auto-execution, artifact review). — CHANGELOG
• rulesync (🌏): AntigravityCliPermissionsOverrideSchema (src/types/permissions.ts) declares toolPermission, enableTerminalSandbox, artifactReviewPolicy, allowNonWorkspaceAccess, and AntigravityCliPermissions.fromRulesyncPermissions copies exactly those four keys. An execution-mode key in the override validates (looseObject) and is then silently dropped on generate; toRulesyncPermissions never reads it back.
• Fix: add the execution-mode key to the override schema, writer, and importer alongside the existing four. Caveat: the settings reference has not yet been updated with the Agent Mode key (it also predates v1.1.8's copyOnSelect), so confirm the exact JSON key name against a real ~/.gemini/antigravity-cli/settings.json before implementing.

Non-gaps (verified, do not re-file)

• rules / mcp / commands / subagents / skills / hooks all at parity, including the v1.1.6 Markdown custom agents and v1.1.5 model frontmatter (already in AntigravitySubagentFrontmatterSchema) and the correct global roots (~/.gemini/config/agents/, ~/.gemini/antigravity-cli/skills/, ~/.gemini/antigravity-cli/global_workflows/).
• The permission action vocabulary (read_file, write_file, read_url, execute_url, command, unsandboxed, mcp) matches antigravity-cli-permissions.ts exactly; global-only scope remains correct (the only other store is ~/.gemini/config/projects/<uuid>.json, keyed by a per-machine UUID and not repo-authorable).
• Upstream issue #309 (CLI honors neither .geminiignore nor .antigravityignore) is an upstream defect — rulesync's .geminiignore output stays the right target.
• Upstream issue #627 (only command(*) matches; glob and regex: forms fail) contradicts the permissions doc — unresolved upstream, so rulesync's glob-style command(npm run *) emission stays as-is; re-check when chore(deps): bump the production-dependencies group with 63 updates #627 gets an official answer.
• Docs URL note for the research map: /docs/cli, /docs/changelog, /docs/rules, /docs/cli/rules, /docs/cli/workflows all 404 — CLI docs live at /docs/cli/{overview,using,features,settings,reference,permissions,plugins}.

References

• https://github.com/google-antigravity/antigravity-cli/blob/main/CHANGELOG.md — v1.1.0 Agent Mode, v1.1.4 headless policy honoring, v1.1.8 window end (the gap).
• https://antigravity.google/docs/cli/reference — settings table that lags the CHANGELOG (key-name caveat).
• https://antigravity.google/docs/cli/permissions — permission action vocabulary (non-gap) and the chore(deps): bump the production-dependencies group with 63 updates #627 contradiction.

[dyoshikawa]

Re-checked on 2026-07-30 with the intent to implement, but this remains blocked on the caveat already recorded in the issue: the exact JSON key name for the persisted Agent Mode execution mode is still not verifiable from public sources.

• /docs/cli/reference still lists only colorScheme, altScreenMode, toolPermission, artifactReviewPolicy, notifications, showTips, showFeedbackSurvey, editor, allowNonWorkspaceAccess, enableTerminalSandbox, useG1Credits, enableTelemetry, verbosity, runningLightSpeed — no execution-mode key.
• /docs/cli/settings likewise has no execution-mode key.
• The google-antigravity/antigravity-cli repo ships only CHANGELOG/README/examples (no source), so the key name cannot be read from code.

Implementing with a guessed key would emit a setting Antigravity ignores — the exact failure mode these follow-ups exist to prevent. Leaving open until one of: (a) the settings reference documents the key, or (b) someone captures a real ~/.gemini/antigravity-cli/settings.json written by /settings → Agent Mode on v1.1.0+. Once the key name is confirmed, the fix itself is mechanical: add it to AntigravityCliPermissionsOverrideSchema, the writer copy-list in AntigravityCliPermissions.fromRulesyncPermissions, and the importer.

[dyoshikawa]

Re-checked 2026-07-31: /docs/cli/reference still documents the same 14 settings keys with no execution-mode key, so the blocker recorded in the previous comment stands unchanged. Keeping this open until the key name is verifiable from the settings reference or a captured real settings.json.

[dyoshikawa]

Upstream update (re-check on 2026-08-06)

Additional or changed gaps

1. permissions — antigravity-cli has no project scope, but upstream merges project-level permissions since v1.0.5. The changelog entry for Antigravity CLI v1.0.5 (2026-06-03): "Integrated the permissioning system with the rest of Antigravity. CLI permissions now merges project level permissions, permissions from user settings shared with Antigravity, and permissions from the CLI settings.json." The project-level file is the committable workspace .antigravity/settings.json the IDE already writes (permissions.allow/ask/deny over the read_file / write_file / read_url / execute_url / command / unsandboxed / mcp vocabulary — permissions docs). rulesync's antigravity-cli-permissions.ts is hard-coded global (Target 'antigravity-cli' supports the feature 'permissions' only in global scope on dry-run), so CLI-only projects cannot get repo-shared permissions at all. Proposed follow-up: project-scope permissions for antigravity-cli emitting the shared .antigravity/settings.json, reusing the AntigravityIdePermissions conversion (the action vocabulary maps are already identical) and the fixed-order shared-file merge pattern used for Antigravity hooks/MCP/subagents; keep the global CLI file for the autonomy knobs. Matrix row → permissions ✅🌏.
2. docs drift — plugin subagents. antigravity-plugin subagents are implemented (agents/ dir wired, dry-run emits agents/*.md; upstream plugin docs list agents/ among components: docs/cli/plugins, docs/plugins), but docs/guide/plugin-packaging.md shows — in the Subagents column for antigravity-plugin and omits subagents from both example configs. Doc-only fix.

Verified unchanged

The Agent Mode execution-mode key blocker tracked here stands (still no verifiable key name in /docs/cli/reference). Hooks (5 events), MCP (serverUrl rename + timeout/disabled/disabledTools passthrough), subagent schema (v1.1.5/v1.1.6 fields), skills, and rules all re-verified in parity.

Housekeeping note: references/antigravity.md in the research skill predates Antigravity 2.0 entirely (claims no MCP/hooks/subagents/permissions surfaces exist upstream) and should be rewritten against the current docs tree.

References

• https://antigravity.google/changelog — CLI v1.0.5 permissions-merge entry
• https://antigravity.google/docs/permissions — action vocabulary + workspace settings file
• https://antigravity.google/docs/cli/plugins , https://antigravity.google/docs/plugins — plugin agents/ component