How to get notified when Antigravity CLI finishes

Quick setup: which Antigravity CLI alert do you want?

Option 1: Antigravity CLI's built-in notifications setting

Antigravity CLI keeps its persistent settings in ~/.gemini/antigravity-cli/settings.json, and writes only the values that differ from the defaults. The notifications setting is a boolean that defaults to false. Turn it on in the file:

{
  "notifications": true
}

Or open /config (alias /settings) inside the CLI and switch Notifications on. Google describes it as a system desktop notification plus a terminal bell chime when a long-running task completes or requires your attention. Since CLI 1.3.1 the CLI also alerts you when the agent stops to ask a question, the same way it does for tool permission prompts. The command you launch the CLI with is agy.

What you get: an alert on the machine running the CLI. Google's docs give no setting for the wording, the sound or a phone push, so for those use a hook. If you run both the setting and a hook, you get two alerts when a run finishes. Separately, CLI 1.4.0 (16 Oct 2026) added terminal status reporting over OSC 7501: in terminals that support it, the tab or window shows whether the CLI is working, waiting for your input, done or failed. It is a status display, not a notification, and AGY_CLI_OSC7501=off turns it off.

Option 2: a Stop hook in ~/.gemini/config/hooks.json

Google's hooks docs let Antigravity CLI read hooks from three places: .agents/hooks.json at your project root, ~/.gemini/config/hooks.json for every project, or the hooks.json inside an installed plugin. The global hooks can also sit inside ~/.gemini/antigravity-cli/settings.json, but the docs don't show the key layout there, so this guide uses hooks.json. The docs write every path with ~ and give no separate Windows path, so on Windows it is the same path under your home folder. This guide uses ~/.gemini/config/hooks.json. Type /hooks inside the CLI to see what it loaded.

The file maps a hook name you choose to its events, plus an optional enabled flag (default true). PreToolUse and PostToolUse take entries with a matcher and a hooks list. SessionStart, PreInvocation, PostInvocation and Stop take a list of handlers directly. A handler has a command (required), a type (only command exists) and a timeout in seconds, 30 by default. This is the shape, after Google's example:

{
  "hook-name": {
    "enabled": true,
    "PostToolUse": [
      {
        "matcher": "run_command",
        "hooks": [
          {
            "type": "command",
            "command": "./scripts/lint.sh",
            "timeout": 10
          }
        ]
      }
    ],
    "Stop": [
      {
        "type": "command",
        "command": "./scripts/after-run.sh"
      }
    ]
  }
}

Antigravity CLI has no AfterAgent or Notification event, and no event for a permission prompt, so a hook can tell you a run ended but not that the agent is waiting on you. Use Option 1 for that. Stop writes one JSON object to the handler's stdin (field names are camelCase); the values below are illustrative:

{
  "conversationId": "7f3c0b1e",
  "workspacePaths": [
    "/home/you/my-app"
  ],
  "transcriptPath": "/path/to/transcript",
  "artifactDirectoryPath": "/path/to/artifacts",
  "modelName": "your-model",
  "executionNum": 1,
  "terminationReason": "model_stop",
  "fullyIdle": true
}

• terminationReason says why the run stopped. Google's examples are model_stop, max_steps_exceeded and error, so treat the list as open. error is present when a system error ended the run.
• fullyIdle is true only when the agent is completely finished and every background command or async task has completed, and false while background work is still running. A script can read it, but Google doesn't say whether another Stop follows when it is false, so skipping the alert on false may lose it for good. That is why anotifier alerts on every Stop.
• workspacePaths lists the project folders, so a script can put the project name in the alert.

What Stop must print: a JSON object on stdout with a decision. "decision": "continue" keeps the agent running and re-enters the loop, injecting an optional reason as a system message; any other value lets it stop. Google marks decision as required, so a notification hook should print {"decision":"stop"} and nothing else.

Antigravity CLI desktop toast and sound by OS

Each hook below is a small script that shows the toast, plays the sound and prints the stop answer, so the command in hooks.json stays one program call. The scripts read nothing from the payload. Replace you with your user name.

macOS. Save as ~/.gemini/hooks/notify.sh. osascript notifications are attributed to Script Editor, and if Script Editor isn't allowed to send notifications the toast silently fails. afplay plays any .aiff, .mp3 or .wav.

