Harness coverage
Antigravity CLI Telemetry in Beacon
Beacon supports Antigravity CLI endpoint telemetry through user-level and project-level hook adapters.
May 26, 2026
What is Antigravity CLI?
Antigravity support added hook coverage for prompts, tools, invocation, stop events, command execution, file edits, and diffs.
Collection path: Native hooks
Authoritative date: May 26, 2026 from v0.0.29 in the Beacon CLI changelog.
How Beacon reads Antigravity CLI
Beacon installs user-level hooks in ~/.gemini/config/hooks.json or project-level hooks in ./.agents/hooks.json, then normalizes Antigravity payloads through beacon-hooks.
The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.
Telemetry coverage
- Prompt, pre-tool, and post-tool events
- Invocation and stop events
- Command execution
- File edit and diff telemetry
What you can do now
- Capture Antigravity sessions without changing the local collector model.
- Use user-level or project-level hook installation.
- Preserve Antigravity under its canonical harness identity for queries.
Get started
- Run beacon endpoint hooks install --harness antigravity.
- Use --level project when repository-local hooks are desired.
- Check runtime.jsonl or the local dashboard after an Antigravity run.