Pushary
Control panel for AI agents on your lock screen
902 followers
Control panel for AI agents on your lock screen
902 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
Launched this week
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
how do you actually set the per-tool policies, is that a config file thing.
Pushary
@aadilghani - Looks cool, and very useful for streamlining development workflows. An plans to integrate with @opencode in the future?
Pushary
@codeandsea
Thanks Brent! Short answer, yes, that's exactly the kind of agent I want to cover.
Today, if OpenCode can load an MCP server (most agents can), you can wire Pushary in right now through the "Other" option in setup and get the notifications and ask-a-human flow. The piece that makes it first-class, approve or deny on its tool calls, needs a pre-tool hook I can wrap, the same way Claude Code and Codex expose theirs. If OpenCode has that surface, a proper adapter is quick and I'd build it.
Point me at its hook or permission API and I'll take a real look.
@aadilghani - Awesome, yes opencode does support MCP integration now.
Pushary
@codeandsea
Legend! <3
This is neat. Do policies carry over if you reinstall the app or switch to a new phone?
Pushary
@dhiraj_patel5
Of course they do, they are account specific, so just ensure you use the same account and you're golden.
Pushary
@ankita_singh27
Fair question. Claude Code's app is genuinely good at what it does, remote-driving a Claude Code session. The difference is the job it's doing.
That app drives one vendor. Pushary sits across Claude Code, Codex, Cursor, Gemini and Hermes, so if you run more than one agent it's one inbox and one policy instead of an app per tool.
It's also a different model. Remote control is pull, you open the app and drive. Pushary is push, the agent keeps running on your machine and only reaches you when it hits something it can't decide alone. You're not watching a session, you're getting tapped for the five seconds that need a human, and the safe stuff auto-approves so it never reaches you. On top of that, per-tool policy decides what even surfaces, and every approval lands in one immutable cross-agent record. That's governance, not just access.
Honest reply dev-to-dev: if Claude Code is your only agent and you just want to drive it from your phone, their app is good and you may not need me. Pushary earns its spot when you're running more than one, want to stop hand-approving the trivial stuff, and need a record of what got approved while you were away.
Really cool concept! How do you prevent accidental approvals from the lock screen?
Pushary
@dhatri_rai1
Thanks Dhatri! Approving is gated behind your device unlock, the Approve button carries an auth requirement, so tapping it triggers Face ID or your passcode before anything registers. A stray tap or a phone in your pocket just hits the unlock wall and nothing happens. Deny stays one-tap since denying is always safe. And for the riskiest calls the server drops the one-tap Approve entirely, so you have to open the app and read the full context before you can say yes.
Congrats. My only concern is security. If someone gets access to my phone, what safeguards stop them from approving everything?
Pushary
@himani_sah1
Good thing to press on, and I'll be straight about where the boundary is.
The first wall is that approving requires your device unlock. The Approve action is gated behind Face ID or your passcode, so a locked or lost phone can't approve anything, and denying stays one-tap since denying is always safe. The honest part: if someone can actually unlock your phone, your device auth is the boundary Pushary relies on, same as your banking app. I won't pretend there's a second password sitting on top of your Face ID.
What still limits the damage: only what your policy allows can be approved at all, destructive calls are force-held so they can't be one-tapped and need the app open with full context, and every approval is logged with when and from where. If a phone goes missing you can revoke it and kill any running agent from another device. One straight caveat, on Android the routine approve isn't behind an unlock at the notification layer yet, that's iOS today, and we're closing it with an in-app biometric.
ConnectMachine
Congrats on shipping! Does this work only with coding agents or can I plug in any agents?
Pushary
@syed_shayanur_rahman
Thanks! Not just coding agents. Those are the first-class ones, Claude Code, Codex, Cursor, Gemini, Hermes, where it hooks in deep. Any other agent can plug in two ways: over MCP if it speaks it, or through the SDK and framework adapters like LangGraph, CrewAI, the Vercel AI SDK, and the OpenAI Agents SDK.
So a marketing or ops agent that needs a human to approve something reaches your phone the same way a coding agent does. The one honest difference is depth: coding agents get hard gating at the hook level, everything else asks through Pushary cooperatively. But the human-in-the-loop part works for any agent.