Changelog.

Fixes Codex and Claude Code completion notifications that previously showed a generic turn-ended placeholder. Notifications now summarize the final assistant answer, include the project name, and retain Markdown in message details. Missing final answers no longer produce empty completion notices. Long replies are truncated to the existing encrypted message limit.

Upgrade the desktop CLI with ntfyx upgrade. Existing phone pairing is retained. npm installations use npm install -g ntfyx@0.6.1.

• Download CLI 0.6.1
• Verify this release

Adds public Topics with anonymous text and rich-message sending, reading, explicit content-terms acceptance, reports and local blocks. Agents can use the CLI directly or equivalent local MCP tools. Usage shows daily message, Call and answer-request allowances plus monitor and subscription slots. Public Topics have no answers or Calls; protected Topics keep signed answers and one-time claiming.

New protocol support requires CLI 0.6.0 and iOS/Android 1.8.0, Chrome 0.4.0 or the updated Web receiver; check each store’s public availability separately. Complete or cancel older pending questions with the original CLI before upgrading. Use ntfyx upgrade for standalone installations or npm install -g ntfyx@0.6.0 for npm installations.

• Public Topics and CLI examples
• Verify CLI 0.6.0

Adds lightweight rich messages: explicit text, Markdown, callouts, metrics, tables, progress and native line/bar charts. Send JSON from a file or stdin without MCP, validate locally without pairing, and keep short notification summaries with full detail/search/copy. CLI/MCP schemas and Agent guidance share the same bounded content format; signed replies and one-time claiming are unchanged.

Rich content requires updated receiving clients. Existing standalone installations can run ntfyx upgrade. npm installations use npm install -g ntfyx@0.5.0. Upgrade the Ntfyx phone app to 1.7.0+ or use an updated Web/Chrome receiver before sending rich content.

• CLI 0.5.0 release manifest
• Verify this release

Keeps phone-reply waits alive across temporary network failures and rate limits, shares concurrent waits in one process, indexes request history, and avoids rewriting unchanged credentials. Approval signatures and one-time claiming remain unchanged. Existing standalone installations can run ntfyx upgrade.

npm installations remain package-managed.

• CLI 0.4.1 release manifest
• Verify this release

Adds Windows x64 and arm64 CLI downloads, PowerShell and npm installation, current-user DACL protection for credentials and webhook exports, and verified updates that replace the Windows executable after the CLI exits. Includes macOS Intel runtime acceptance; CLI, MCP, My Monitor and fixed webhooks use the same phone-authorized permissions.

Windows Claude Code hook setup requires 2.1.139 or newer; older or unknown hosts get MCP only. Codex on Windows uses local MCP without automatic hooks. The existing marketplace plugin remains a macOS/Linux setup path. Standalone macOS/Linux and Windows installations use ntfyx upgrade; --target-version 0.4.0 can pin the official immutable version, and downgrades remain rejected.

On Windows, a scheduled result starts replacement after the invoking CLI exits: inspect the returned receipt and run version --json before reporting success. PowerShell and npm installation remain available; npm installations return package_managed and are updated through npm. Native host execution approvals retain their separately verified host/platform combinations; Windows scheduling uses your own scheduler.

• CLI 0.4.0 release manifest
• Verify this release

Adds incoming Webhooks backed by the existing HTTPS Push delivery channel. Fixed private POST URLs accept UTF-8 text, JSON and URL-encoded forms. Existing App-copied send URLs also accept dynamic POST bodies. CLI and MCP can manage independent Source-owned Webhook keys after separate explicit phone approval: create, inspect, update, rotate, enable, disable and delete.

Private URLs are exported only to an explicitly selected protected file. Adds exact raw-body GitHub HMAC and Standard Webhooks signature verification, bounded timestamp checks, delivery-ID deduplication and generation checks for queued work. Existing notifications, phone questions, Sessions, My Monitor management and phone-created HTTPS keys remain compatible.

Webhook management requires its own bounded grant; it does not grant Inbox or root-key authority. Revoking the management grant does not revoke existing send keys: disable or delete those keys to stop delivery. Run ntfyx upgrade for a standalone installation, or update ntfyx through npm for a package-managed installation.

• CLI 0.3.0 release manifest
• Verify this release

Adds My Monitor management through a phone-authorized, revocable 24-hour delegation. Agents can inspect, create, update, pause, resume, remove, test and preview monitors using the existing reachable, text and JSON rules. Structured configuration, partial updates, dry runs, operation IDs and generation checks make automated changes reviewable and recoverable.

Adds machine-readable capabilities, help and schemas, signed marketplace discovery, local request inspection, and question deduplication for MCP. Existing notification, question, Session and one-time answer-claim behavior is preserved. Monitor access requires a separate explicit phone authorization; it does not grant Inbox administrator or root-key access.

Run ntfyx upgrade for a standalone installation, or update ntfyx through npm for a package-managed installation.

• CLI 0.2.0 release manifest
• Verify this release

Installation and upgrade downloads can now continue on slow networks without failing at the former 60-second total limit. Downloads stop after 60 seconds without data or a 30-minute total cap. Network failures now report a retryable network_error. This patch applies to the standalone CLI upgrade and the npm postinstall downloader.

