@raidiant/notifai weekly downloads statistics

Notifai for Claude Code, Codex & more

Your agents can reach you, and you can answer from your phone. The answer goes back to the exact Agent Session that asked, in whichever harness it runs: Claude Code, Codex, Cursor, OpenCode, OpenClaw, Hermes or Grok.

An agent working while you are away has no way to reach you, so it either guesses or sits blocked in a terminal nobody is watching. notifai gives it a way to tell you something finished, and a way to ask you a question and get your answer back as a banner on your phone. Notifications name the Project and Agent Session they come from, so you know which one needs you.

Your agent sets it up. Paste this into any agent:

Set up Notifai: https://app.notifai.sh/setup.md

Website: https://notifai.sh

To do it yourself, use the native installer for your computer; it installs Notifai and starts setup. No Node.js or npm needed.

# macOS / Linux / WSL
curl -fsSL https://notifai.sh/install.sh | sh

# Windows PowerShell
irm https://notifai.sh/install.ps1 | iex

Setup defaults to QR approval with your signed-in Companion App; notification and browser approval are selectable alternatives. Run notifai init to resume. See installation and migration for agent-safe script inspection, platform prerequisites, channel selection and legacy npm migration.

Optional Node/npm launcher, once its replacement package and matching native release are verified as published:

npx --yes @raidiant/notifai@latest init
# Or: npm install -g @raidiant/notifai, then notifai init

Requires Node.js 20.12 or newer for this launcher. Notifai installs its own native runtime. Use notifai update for runtime updates. npm updates/removes only the launcher; notifai uninstall removes the runtime after its safety checks. Existing native versions and channels survive launcher changes. @version selects launcher code, not a command to replace an existing runtime.

Run notifai doctor or notifai update --check --json to check for a newer CLI and inspect release notes, guidance, and session requirements. Enabled Projects give root agents a quiet update offer at most once every seven days across the machine. A release does not install itself or restart an Agent Session automatically. The package includes its changelog.

Use notifai update for later global updates. It repairs the installation the shell actually selects and keeps the stable hook adapter on that same CLI. It fails instead of moving the command to a different PATH slot when it cannot verify the selected installation or retarget an existing adapter safely.

init walks the setup one step at a time and tells you the single next thing to do. Run it again after each step; it works out what remains.

At a human terminal, init asks once whether this setup is for this project or for every project on this machine. That answer is skill, hooks, and config together. Pairing, devices, and credentials stay on this machine either way. An unattended caller passes the same choice as a flag: notifai init --setup-scope project or notifai init --setup-scope global. --skills-scope is an alias of that flag when --skills is set. Shared project config may live in the repo; personal project preferences live under the user config directory and never require a .gitignore edit.

Telling you something happened

notifai send --kind done \
  --title "Deploy finished" \
  --summary "The staging deployment is live." \
  --body "The staging deployment is live and ready for review."

Write a brief title whose substance is immediately understandable; type lives in --kind, and Project identity is inferred from the invocation directory. Every Notification Request has a purpose-written, one-line plain-text Summary for native banners and list views. It is required and limited to 240 Unicode characters. Body is optional standalone Markdown for focused detail; when it is absent, the focused view shows Summary. Use --body-file <path|-> for long content. Repeat --image for an ordered image collection (up to eight) and pair each with --image-alt. Every attached image appears in the gallery; to place one where the words refer to it, write Markdown image syntax with its 1-based position, ![what it shows](media:1). A bare media:1 or a link to it is refused before sending.

Asking you a question

notifai ask "Deploy the migration to production?" \
  --choice Yes --choice No

The agent registers the question and starts background submission immediately; it can continue independent work while your answer is outstanding. Registration alone does not prove Provider Acceptance. Question Routing keeps the exact Agent Session's answer path for the complete answer window. Claude Code and Codex observe answers out of band. Codex queues a wake-up, then drains current notes and answers together at a supported hook or notifai receive boundary. Queue success proves wake storage, not presentation.

By default submission begins without waiting for the turn to end (ask_grace_seconds = 0). Set a positive grace period for a terminal-only answer window first.

When you answer, the agent acknowledges it before it does anything else, so you find out your reply landed and what it set in motion — not just that you sent it. Answering from your phone and wondering whether anything happened is the whole problem this solves.

For a harness that cannot resume an idle agent turn, notifai send --reply owns the complete answer window in the foreground: keep it alive and set --reply-timeout equal to --reply-window. After a timeout, retain the request ID and inspect that original with notifai replies and notifai status; never send a duplicate.

Agent harnesses…