#!/bin/sh
cat > /dev/null
osascript -e 'display notification "Run finished" with title "Antigravity CLI"'
afplay /System/Library/Sounds/Glass.aiff
echo '{"decision":"stop"}'
exit 0

{
  "notify": {
    "Stop": [
      {
        "type": "command",
        "command": "sh /Users/you/.gemini/hooks/notify.sh",
        "timeout": 10
      }
    ]
  }
}

Linux. Same file name, with notify-send and paplay. notify-send needs a desktop notification daemon, which servers, containers and SSH sessions without a desktop lack, and paplay needs PulseAudio or PipeWire with the freedesktop sound theme.

#!/bin/sh
cat > /dev/null
notify-send 'Antigravity CLI' 'Run finished'
paplay /usr/share/sounds/freedesktop/stereo/complete.oga
echo '{"decision":"stop"}'
exit 0

{
  "notify": {
    "Stop": [
      {
        "type": "command",
        "command": "sh /home/you/.gemini/hooks/notify.sh",
        "timeout": 10
      }
    ]
  }
}

Windows. Save as C:\Users\you\.gemini\hooks\notify.ps1. It needs no module, runs on Windows PowerShell 5.1, and is the same toast as in the WSL toast guide. PlaySync waits for the chime to end so PowerShell doesn't exit first; any .wav in C:\Windows\Media works. In the JSON, write the path with forward slashes so it needs no backslash escapes:

$ErrorActionPreference = 'SilentlyContinue'
$null = [Windows.UI.Notifications.ToastNotificationManager, Windows.UI.Notifications, ContentType = WindowsRuntime]
$null = [Windows.UI.Notifications.ToastNotification, Windows.UI.Notifications, ContentType = WindowsRuntime]
$AppId = '{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\WindowsPowerShell\v1.0\powershell.exe'
$xml = [Windows.UI.Notifications.ToastNotificationManager]::GetTemplateContent([Windows.UI.Notifications.ToastTemplateType]::ToastText02)
$texts = $xml.GetElementsByTagName('text')
$null = $texts.Item(0).AppendChild($xml.CreateTextNode('Antigravity CLI'))
$null = $texts.Item(1).AppendChild($xml.CreateTextNode('Run finished'))
[Windows.UI.Notifications.ToastNotificationManager]::CreateToastNotifier($AppId).Show([Windows.UI.Notifications.ToastNotification]::new($xml))
(New-Object Media.SoundPlayer 'C:/Windows/Media/chimes.wav').PlaySync()
'{"decision":"stop"}'
exit 0

{
  "notify": {
    "Stop": [
      {
        "type": "command",
        "command": "powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:/Users/you/.gemini/hooks/notify.ps1",
        "timeout": 10
      }
    ]
  }
}

• Run chmod +x on the shell script, or keep the sh in front of the path as above.
• The Windows toast shows under the name Windows PowerShell, with no Antigravity icon or click-to-focus. If nothing appears, Do not disturb (Focus Assist) may be on.
• A hook runs on the machine where agy runs. Over SSH, notify-send and afplay act on the remote machine, so use phone push there.

Antigravity CLI alerts on your phone with ntfy

ntfy is a free, open-source push service with Android and iOS apps and no account. Install the app, subscribe to a long random topic name, and add one line to the script, before the stop answer. -s -o keeps curl's reply off the hook's stdout, where only the stop JSON belongs. On macOS and Linux:

curl -s -o /dev/null -d 'Antigravity run finished' -H 'Title: Antigravity CLI' https://ntfy.sh/your-topic

On Windows use curl.exe, because curl is an alias for Invoke-WebRequest in Windows PowerShell 5.1:

curl.exe -s -o NUL -d 'Antigravity run finished' -H 'Title: Antigravity CLI' https://ntfy.sh/your-topic

Keep the text generic, or run your own ntfy server before putting anything about your work in the body. The ntfy phone push guide and the phone page cover private topics, self-hosting and priorities.

Option 3: anotifier, one command

npx anotifier@latest setup

