Stop watching your agent work.
Get pinged instead.

Claude Code, Codex CLI and Google Antigravity CLI today — all fully supported, and any combination of them on the same machine at once. Antigravity CLI needs version 1.1.12 or newer.

You pick which agents to connect when you install, and each one shows its own status on your dashboard. A machine only reports an agent as connected once that agent has actually sent an event — never just because another agent on the same machine did.

All of them are terminal tools. Pager9 works by installing a lifecycle hook, and only the command-line versions have one — so it does not work with claude.ai, the Claude desktop app, or any chat in a browser tab.

Yes — one step, and it happens inside Codex. After you install, open Codex and run /hooks, then approve Pager9. That is Codex's own security step: it will not run a hook you have not approved, and Pager9 cannot approve it for you.

Until you do it, Codex skips the hooks silently — no notifications, no error message, and nothing on the dashboard to tell you something is wrong. It looks exactly like a quiet day.

If you skipped it, re-running the setup command will not ask again — it writes the same hook definition, so Codex considers the question already answered. The only way in is opening Codex and running /hooks. You can check the state any time with pager9 doctor, which reports whether Codex has a trust record for each hook.

Claude Code and Google Antigravity CLI have no equivalent step — their hooks load as soon as they are written.

Claude Code is Anthropic's coding tool that you run in your terminal — the command line (CLI) — on your own computer. It's not the Claude web app (claude.ai) or the Claude desktop chat app; it's a separate program that works inside your project, right where your code lives. Here's what it looks like running: Pager9 hooks into that terminal session — so the moment Claude Code finishes a run or needs your input, your phone gets pinged. Codex CLI and Google Antigravity CLI work exactly the same way — you launch them by typing codex or agy.

Install the app, then run one command on the computer where you use Claude Code, Codex CLI or Google Antigravity CLI. About 30 seconds, once. The dashboard hands you the exact line to paste for your shell — PowerShell, cmd, or Mac/Linux — so there's nothing to look up and nothing to type from memory. It needs no Node and no npm (there's an npx pager9 option too, if you prefer it), and it installs the hooks for the agents you picked: no config files to edit and nothing left running in the background. Claude Code needs no restart, and neither does Antigravity CLI — for Antigravity, Pager9 writes only its own entry into that agent's global hook config and leaves everything else in the file alone. Codex asks you to approve the hook once, in its own /hooks screen, which is Codex's security step and not something we can or should skip for you. After that you never touch it again — you just start getting pinged.

Yes — tested with the screen off, the phone in Doze, and the app killed. It lands as a native system notification, so the phone wakes for it. The honest limit: Do Not Disturb or force-stopping the app can silence it — that's your phone choosing quiet, not Pager9 failing.

No. No prompt content, no code, no transcripts, no file contents ever leave your machine. Pager9 sees only event names, timestamps, and a project name — enough to know a run finished or needs you. More in our Privacy policy.

Pager9 installs a hook into the agent — Claude Code, Codex CLI or Google Antigravity CLI, the agentic coding tools that run in your terminal. They fire lifecycle events as they work; Pager9 turns the ones that matter — finished, or waiting on you — into a push to your phone. That's also the answer to a question people ask next: it works with the command-line tools specifically, and not with Claude in a browser tab (claude.ai) or the Claude desktop chat app — those have no hooks to install into.

No. Notifications arrive with the app fully closed — that's the whole point. Install it once, then forget it's there until it pings.

Pro is $7.99/month after a 7-day free trial, sold through Google Play inside the Android app. Early access is still free to use while the app goes out to a limited group of testers. One subscription covers your whole account, and you’ll need the Android app to start a trial or subscribe — see Pricing.

One command on the machine, and it's out of your agents: Run it with no flags first and it just shows you what it would remove — it changes nothing until you add --yes. It takes Pager9's hooks out of every agent on that machine and backs up each config first, leaving everything else in those files exactly as it was. Use pager9 uninstall claude, pager9 uninstall codex or pager9 uninstall antigravity to remove just one.

Your machine stays paired, so pager9 setup claude, pager9 setup codex or pager9 setup antigravity turns notifications back on with nothing to re-enter. To remove the pairing too, use pager9 reset — and you can revoke the machine's key from the dashboard at any time.

Each machine gets its own key, so you revoke a leaked one without touching the others. Install tokens mean the raw key is never shown, pasted, or left in your shell history — and a key can only send you pings, never read your data.

Android only, for now. The Pager9 app is on Google Play — that's the one to install, because a native Android app is what buys you delivery with the screen off, the phone in Doze and the app killed. You can also just use it in any browser as a PWA. iOS isn't here yet — it may come later, but we won't put a date on it or pretend it exists before it does. (The computer side is any OS that runs Claude Code, Codex CLI or Google Antigravity CLI: macOS, Linux or Windows.)