Antigravity,
in your notch.
Google Antigravity CLI notifications on your Mac, with the command it asks about
Gnista shows every agy session in your MacBook’s notch: what it’s doing, when it’s done, and when it asks permission, with the command it wants to run. One click takes you to the tab to answer.
Gnista with Antigravity, at a glance.
- Where it runs
- The Antigravity CLI,
agy, in any terminal, Antigravity’s IDE and app, which read the same hooks, and Antigravity in Xcode (how). - Setup
- A named hook,
gnista, in~/.gemini/config/hooks.json, after a backup, and the same in the hooks file of Antigravity in Xcode. - Needs you
- Permission requests, with the command or file, within a second of Antigravity asking.
- Answer from the notch
- No: Gnista shows the request, and a click takes you to
agyto answer it. - Reply from the notch
- Typed into its terminal: Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
- In the row
- The conversation’s title, your prompt, the reply and the tool in use, from Antigravity’s own records.
- Subagents
- Shown on the session’s row while they work, including ones started in earlier turns.
- Cost and limits
- Neither: Antigravity records no tokens and keeps its quota in memory, so Gnista doesn’t guess.
Know exactly what it’s asking.
No Antigravity hook says it needs you, so Gnista reads agy’s own conversation as it goes. Within a second of it asking, the row says what for: “Antigravity wants to run npm test”.
One click to the tab.
Answering from outside would mean holding Antigravity before every tool, asked or not. Gnista won’t slow it down for that: a click lands you in the exact tab, ready to answer.
Subagents, not lost.
When Antigravity hands work to subagents, they show on the session’s row while they work, even ones it started a few turns ago.
What it can’t do with Antigravity, and why.
- Answering from the notch: Antigravity’s only hook that can decide runs before every tool and holds the agent, so Gnista leaves it alone. You answer in
agy. - Tokens, cost and plan limits: Antigravity’s transcript has no tokens, and
agykeeps its quota in memory.
Connected in a minute.
- Open Gnista and tick Antigravity.
- Gnista backs up
~/.gemini/config/hooks.jsonand adds its own named hook,gnista. Other hooks there are left alone. - Start
agyin a project. It asks you to trust the folder once; say yes, and its sessions show in the notch.
Antigravity, asked and answered.
Can I approve Antigravity from the notch?
No. Its only hook that can decide runs before every tool and holds the agent, so Gnista leaves it alone. The notch shows the request; you answer in agy.
Does it work with the Antigravity IDE or app?
Yes. They read the same hooks file as agy, so one connection, Antigravity (CLI, IDE and app) in Settings, covers all three. Connecting also adds Gnista’s hook for Antigravity in Xcode.
Nothing shows when I start agy. Why?
agy. Why?Antigravity’s hooks first run when you send a prompt, not when agy opens, so the row appears with your first turn. Trust the folder when agy asks, then send one.
Does it show what Antigravity costs, or my limits?
No. Antigravity’s transcript has no tokens, and agy keeps its quota in memory, so there’s nothing for Gnista to read.
How do I remove it?
Settings ▸ Agents ▸ Antigravity ▸ Disconnect. Exactly Gnista’s hook goes; others in the file stay.
Gnista also keeps an eye on
Claude Code
Codex
Gemini CLI
Copilot
OpenCode
Devin
Qwen Code
Cursor
Mistral Vibe
CodeBuddy
Kimi Code
Codewhale
Droid
Qoder CLI
Kilo Code
MiMoCode
ZCode
WorkBuddy
Grok Build
Amp
Pi
Goose
Auggie
OpenHands
Trae
Aider
DeepSeek Harness
Wrote your own? It can report to Gnista with one line of JSON: custom agents.