Antigravity CLI support arrived in anotifier 1.4.0 and is in the current release, 1.7.1. Setup wires it when a ~/.gemini/antigravity-cli folder exists. It backs up an existing ~/.gemini/config/hooks.json to ~/.anotifier/backups/, then adds one top-level group named anotifier with a Stop handler (30-second timeout) beside your own groups. If you muted that group with "enabled": false, or tuned its timeout, running setup again keeps both. The path in command is where anotifier is installed:

{
  "anotifier": {
    "Stop": [
      {
        "type": "command",
        "command": "node \"/path/to/anotifier/src/notify.mjs\" --source antigravity --event Stop",
        "timeout": 30
      }
    ]
  }
}

A finished run sends "Task complete", titled my-app · Antigravity; the project name is the name of the first folder in workspacePaths. The hook always answers {"decision":"stop"}, even when a channel fails or you have snoozed notifications, so it can never keep a run going. The alert goes to every channel you enabled: a desktop toast on Windows, macOS, Linux or WSL, an ntfy push to your phone, a Slack, Discord, Telegram or other webhook, and a terminal bell. Setup does not touch the notifications setting from Option 1.

npx anotifier@latest uninstall removes only the handlers anotifier added to hooks.json; your own groups stay. anotifier snooze 2h silences every channel for two hours. For what setup writes for each agent, see the Antigravity CLI page. What anotifier does not do for Antigravity:

• No needs-input alert. Antigravity has no hook event for permission prompts. Finished runs only.
• An error or a cancel also says "Task complete". anotifier does not read terminationReason or fullyIdle, so every Stop alerts, even one with background work still running.
• Generic text. anotifier does not read the transcript for Antigravity, so the alert never quotes what the agent said.
• Not tested against a live Antigravity CLI yet. The hook wiring and payload parsing are unit-tested against Google's hooks docs, and there is no live Antigravity lane in CI. Run npx anotifier@latest test to confirm your channels work, then check that a real run alerts you.
• The 2.0 app and the IDE. Google's docs say both read the same global ~/.gemini/config/hooks.json, so a handler setup wrote should fire there too. But setup only wires Antigravity when ~/.gemini/antigravity-cli exists, and neither app has been tested.

Antigravity CLI notifications not working: fixes by symptom

Gemini CLI vs Antigravity CLI: which setup applies

Google replaced Gemini CLI with Antigravity CLI on June 18, 2026: Gemini CLI stopped serving Google AI Pro and Ultra subscribers and free Gemini Code Assist users. It stays available with a paid Gemini API key or a Code Assist Standard or Enterprise license. Google's announcement says hooks are among the features carried into Antigravity CLI, but the setup differs.

Antigravity's hooks docs list only the files above, not ~/.gemini/settings.json, so an AfterAgent hook there won't fire in Antigravity CLI. For the Gemini CLI side, see the Gemini CLI notifications guide. anotifier handles both at once: its Gemini CLI entries stay in ~/.gemini/settings.json until you remove them with npx anotifier@latest uninstall.

Sources

Each Antigravity CLI claim above comes from Google's official docs or release notes, read on 2026-10-16 when the latest CLI release was 1.4.0. Settings and hooks change between releases, so confirm anything you rely on there.

• Hooks: file locations, events, handler fields, the Stop payload and answer, and the /hooks command: antigravity.google/docs/hooks
• The notifications setting and the location of settings.json: Google's settings and CLI commands reference pages (type and default are in the reference)
• Question alerts under the notifications setting (CLI 1.3.1) and terminal status reporting (CLI 1.4.0): the antigravity-cli release notes
• The agy command: Google's Antigravity CLI codelab
• Gemini CLI and Antigravity CLI: Google's transition announcement
• Hooks not firing in the IDE on Windows: a Google AI Developers Forum report from August 2026, unresolved
• anotifier 1.7.1: patch-config.mjs, parse-input.mjs, notify.mjs, the README and the docs

Try it

One command wires Antigravity CLI and every other agent you have installed.

npx anotifier@latest setup

Other guides

Claude CodeCodex CLICursorGemini CLIClaude Code permissionsClaude Code soundsClaude Code usage limitsClaude Code auto-compactClaude Code hooks securityccnotifyCodex CLI soundsWindows & WSLmacOS & LinuxAgent hooksTroubleshootingntfy phone pushWSL Windows toast