Skip to main content

Antigravity Runtime Integration

Google Antigravity is AG Kit's production runtime. Beyond rules, skills, and workflows, the kit ships a native integration layer inside .agents/.

The runtime layer

antigravity.json
Machine-readable runtime contract
hooks.json
Native PreToolUse safety gate
mcp_config.json
Workspace MCP source of truth
Doctor
Read-only integration diagnostics

Tool safety hook

hooks.json registers a native PreToolUse gate for run_command. It is deliberately narrow — it blocks high-confidence destructive patterns only:

  • Unix root-filesystem deletion (rm -rf / and equivalents)
  • Filesystem formatting and raw-disk overwrite (mkfs, writing to /dev/sdX)
  • Windows drive formatting and forced root deletion

Normal project cleanup (deleting dist/, node_modules/) passes through.

The hook does not replace Antigravity permissions, workspace trust, sandboxing, or human approval. It is a last-resort tripwire, not a security boundary.

MCP synchronization

.agents/mcp_config.json is the workspace source for MCP servers. The sync helper applies it explicitly — it refuses placeholder credentials, preserves conflicting entries by default, and backs up the target before writing:

agent-session

Antigravity Doctor

The Doctor checks discovery, MCP, hooks, orchestration, plugin packaging, and release readiness — read-only:

agent-session
[PASS] discovery [PASS] mcp [PASS] hooks [PASS] orchestration [PASS] plugin [PASS] validation [PASS] Antigravity contract is ready.

Plugin bundle

For teams who prefer a packaged install, the plugin builder produces a local Antigravity plugin bundle with a deterministic SHA-256 content inventory:

agent-session

Everything on this page is validated in CI: the Doctor, hook regression tests, and plugin inventory run on every push.