Know when it’s done. Answer when it asks.

No. Ntfyx (ntfyx.me) and ntfy (ntfy.sh) are separate products with no affiliation. Ntfyx brings command and script notifications, agent questions and phone replies into one Inbox. ntfy is an HTTP publish/subscribe notification service with hosted and self-hosted options.

Phone notifications for Claude Code, Codex and scripts. Send to public Topics without pairing, or pair a protected Topic for encrypted CLI messages and verified phone answers. Its official website is ntfyx.me. Use an existing public Topic or a private HTTPS link for notifications; pair a protected Topic and the companion CLI for verified agent answers.

Use a protected Topic. Install the signed CLI, scan its connection QR with the phone app, then configure your agent. Claude Code can forward AskUserQuestion through its bridge. Codex and other supported MCP clients use explicit Ntfyx question tools. Supported permission hooks are a separate integration.

In a protected Topic, allow or deny one request, choose an offered option or type a text answer. Select Reply on the question to open a quoted composer. Your answer stays below that question, and the sending computer verifies the signed reply. Sending a reply does not prove an external action has completed.

Yes, for protected Topics. On Ntfyx iPhone and Android 1.6.0 or later, enable Call notifications in Settings and grant the required system permissions. CLI 0.4.1 can request --alert-mode call; local MCP uses alert_mode=call, and a JSON webhook can use ntfyx.alert_mode=call. It is an attention request for a message, not a voice call or permission to execute a task. Topic mute and quiet hours control eligible alerts. Android full-screen display depends on notification and channel permissions. iOS background registration lasts up to 24 hours and needs the app opened daily to renew; unavailable registration falls back to ordinary notifications. An already in-flight iOS system call can briefly appear before ending after a quiet-state change. Focus, system settings, network and delivery limits still apply; delivery or sound is not guaranteed.

Both provide local MCP question tools and phone-reply guidance. Completion hooks are available on macOS / Linux. Claude Code also bridges AskUserQuestion; Codex native request_user_input is not intercepted. Native execution approvals have verified Linux x64 support for Claude Code 2.1.283 / 2.1.284 and Codex 0.158.0; Apple silicon Mac native approvals are verified with Claude Code 2.1.303 and Codex 0.163.0 and require CLI 0.1.5+. Intel Mac native approvals remain unverified and return to the terminal. Codex requires interactive TUI and /hooks trust; codex exec does not trigger permission hooks. Claude setup permission hooks require --permissions on. Other MCP clients require host-specific configuration. This is not a hosted ChatGPT or Claude app-directory connector. On Windows, use direct CLI setup or local MCP. Claude Code hooks require 2.1.139+; an older or unknown version gets MCP only. Codex on Windows provides MCP questions without automatic hooks. The marketplace plugin uses POSIX shell hooks; use direct setup on Windows. Native tool permission approvals retain their separate platform and host policy.

A Topic groups messages from sources you authorize. Use the same session ID inside the same Topic to keep one task’s updates and replies in a Session conversation. Without a session ID, each new message starts a separate conversation. Grouping does not grant access to other Topics or export the agent’s whole transcript.

For verified agent answers: an iPhone or Android phone, plus a Windows, macOS or Linux computer with the companion CLI. Public Topic reading and sending need only an HTTP client or browser. HTTPS link notifications, hourly monitors and notification subscriptions need only the phone. Your phone can also authorize an optional Web Inbox. Android push requires Google Play services.

Yes, to an existing public Topic: anyone with its ID or link can read and send without a key. Public messages are visible to the service and link holders, and cannot request answers or Call reminders. A private HTTPS send-only link is another phone-only setup; the service reads that input before encrypted delivery.

Free includes 100 messages per UTC day, including up to 10 Call reminders and 10 answer requests, one monitor and one subscription. Notification-source subscriptions and public follows share the subscription allowance. Topic count is not a paid entitlement. Public Topics support ordinary and rich messages; protected Topics also support verified answers and Call reminders.

Protected Topic CLI and agent message titles, bodies, options and replies are end-to-end encrypted on your devices. Public Topic names and messages are readable by the service and anyone with the Topic ID or link. The explicit fixed monitor-access and webhook-management questions and their signed phone answers are disclosed to the service for verification. HTTPS push and webhook requests are readable by the service before encrypted delivery. Optional provider verification secrets are encrypted and stored by the service, then used in plaintext to verify the raw webhook body; they are hosted secrets, not hidden from the service. My Monitor reads the monitored address, rule and response; a public publisher knows the content it publishes. The relay routes ciphertext and processes operational metadata such as identifiers, time, size and push tokens. Do not put secrets in monitored URLs or request examples. Independent security review is not complete.

Ntfyx combines task messages, answers attached to the original question, and Topic/Session history with an opt-in notification marketplace. A workflow can wait for a verified confirmation, choice or text answer. Push services and bots have different reply, encryption and integration features; compare their current official documentation and the setup your workflow needs.

Yes. Open HTTPS Push on the phone to prepare MyNotify. The app generates a short sk_ send-only key and prepares your HTTPS sending link. Tap Send to receive hello, or copy the link. Open it with GET to send a notification using the final URL-encoded path segment, or keep the whole copied URL fixed and POST dynamic text, JSON or form content to it. No app update or CLI is required for that URL. CLI 0.3.0 and local MCP can create independent wh_ sending keys after separate phone-approved webhook management authorization; monitor permission does not grant it. Revoking management does not itself disable existing sending URLs. The HTTPS service processes this plaintext request, then encrypts the message for authorized receivers. Keep the whole sending link private because it includes your key. Rotate the key in the app to invalidate old links. It cannot read messages, manage the Inbox or receive agent replies.

Open Discover → My Monitor and add a public HTTP or HTTPS address. Checks run every hour and require a final HTTP 2xx status; optionally require the response to contain specified text or a simple JSON object field equal to a chosen primitive value. Every check result is grouped into one Session per service in the system My Monitor Topic. In app 1.5.3, preview text or JSON before entering your expectation. Only notify on failure is on by default: healthy results stay in the conversation silently; turn it off to receive an alert for every check. It does not consume your custom Topic allowance. The paired CLI and local MCP tools can manage these same items after explicit, revocable phone approval valid for up to 24 hours; the grant covers all My Monitor items. The monitoring service reads the address, rule and response. Individual scheduled outcomes are kept for seven days. For weeks with check activity, a non-silent English summary with emoji is scheduled for Monday at 00:00 UTC, reporting counts, completed-check success rate and response time, subject to mute and delivery settings. This is hourly monitoring, not real-time incident response or an SLA.

No. Open Discover in the iPhone or Android app, review a public notification source and confirm its subscription. No computer, CLI, pairing scan or Ntfyx account is needed. Receive future editions in its Topic; pause or unsubscribe from the phone. Each source lists its coverage and schedule. Private agent messages are not used to generate these updates.

Chrome extension 0.2.4 is publicly listed on the Chrome Web Store. The current protected-message protocol requires Chrome 0.4.0, submitted and still under review as of 28 October 2026. The public 0.2.4 listing does not establish compatibility with that protocol. Use the phone-authorized Web Inbox while waiting for the compatible extension. A compatible extension can show desktop alerts and replies on the original message. Each Topic needs phone authorization and Chrome must remain running for background checks. The phone-authorized Web Inbox is available now.

Click App Store or Google Play to show a QR code, then scan it with your phone camera. The dialog also has a direct store link. On a phone, the store button opens the store directly. These download codes do not authorize a device.