Ntfyx for Chrome: encrypted agent notifications and replies

The Chrome receiver is being built and checked. A Chrome Web Store listing and public install link have not been verified or announced. The currently available browser receiver is the Web Inbox. This guide describes the extension’s first-release design and will be updated with its actual publication state.

• Open the current Web Inbox
• Web Inbox guide
• Download the phone app

The extension adds desktop notifications, a toolbar unread count and a side-panel Inbox to your browser. View Topics, open Sessions and respond below the original question. Keep your phone for the initial authorization and access management. It receives messages from sources you connect; it does not read the pages you visit or automatically intercept every terminal prompt.

Open Ntfyx on your primary iPhone or Android phone before connecting the browser. The extension has its own receiver keys, separate from the phone’s management identity. Authorization is scoped to a Topic: authorizing one Topic does not automatically open every Topic in your Inbox.

1. Open the extension connection screen and name this browser connection.
2. Create a fresh one-time QR code. Scan it in the Ntfyx phone app.
3. Check the browser name, select the intended Topic and approve on the phone.
4. Send a new test message to that Topic. To receive another Topic, repeat Add another Topic and approve it on the same primary phone.

• Phone app downloads
• Pairing and receiver security

Within a Topic, the same Session ID groups related messages into one conversation. Inbox shows the latest activity; opening the Session shows its message history. Without a Session ID, each new message starts a separate conversation. A new receiver can only decrypt messages newly addressed to its authorized keys; it does not download the phone’s complete past history.

ntfyx send "Homepage update is ready" --session-id homepage-update --session-name "Homepage update"
ntfyx ask "Publish the homepage?" --allow-deny --session-id homepage-update
ntfyx ask "What should change?" --text --session-id homepage-update

• Session rules and CLI examples

Allow or deny a request, or choose a supplied option, with the compact controls directly below it. For a text question, select Reply to focus an input that quotes the original question. Your answer and its status appear below that question, separated by a light divider. New messages do not change your reply target.

Sending a reply does not establish that an agent has executed an external action; follow the actual receipt and execution status.

• Agent question and integration support

The extension’s notification settings let you switch desktop alerts on or off, mute individual Topics and choose whether system notifications can contain decrypted titles and message text. Message preview is off by default: the generic alert lets you open the Inbox without putting its contents in the operating system’s notification history.

The toolbar unread count and the Inbox are separate from whether a system alert was shown.

Chrome needs to be running for its background checks and desktop notifications. Closing the entire browser, suspending the computer, going offline or applying an organization’s browser policies can delay delivery. Opening the Inbox requests a fresh synchronization. A reply saved for retry must keep its original signed bytes; it remains pending until the service accepts it or its actual terminal state is reconciled.

A delayed or cancelled request cannot be treated as permission to continue.

The extension requests only the capabilities needed for the encrypted Inbox: notifications for desktop alerts, alarms for periodic background work, a side panel for viewing and replying, and access to the Ntfyx encrypted API. Its executable code is packaged with the extension. It does not request browser history, website content, cookies or permission to inject code into every page.

• Privacy, storage and deletion
• Encryption and remaining limits

Disconnecting clears this extension’s local connection, receiver keys, cached messages and drafts. It attempts to revoke the browser receiver; if the network is unavailable, revoke it on the primary phone as well. Revocation stops future access but cannot erase copies already delivered to a device. Extension data is separate from the hosted Web Inbox, even in the same browser.

Clearing one does not silently clear the other.

• Recovery and key loss
• Request service data deletion
• Get help without sending secrets