Antigravity

Antigravity sessions, visible outside the editor

Your Antigravity agent conversations in the notch, read straight from local transcripts.

Download for FreeFree 3-day trial · Apple silicon

01

Zero setup, by design

Antigravity needs no hooks: AgentPeek tails the transcript files Antigravity already writes under ~/.gemini/antigravity, checking every few seconds. Start a conversation and it appears in the notch alongside your other agents, with state (executing, waiting, or idle) inferred from how recently the transcript moved.

02

A window, not a remote control

Antigravity sessions are view-only: AgentPeek reads the transcripts but can't answer prompts or send follow-ups into Antigravity, and the transcripts carry no token or quota data, so there are no usage numbers to show. What you get is the part that matters when Antigravity runs agents in the background: knowing they exist, seeing what they're doing, and noticing when one goes quiet, without keeping the editor's agent manager open.

03

Alongside everything else

The point of one monitor is not per-tool novelty; it's that Antigravity, Claude Code, and Codex sessions sit in the same list, the same board, and the same attention flow. Quick Routes opens the Antigravity brain logs and root folder when you want the raw files.

Questions, answered.

Yes. AgentPeek reads the transcript files Antigravity keeps on your Mac and shows each conversation as a session in the notch, with state inferred from transcript activity. No hooks or configuration needed.
No. Antigravity transcripts carry no token or quota data, so its sessions appear without usage numbers. Session visibility and attention flow still work.
No. Antigravity sessions are view-only: AgentPeek shows the conversation and its state but has no channel to answer prompts or send follow-ups into Antigravity.

Your agents, one glance away.

Download for FreeFree 3-day trial · Apple silicon