Ntfyxnotify x to me

Ntfyx

Install Ntfyx: phone app, computer CLI and Web Inbox

Download Ntfyx for iPhone or Android, then install signed CLI 0.6.1 on Windows, macOS or Linux and scan to connect. Add a phone-authorized Web Inbox if needed.

Updated

Choose public access or protected pairing

#

Read or send to an existing public Topic with CLI 0.6.1 or Web using its link; no phone installation or pairing is needed. For encrypted messages and verified replies, pair with iOS/Android 1.8.0 or later and choose a protected Topic. Verified public store releases are iPhone 1.8.3 and Android 1.8.2; check that 1.8.0 is available before starting protected pairing.

One-command Agent setup

#

Choose an installed agent. This installs the signed CLI, guides phone pairing, then configures MCP, hooks and phone-reply guidance. Restart your agent afterwards; review Codex hooks in /hooks. Use direct setup or marketplace installation per host, not both.

Terminal
curl -fsSL https://ntfyx.me/install.sh | bash -s -- --agent claude-code

# Or Codex
curl -fsSL https://ntfyx.me/install.sh | bash -s -- --agent codex

macOS and Linux

#

Run the short installer command below. The installer detects your supported platform, verifies the release signature and checksum, and installs to ~/.local/bin by default. It needs bash, curl and OpenSSL. You can also download and inspect the installer before running it. If ntfyx is not on your PATH, use ~/.local/bin/ntfyx or add that directory with your usual shell configuration.

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

Windows PowerShell

#

Run the official PowerShell installer without administrator rights. It chooses x64 / ARM64 and verifies the release signature and exact hash. Manual script / ZIP downloads or npm with Node.js 24 are alternatives in the detailed installation guide.

Terminal
irm https://ntfyx.me/install.ps1 | iex
ntfyx version --json
ntfyx connect

Alternative: npm registry or versioned package

#

Install ntfyx 0.6.1 from the npm registry or its official versioned package URL. Both wrappers require Node.js 24 or later, download the version-pinned binary, and verify its release signature and hash. Keep your existing installation scope and lifecycle policy; when scripts are disabled, use the standalone installer.

Terminal
npm install --global ntfyx@0.6.1
# Or the official versioned package:
npm install --global https://ntfyx.me/releases/0.6.1/ntfyx-0.6.1.tgz
ntfyx version --json

Connect

#

Protected Topics require iOS/Android 1.8.0 or later. In the phone app, create or select a protected Topic; new Topics default to public and cannot pair Sources. Run ntfyx connect on the computer, scan the fresh QR, then confirm the protected Topic and Source on your phone. The QR expires after five minutes.

Use the explicit staging origin only for the separate test environment. Existing public Topic links work with ntfyx public without pairing.

Terminal
ntfyx connect
ntfyx send "Build complete"
ntfyx ask "Deploy to staging?" --allow-deny
# Separate staging environment:
ntfyx connect --server https://api.staging.ntfyx.me

Updates and rollback

#

Standalone installs use ntfyx upgrade. The release signature and checksum are verified before an atomic replacement; failed downloads preserve the prior binary and credentials. Successful replacements retain a .rollback binary, and version downgrades are refused. npm installations remain owned by your package manager and do not self-replace.

Windows executable replacement runs after the invoking CLI exits. A scheduled result is not installation success: inspect its receipt and the resulting version before relying on the replacement.

Terminal
ntfyx upgrade
ntfyx version --json

Manual downloads and verification

#

Choose the archive for your CPU and operating system. Both macOS builds are Developer ID signed and notarized. Linux requires glibc. Check the signed manifest and checksum before running a manually downloaded file.

Upgrade with pending questions

#

Before moving to CLI 0.6.1, finish or cancel outstanding questions with the version that created them. A request signed by an older protocol cannot be restored by the new CLI. If creation or delivery is uncertain, retain the original request and operation IDs; a timeout does not authorize sending a new request.

Runtime requirements

#

Runtime requirements: Windows 10 1809+, macOS 13+, and glibc-based Linux. x64 CPUs require Nehalem / SSE4.2 or newer; AVX2 is not required. These are the official requirements for the embedded Bun 1.4.2 runtime; tested systems are recorded separately.