Pushary

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.

Claude code app lets me remote control my session from any device! I am just trying to understand what is different here?

This nails an unglamorous bottleneck: the agent is often fast enough, but the permission loop is not. The audit trail matters as much as the lock-screen approval because small teams need to know exactly what got approved while work kept moving.

lfg!! congrats on the launch. cracked founder

Love the switch to QR pairing! With one unified inbox, how does it handle multiple agents requesting approval at the exact same time?

the lock screen is the right place for this. agent permission prompts are the exact kind of thing that should interrupt you for 5 seconds, not require you to open a laptop and find the right terminal window. the "work keeps moving while you're away" framing is good because that's the actual cost of blocked agents, it's not just inconvenience, it's idle compute and missed time windows. curious whether you can set different approval thresholds per agent or per action type, or is it a single yes/no for everything?

This is neat. Do policies carry over if you reinstall the app or switch to a new phone?