Notifications for multiple coding agents and projects

A build in one repository can finish while another agent waits for permission and a backup job reports a failure. Give each source a recognizable name and use a concise title and project context. A useful alert tells you what needs your attention, rather than repeating an entire terminal transcript. Ntfyx receives ordinary messages and individual questions in the same Inbox.

Use Ntfyx CLI 0.1.2 on macOS or Linux and a compatible primary phone app. The iPhone app is awaiting App Store review. Android 1.0.0 is in Google Play production review and available to configured Internal testers. Neither status announces public store availability. Android push requires Google Play services.

The phone authorizes each computer or server as its own Source; an optional Web Inbox receives new messages after phone authorization.

curl -fsSL https://ntfyx.me/install.sh | bash
ntfyx connect
ntfyx topics

• Downloads and current availability
• Pair your first computer

Free includes one active Topic. Multiple authorized Sources can use it; you do not need a paid Topic for every computer, agent or repository. A Source is a separately authorized sender with its own keys. Plus increases active Topic capacity to twenty; it does not multiply the message allowance or promise unlimited traffic.

ntfyx topics
ntfyx send "Website build passed" --title "Website" --topic Work
ntfyx send "Backup failed: inspect the server log" --title "Backups" --topic Work

• Source, receiver and message limits
• Free and Plus

Run connect on each trusted computer or server and authorize it from the phone. A source on a server can be revoked without giving that server the management root. Do not clone your desktop credentials onto every host. Agent and project labels identify messages; if two agents must be revoked separately, pair separate Source identities.

ntfyx connect
ntfyx sources

• Phone authority and revocation

If builds, client work and server operations need distinct routing, use named Topics. Creating or activating a second Topic requires Plus. Within one CLI configuration, local aliases select which connection send and ask use; adding an alias does not automatically create or grant a server Topic. Choose an existing alias from topics before running these examples.

ntfyx send "Ready to review" --topic Work
ntfyx ask "Which environment should I inspect?" \
  --choice staging=Staging --choice production=Production --topic Work --json

Use send for status updates and ask only when a person needs to decide or provide information. Optional quiet hours pause push alerts while synchronization and replies remain available. A short request can expire during quiet hours, so choose a lifetime that matches the workflow. Multiple devices can attempt to answer; the service arbitrates one accepted answer, and the sender must verify it before proceeding.

• Agent questions, timeouts and choices
• Authorize a browser Inbox

Ntfyx is a personal Inbox with one active primary phone and up to two authorized browsers, not a team on-call system. There is no current shared team roster, escalation schedule or multi-person approval policy. Native approval adapters are limited to documented tools, host versions and platforms. Use the explicit ask/MCP path for questions in other workflows.

• Verified agent compatibility
• SSH and remote server jobs