Pushary
Control panel for AI agents on your lock screen
749 followers
Control panel for AI agents on your lock screen
749 followers
Your AI agents stop when they need a permission or an answer. Pushary puts that yes or no on your lock screen, so the work keeps moving while you are away. New in this launch: native iPhone and Android apps. Pair with your terminal by scanning a QR code, no key to paste. Approvals, questions, and task-done alerts from Claude Code, Codex, Cursor, Gemini CLI, Hermes, and Claude Cowork land in one inbox, with per-tool policies that auto-approve the safe stuff and an audit trail of every decision.
This is the 4th launch from Pushary. View more
Pushary
Launching today
One command connects your AI agents to your lock screen. When Claude Code, Codex, Cursor, Gemini CLI, Hermes, or Claude Cowork stops to ask, you tap yes from your phone and the run keeps moving. New in this launch: native iPhone and Android apps. Pairing is a QR code you scan from the terminal, no key to paste. Per-tool policies auto-approve the safe reads. Every decision lands in an audit trail.
Free Options
Launch Team / Built With
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.
Pushary
@krekeltronics
Thanks Patrick, that's exactly the framing. The agent was never the slow part, the human loop was, and most tools optimize the wrong half.
On the audit piece, agreed it carries as much weight as the tap. Every decision writes to an immutable record: what was asked, what got answered, when, and from which surface, bound to the request so it can't drift after the fact. For a small team that's the difference between "the agent did something" and "here's exactly what was approved while everyone kept moving." It exports too, so it holds up when someone actually asks.
MonoCloud for Startups
Anyone running Claude Code or Cursor heavily knows the pain of an agent stuck waiting on a yes while you are away from the keyboard. Pushary going after that with lock-screen approvals is well targeted. The thing that would keep me using it is trust, showing enough of what the agent wants to do that I can approve safely from my phone. Get that right and this fits into a lot of workflows.
Pushary
@roguetink
That's exactly the bar. A yes/no with no context is just a slower terminal. So the approval shows the real call, the exact command or file, the agent, and the project, and policies mean only the risky stuff reaches you in the first place. Richer previews like an inline diff before you approve are where we're headed next. If you run agents heavy, I'd want your read on where the context isn't enough yet.
you basically named the exact tension in your own forum post (babysit vs walk away) and this is the fix for it, just across 6 tools instead of 1.
Pushary
had this happen last week actually, agent just sat there for 20 min waiting on a permission.
Pushary
gonna try this on my next overnight run.
Pushary
Build Check
Hey Aadil! Looks awesome and sounds so promising for every dev. Wish you all the best here!
Pushary
@german_merlo1
Thanks Germán, really appreciate you stopping by. Means a lot. 🙏
if there are any questions you have after using the product I'm always here or email at aadil@pushary.com
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 👍
Pushary