Pushary
Control panel for AI agents on your lock screen
527 followers
Control panel for AI agents on your lock screen
527 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
Lock-screen approvals solve a real gap for long-running coding agents, but that tiny approval moment has to carry a lot of meaning. I would want to see which repo/session/tool is asking, what files or services are affected, and whether the action is reversible. How much of that fits into the mobile prompt?
Pushary
@yaroslav_stelmakh
Yaroslav, good list, and most of it already rides along.
Agent, tool, and repo: yes. Every request carries the agent it came from, the tool and its target (the file for an edit, the command for a shell call), and the project it's running in. Session identity is tracked too, so the app groups requests by agent and run.
What's affected: for an edit or a command you get the exact target. Structured "services" is softer, a deploy shows the command, not a parsed list of what it touches. Real gap, not pretending otherwise.
Reversible: today that comes through a risk classifier that flags destructive calls like rm -rf or a force push, so those are marked and never auto-approve. It's a risk signal, not a hard guarantee, and I'll say that straight.
How much fits: the notification carries the headline, which agent and what it wants. The full command or diff, your intent, and the risk flag live one tap in, so the glance stays scannable and the detail is there when the call is close. The more you cram onto the lock screen, the less gets read, so it's a glance plus a real detail view.
Where I'd want your push: the smallest set that lets you say yes safely without tapping through. That's the line I'm still tuning.
Love the switch to QR pairing! With one unified inbox, how does it handle multiple agents requesting approval at the exact same time?
Pushary
@aren_barseghyan
Thanks Aren! They don't collide, because nothing is shared between them. Each request is its own item with its own id, tagged with the agent, session, and project it came from, so three agents asking at once show up as three separate cards in the inbox, each labeled so you can tell them apart.
You answer them independently, and answering one resolves only that request. An unanswered one waits or denies on its own timeout without holding up the others, and the finalize step is guarded so a fast double-tap or two devices can't record conflicting answers for the same request. Policies also quietly clear the safe ones, so a burst rarely lands on you all at once.
what happens if you're on a plane or somewhere dead zone and something's blocking on you.
Pushary
@sadie_charlotte
Good question, and honestly it's the whole point. Nothing risky runs while you're dark. Pushary is fail-closed: no answer defaults to no, so a blocked call never gets auto-approved on your behalf just because you dropped off signal. The worst case is that one step waits or gets denied per the policy you set, while everything safe keeps moving.
And you set that behavior per tool. A risky command can hold for a decision, fall back to deny after a timeout you choose, or route to a teammate if you're out of reach. Meanwhile reads, greps, anything you've allowlisted auto-approve, so most of a run never needs you at all.
When you land, the questions that were waiting are sitting in your inbox. You answer, the agent picks back up.
This actually looks very useful. I'm gonna try this out. Does it also work with VSCode and Antigravity?
Pushary
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.
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.