• CLI 0.1.6 release manifest
• Verify this release

Native permission approval is now enabled on Apple silicon Macs after real-host validation with Claude Code 2.1.303 and Codex 0.163.0. Intel Mac native approval remains unverified and returns to the terminal; Codex requires interactive TUI and /hooks trust. Claude setup now separates permissions (off by default), questions and notifications.

The installer adds config/Topic forwarding, skip-connect, dry-run and integration-only removal. Hook lifecycle epochs reject stale replies across session restarts, managed Hook removal preserves other commands, and MCP inherits the selected Topic. Request IDs beginning with a dash also work after leading options.

Shared client pairing also accepts an existing non-exportable browser identity for Web/Chrome integration. The signed standalone installer and versioned 0.1.5 npm-package URL passed public installation checks. Acceptance of the 0.1.4 to 0.1.5 upgrade is still blocked: the original binary returned invalid_schema on both tested network paths.

npm registry remains at 0.1.4; publication of 0.1.5 and the MCP Registry entry is paused. To enable Claude permission hooks, use ntfyx setup claude-code --permissions on with the original executable/config/Topic context. Codex hooks require review in /hooks.

• CLI 0.1.5 release manifest
• Verify this release

Improved delivery on unstable connections. Safe reads and signed notification or answer submissions retry twice using the same message, preventing a retry from creating another decision. Execution claims remain single-use and are never automatically replayed. Includes Session grouping, adaptive connection QR codes, and one-command Claude Code or Codex setup from 0.1.3.

Run ntfyx upgrade for a standalone installation, or use the signed installer. Existing connections and credentials are preserved. The npm package is available through the versioned download URL; npm registry publication is tracked separately.

• CLI 0.1.4 release manifest
• Verify this release

Adds Session conversations with --session-id and --session-name, compact adaptive pairing QR codes, one-command Claude Code/Codex setup, phone-reply guidance, and a Claude AskUserQuestion bridge with verified single-use answers. Custom credential paths now carry through setup to MCP and hooks. Plugin 0.2.0 includes matching instructions and host manifests.

Run ntfyx upgrade or the signed installer. Use iOS 1.1.0+, Android 1.1.0+ or current Web Inbox for Session conversations. Native execution-approval platform restrictions remain separate; Codex native question prompts are not intercepted.

• CLI 0.1.3 release manifest
• Verify this release

Adds phone approval for Codex and Codex usage alerts. ntfyx setup codex installs PermissionRequest and Stop hooks for shell commands and apply_patch file changes and registers the MCP server; trust the hooks in Codex with /hooks. ntfyx watch codex-usage and ntfyx setup codex-usage notify you about new rate-limit reset credits, credits about to expire, 80% and 95% usage, window resets, and the limit being reached or lifted, reading usage read-only through Codex's local app-server.

Claude Code phone approval now works on releases from the minimum verified version, 2.1.283, whenever the request matches the documented format, instead of on one exact version. MCP tools declare read-only and destructive hints. Protocol v1 and the release key are unchanged. Existing standalone installations can use ntfyx upgrade.

Codex approvals: ntfyx setup codex, then trust the hooks with /hooks in Codex. Usage alerts: ntfyx watch codex-usage --dry-run, then ntfyx setup codex-usage.

• CLI 0.1.2 release manifest
• Verify this release

Protects local credentials when adding another Source. If this computer already has a connection, connect --new and create require an unused local --topic alias before starting a pairing session; the phone still chooses the remote Topic. If another process takes that alias while pairing is in progress, the newly authorized connection is saved separately and the CLI returns a resume ID and command.

Use ntfyx connect --resume ID --topic UNUSED_ALIAS to install that saved authorization without pairing again. Existing profiles and the default connection are preserved. This patch does not change protocol v1 or migrate existing credentials. Existing standalone installations can use ntfyx upgrade. New Source example: ntfyx connect --new --topic SECOND_ALIAS.

Recovery from a reported alias race: ntfyx connect --resume ID --topic UNUSED_ALIAS. The resume ID comes from the CLI; do not invent it.

• CLI 0.1.1 release manifest
• Verify this release

First signed CLI release for macOS and Linux: phone-authorized pairing, encrypted notifications and questions, one-time execution claims, MCP, and the verified Claude Code 2.1.283 Linux x64 permission-hook integration. Both macOS artifacts are Developer ID signed and Apple-notarized. Linux x64 and macOS Apple silicon have actual runtime checks; Linux arm64 has an emulated check, while Intel Mac runtime testing remains outstanding.

• CLI 0.1.0 release manifest
• Verify this release

Production and staging Web/API services are deployed, with an independent status page. iPhone 1.8.3 is publicly available on the App Store and Android 1.8.2 on Google Play. Store release availability, purchase validation and device-specific acceptance checks are separate. 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.

• Service status

Wire messages use protocol v1. Claude support is limited to the tested host/version; unsupported or interrupted authorization returns to the local terminal. The npm wrapper is available as an official website package URL; there is no npm registry release. Future schema or minimum-client changes will include migration notes.