Ntfyx FAQ: HTTPS push, agent replies and hourly service checks

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.

• Guide and scope

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.

• Guide and scope

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. The official website is ntfyx.me. The product is named Ntfyx on the App Store and Google Play; ntfyx is its companion CLI command.

The tagline is “notify x to me”. No Ntfyx account is required.

Protected Topic agents, CLI tools, scripts and services need authorization on the primary phone. Anyone knowing a public Topic ID or link can read and send there, without pairing; public messages cannot request answers or Call. You can also explicitly subscribe to official public-content sources in Discover.

Ntfyx does not automatically subscribe you or insert unrelated content. Revoke a source, or pause and unsubscribe from a subscription, on your phone.

Ntfyx does not insert ads or unrelated content into the Inbox, including during free use. You choose your own authorized sources and may opt into official notification subscriptions. Pairing tests and necessary connection or security status support the Inbox. The Technology digest uses public headlines and links; its publisher knows the public content it sends, but does not use private agent messages.

The primary phone app is public on the App Store (iPhone 1.8.3, iOS 18.4+) and Google Play (Android 1.8.2, Android 10+). Current signed CLI 0.6.1 supports Windows, macOS and Linux glibc; musl Linux is not supported. Your phone can authorize an optional Web Inbox. Android push requires Google Play services.

• Current downloads and availability

Agents that can run the CLI or launch a local stdio MCP server can use the notification and question tools, subject to their host’s permissions. The documented Claude Code permission adapter has a specific tested scope. Ntfyx is not a published ChatGPT or Claude app-directory integration, and local stdio support does not imply that a cloud chat interface can launch a program on your computer.

Finding this documentation in AI search is separate from connecting an agent.

• Supported agent integration and configuration

A Topic groups messages from a source or a workflow, such as Work or Backups. Free includes one shared subscription slot for a notification source or public Topic follow. Topic count is not a paid entitlement; every plan has a 1,000-Topic technical limit. Public Topics allow anyone knowing the ID to read and send messages.

Protected Topics receive private messages and questions from authorized agents, scripts or services. Connecting an authorized browser to an existing Topic does not create another Topic. Message, device, storage and rate limits still apply.

• Service limits

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.

• Security model and limitations
• Privacy and retention

Keep an encrypted recovery package and its separate recovery code if you want to migrate your Inbox. Support cannot recover lost encryption keys or expired history. Check your recovery materials before removing the original phone.

• Recovery guide

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.

• Read the encryption model and its limits

Choose your agent in the installer on this page. One command installs the signed CLI, guides phone pairing and configures local MCP, hooks and phone-reply guidance. Restart the agent and answer a test question. You can also install from the public Ntfyx plugin marketplace.

• Session guide and availability

A Session groups messages and replies for one task inside a Topic. The Inbox shows the latest message for each session; opening it reveals the conversation. Session conversations are available with CLI 0.1.3+ and current phone and Web apps.

• Session guide and availability

With CLI 0.1.3 or later, send notifications and questions with the same --session-id inside the same Topic. A session can include multiple authorized sources. Without a session ID, each new message starts its own conversation.

• Session guide and availability

Confirm or choose directly on the original message. For text, select Reply on that message and write in the quoted composer. New questions do not change the reply target. Confirmed choices and sent text appear below a light divider inside the original message.

• Session guide and availability

In the updated Web Inbox, open the conversation actions, select Delete conversation and confirm. Phone support arrives with Ntfyx 1.4 after store approval. This removes existing messages from that device and keeps resynchronized history hidden. New messages can reopen the conversation. Other devices and already submitted replies are unchanged.

• Session guide and availability

No. A reply answers one explicit request. The sender verifies it before continuing; an expired or denied request does not grant approval. A session does not give an agent new permissions or forward arbitrary terminal prompts.

• Session guide and availability

Choose one-command setup on the homepage, or install CLI 0.6.0+ and add KaylaONeal/ntfyx-agent-plugins as the Ntfyx marketplace. Plugin 0.4.1 includes step-by-step phone setup, local MCP, rich-message guidance, phone replies and Session support. Claude AskUserQuestion is bridged; Codex uses explicit MCP questions.

Public Ntfyx marketplace installation and official directory inclusion are separate.

• Agent plugins and compatibility

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.

The extension provides desktop alerts, a toolbar unread count, Topic/Session history and original-message replies. The primary phone authorizes each Topic separately. For now, use the available Web Inbox.

• Chrome extension: setup and publication status

The extension needs Chrome running for background checks and desktop alerts. Sleep, offline mode, organization policies or OS notification settings can delay delivery. Opening the Inbox requests a fresh synchronization. An alert, a reply accepted by the service and an agent action completed are different states.

• Chrome extension: setup and publication status

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.

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.

• Notification marketplace and free subscriptions

Choose App Store or Google Play on the homepage or Downloads page, then scan the download QR with your phone camera. The dialog also has a direct store link. On a phone the buttons open their stores directly. The links work without JavaScript, and download QR codes do not authorize devices.

• Phone apps and computer downloads

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.

• Details and verified scope

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.

• Details and verified scope