What shipped: reliable delivery across browser, mobile, and the iOS home screen

A notification that does not arrive is worse than no notification, because you wait on it. This release closes three ways an agent question could go quiet on you.

Agent push no longer fails silently

Some agent sites were missing VAPID keys, the credential a browser needs to accept push. When a key was absent, the ask_user call could fail without telling anyone, so an agent would block on an approval that never reached a phone or browser.

Two fixes landed. Agent sites now get their VAPID keys generated atomically when the site is created, so a site can never end up half-configured. And ask_user no longer depends on web push being live. If the browser channel is not ready, the question still routes through your other connected channels instead of dying.

One Connections tab

Web Push, Mobile, and Slack used to live in different corners of settings. They are now one Connections tab so you can see, in one place, which channels can actually reach you and turn them on or off. If a channel is off, you know it, instead of finding out when an approval goes missing.

An inbox for the iOS home screen

On iOS, the decision link from a notification is cross-origin to a home-screen web app, and Apple breaks that hop. Tapping through did not reliably open the page to answer.

So home-screen users on iOS now get a pending-questions inbox on the agent page. Open it and every waiting question is there to approve or deny, no deep link required. For full lock-screen approvals with the app closed, the native iOS and Android app is the better path.

Turn it on

If you already use Pushary, these fixes are live with nothing to do. To wire up channels, open your Connections settings, or start from the quickstart. Delivery is the floor under the permission policy and audit trail that make Pushary a control panel for AI agents. See pricing for plans.