Skip to content

Antigravity

meshpoint connect antigravity

installs one meshpoint group in ~/.gemini/config/hooks.json with handlers for SessionStart, PreInvocation and Stop, and the skill at ~/.gemini/config/skills/meshpoint/SKILL.md. With --project <repo> the group goes to <repo>/.agents/hooks.json and the skill to <repo>/.agents/skills/meshpoint/.

Antigravity’s payloads are camelCase and carry no event name, so each handler runs meshpoint tap antigravity <Event> with the event as an argument.

  • Recall is injected once per conversation as an injectSteps system message, keyed by conversationId under ~/.local/state/meshpoint/antigravity/.
  • PreInvocation with invocationNum 0 spools lastUserInput as the user turn, deduplicated, since every model call repeats it. invocationNum is zero-based.
  • Stop spools the reply with the files its tool calls touched, answers {"decision":"continue","reason":...} once when a checkpoint is due, and sends the spool at once when fullyIdle is true.
  • There is no session-end or compaction event; the idle flush covers it.

Ported from Antigravity’s published hook documentation; not yet run end to end against the platform. Unconfirmed:

  • the transcript.jsonl line schema (the reader accepts Gemini-shaped and generic records; without per-line timestamps the nudge never fires),
  • a community report that Stop hooks did not fire in one IDE build.

If you run Antigravity with Meshpoint, a meshpoint doctor output and the spool file after one session are enough to confirm or correct these.