Skip to main content
Coming soon in onboarding. Antigravity appears as Coming Soon in the terma setup and terma install agent pickers. You can wire its hooks today with terma install --adapters antigravity; the capabilities below describe what that captures.
Google’s Antigravity CLI (agy) replaced Gemini CLI for many users in June 2026. It has no configurable OpenTelemetry export, so everything Terma learns about an agy session arrives through the lifecycle hooks Terma writes into the repository. Support is partial: commits are attributed and every tool step is recorded, but agy reports no token counts or cost.

​
Set up

In a repository you have already installed Terma in:
A repository that already has one of agy’s customization directories (.agents, .agent, _agents, or _agent) gets the hooks by default. Commit the updated .agents/hooks.json. Terma owns one named hook in that file, terma, holding PreInvocation, PostToolUse, PostInvocation, and Stop. Every other named hook is preserved, and terma uninstall removes only Terma’s entry. If you set "enabled": false on Terma’s entry, a reinstall keeps it and terma doctor reports it.

​
Make sure the hooks run

agy runs a workspace’s hooks only under two conditions, and terma doctor checks both:
  • Trust. You must trust the workspace from inside agy.
  • Workspace binding. Hooks belong to an agy project, not to the directory you started in. An agy started in a folder that is not one of its projects works in a scratch “CLI Project” and loads no repository hooks. Open the repository as a project, or in print mode pass --add-dir <repo>.

​
What’s captured

Treat Antigravity data in Terma as evidence of activity, not usage or spend. agy has no session-end hook, so a session is closed after a period of inactivity.

​
Verify