anotifier for Gemini CLI.

Setup wires Gemini CLI when a ~/.gemini folder exists. It backs up settings.json to ~/.anotifier/backups/ and adds one entry per event. Gemini CLI takes the timeout in milliseconds:

{
  "hooks": {
    "AfterAgent": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node \"/path/to/anotifier/src/notify.mjs\" --source gemini",
            "timeout": 30000
          }
        ],
        "_managed_by": "anotifier"
      }
    ]
  }
}

Notification gets an identical entry. Older anotifier versions wrote a separate ~/.gemini/hooks.json; setup removes those stale entries, because Gemini CLI reads hooks from settings.json.

Antigravity CLI keeps hooks, in a new format. It reads them from its own files, such as ~/.gemini/config/hooks.json or a workspace's .agents/hooks.json, and its events are SessionStart, PreToolUse, PostToolUse, PreInvocation, PostInvocation and Stop. There is no AfterAgent or Notification event, so the hooks anotifier writes for Gemini CLI don't fire there. anotifier 1.4.0 and later wire Antigravity CLI separately: run npx anotifier setup and, when ~/.gemini/antigravity-cli exists, it adds one group named anotifier with a Stop handler to ~/.gemini/config/hooks.json, beside any groups of your own, after backing up an existing file. A finished run sends "Task complete", titled <project> · Antigravity. Google's Antigravity hooks docs describe the format.

Limits: Antigravity's hooks have no notification or permission event, so anotifier sends no needs-input alert for it, and a Stop caused by an error or a cancel also says "Task complete". For permission and question alerts, turn on Antigravity's own notifications setting, covered in the Antigravity CLI notifications guide. Google's docs say the Antigravity 2.0 app and the Antigravity IDE 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. Hook wiring and payload parsing are unit-tested against Google's hooks docs; anotifier has not yet been tested against a live Antigravity CLI.

The full Antigravity CLI setup, limits and FAQ are on the Antigravity CLI page, and the Antigravity CLI notifications guide covers the built-in setting and writing the hook yourself. The Gemini CLI entries stay in ~/.gemini/settings.json until you remove them with npx anotifier@latest uninstall, which removes only the handlers anotifier added to the Antigravity file.

• Tested end to end. CI installs Gemini CLI 0.50.0, runs a prompt with an API key, and fails unless the AfterAgent hook delivers a real ntfy push.
• The ding is a bell anotifier writes to the terminal Gemini CLI runs in, when it has one.
• Click-to-focus is Windows-only. Clicking the toast brings forward the window whose title contains the project folder. macOS, Linux and WSL toasts have no click action.

npx anotifier@latest test       # fire a test alert on every channel
npx anotifier@latest status     # show which agents and channels are set up
npx anotifier@latest doctor     # diagnose a channel that stays quiet
npx anotifier@latest uninstall  # remove the hooks setup added

test sends straight to your channels without going through Gemini CLI, so it proves the channels work. uninstall removes only the entries anotifier added and restores your statusline (1.5.0 and later), and setup keeps a copy of every file it changes in ~/.anotifier/backups/.