Pushary

Approve AI requests from your lock screen

Productivity

Developer Tools

Artificial Intelligence

Visit WebsiteSee on Product HuntApp Store ⧉Play Store ⧉Twitter ⧉

I literally was thinking about this. I personally would use this! I need to ask if I am allowed to use this on certain computers. But I really like this. Slightly thinking about how all the major players have this feature but you create a central hub which is very cool.

Nice framing — the phone approval loop is the part I’d actually use.

One small thing I’d want as a builder: not just Yes/No, but a quick risk label for why the agent is blocked — file write, shell command, dependency install, payment/API action, etc. When I’m away from the terminal, the hard part is knowing whether I’m approving a harmless unblock or changing the risk profile of the run. The audit trail could make that decision reviewable later.

The annoyance of having to open up an app, then select the chat, then either type or click accept is very real.

Love this! Congrats on the launch y’all :)

the per-tool auto-approve for safe reads is the part I'd poke at - how do you define "safe" consistently across six agents that each have their own permission model, shared policy schema or configured per agent?

The per-tool policy layer is the part I'd want to configure first — the difference between auto-approving all file reads and auto-approving only reads from your project directory is a meaningful trust boundary. Is that granularity available now, or does the policy system work at the tool level only (all of Claude Code's file reads, not individual path patterns)? The audit trail only stays useful if the policy captures intent at the right grain.

Okay this is really amazing. I run multiple things at once some days and the tab switching happens. I am looking forward to trying this. Congratulations on your launch! :) Just wondering if it also works with tools outside of coding like general AI workflows?

the fail-closed design answers the question I would've asked about a missed tap, but what about the phone being straight up unreachable - dead battery, no signal, airplane mode on a flight. for the overnight-run use case you're marketing specifically, does the agent just sit blocked indefinitely until the phone comes back, or is there some kind of escalation/timeout path (email fallback, a second paired device, anything) so a dead phone overnight doesn't turn into a stalled job for hours?

The per tool policies plus the audit trail are the part I would build the whole product around. After a week of taps you can look back and see which approvals were rubber stamps every single time, then promote exactly those to auto. That is a much safer route to fewer prompts than guessing the policy up front.

The thing I would watch is what the notification actually shows. A lock screen has room for the command but not for the context, and an approval given without the diff is just a faster way to say yes to the wrong thing. Risk class might also travel further than tool name, since a read is a read whether it came from Codex or Cursor.

Congrats on shipping the native apps, iOS web push was never going to carry this.

congrats on the rebuild. the part that stands out is going all-in on native push after web push let you down on iPhone. genuine question - for the overnight runs, what happens if you don't respond to an approval within a few hours? does the agent just stay blocked indefinitely, or is there some timeout/escalation so a long run doesn't die silently while you're asleep?

Congrats on the launch man, almost overtook us too aha)

Is this essentially an app on mac and on iphone?

Novel concept. What's the latency like from agent request to phone notification?

Congrats on shipping! Does this work only with coding agents or can I plug in any agents?

Interesting take on the build. I was solving this with Slack messages, but lock screen approvals sound much smoother.

A feature I would request is approve with Face ID confirmation for high-risk actions. :D

Congrats. My only concern is security. If someone gets access to my phone, what safeguards stop them from approving everything?

Love this, it's so frustrating when an agent job stalls when I step away. Cool tool!

Really cool concept! How do you prevent accidental approvals from the lock screen?

Congrats Aadil, the fail-closed detail is what separates this from a notification hack! I’m the non-dev case though: I run Claude Cowork and claude.ai all day for marketing and ops automations, so my risky actions are “send this email to a client” or “update the CRM,” not bash commands. Two questions: do policies work the same for those kinds of actions? And can an approval route to a teammate instead of just me? If my agent drafts an outbound email, the real approver should sometimes be my marketing director, not whoever paired the phone. A shared approval inbox for a team would make this a company tool, not a solo one.

Really smart solution to a common problem with AI agents. Aadil, approving important requests from your phone while keeping risky actions controlled can save a lot of time.
Congrats on the launch 👍