K Koda Intelligence
scienceThe Lab
LAB REPORT · No. 0186 · 2026-08-04 codeCoding 7 MIN READ

Pushary

Lock screen approvals and push notifications for AI coding agents via MCP

Your agent stalls on a yes-or-no question while you are making coffee; Pushary moves that question to your lock screen and gets the run moving again.

payments$9.99/mo after a 7-day card-first trialtimerabout 10 minutesdevicesweb, iOS, Android
mcpservers.org/servers/pushary/pushary-skill
Pushary interface screenshot
SPECIMEN 0186
THE KODA SCORE 7.0/ 10

A narrow problem solved cleanly with three question types, permission hooks and an audit trail, held back by thin independent validation and a subscription for what is essentially a notification relay.

Capability7.2
What it can actually do
Ease of use8.3
Zero to productive
Value6.8
What you get per dollar
Momentum6.0
Shipping pace and traction
gavelThe Verdict

This is for people running two or more coding agents who keep losing minutes to approval prompts nobody is at the desk to answer. If that is you, the $9.99/mo is cheap against the dead time, and the MCP-plus-hooks install is genuinely a one-command affair with Claude Code. If you run a single agent on Claude Code with Claude Max, Anthropic's own Remote Control already covers that case for free and Pushary is redundant.

BUILT FOR
check_circleMulti-agent operatorscheck_circleSolo founders shipping from a phonecheck_circleClaude Code power users without Maxcheck_circleSmall teams needing an approval audit trail
SKIP IT IF
cancelSingle-agent Claude Max userscancelTeams needing airtight prod gating
IF YOU ONLY READ ONE BLOCK
>Today's digest called it free; the site says $9.99/mo after a 7-day card-first trial, so budget for a subscription and a card up front.
>MCP server plus Claude Code permission hooks means agent approval prompts arrive as yes/no, multiple choice or free-text questions on your phone.
>Do not install both the Claude Code plugin and the npx agent-hooks setup; the docs warn each hook then fires twice.
>If you run Claude Code on Claude Max and nothing else, Anthropic Remote Control already does this for free.
THE RUNDOWN

What it actually does.

lock

Lock screen answer buttons

Agent questions arrive as notifications you can answer without unlocking into a terminal session.

quiz

Three question types

Agents pick yes/no confirmations, multiple choice, or free text depending on what they actually need from you.

verified_user

Claude Code permission hooks

Routes native tool approval prompts out of the terminal and into push notifications.

description

Rich context notifications

Agents can attach file changes, error details and suggested next steps to a detail page behind the notification.

smart_toy

Agent identification

Each notification names the agent asking, so a fleet of parallel runs does not become a guessing game.

hub

Cross-agent fleet coverage

One inbox spanning Claude Code, Codex, Cursor, Windsurf, Hermes, Lovable and any MCP client.

history

Audit trail

Every question and answer is logged, which is the part that matters when someone asks who approved what.

extension

One-command plugin install

The repo ships as a Claude Code plugin that installs MCP tools, hooks and the skill together.

RUN THESE PLAYS

How you would actually use it.

Concrete setups pulled from the research, not feature-list hand-waving.

01

The coffee-run refactor

WHO

Solo builder running one long agent task

THE PLAY

Install the Claude Code plugin, set PUSHARY_API_KEY, and tell the agent to keep going and ping your phone if it needs anything.

PAYOFF

A 20-minute refactor no longer sits idle waiting for you to walk back to the desk.

02

Fleet triage from one inbox

WHO

Developer running Codex, Cursor and Claude Code in parallel

THE PLAY

Point each agent at the hosted MCP endpoint with the same API key so every question lands in one notification stream with the agent name attached.

PAYOFF

You stop tab-hopping between three tool UIs to find out which run is blocked.

03

Gated writes with a paper trail

WHO

Small team lead reviewing agent changes

THE PLAY

Enable permission hooks so tool approvals route to phones, keep the safe-task list to read-only operations, and lean on the logged question-and-answer history.

PAYOFF

Approvals happen in minutes instead of hours, and you can reconstruct who greenlit each action.

04

Done and failed alerts

WHO

Anyone kicking off overnight or background runs

THE PLAY

Have the agent fire task-done and task-failed notifications instead of you polling the terminal.

PAYOFF

Failures surface immediately rather than at the next manual check-in.

THE DAMAGE

Pricing, straight.

KODA PICK Monthly
$9.99/mo

7-day card-first trial, MCP support, cross-agent fleet, lock screen answer buttons

insightsTen dollars a month is fair if you genuinely run multiple agents, but it is a hard sell as a notification relay for a single Claude Max setup that Anthropic already covers for free.

Pricing as captured on 2026-08-04. Check the live site before you commit.

THE STREET

What people online are saying.

Real reactions surfaced during research. Paraphrased faithfully, linked to source.

graphic_eqReaction is thin and mostly launch-adjacent: Product Hunt supporters love the idea of a phone yes button, and the sharpest public critique is that a lock screen strips away the session context you had 40 minutes ago.

Supporters like that it collapses an agent pause into a simple yes button on your phone, so the work keeps moving while you are away from the desk.
PraiseProduct Huntarrow_outward
The launch thread frames task-done, task-failed and task-needs-decision alerts as the killer use case for keeping coding agents moving.
PraiseProduct Huntarrow_outward
At the terminal the whole session is scrolled above you; on a lock screen you get one diff and none of the intent you set 40 minutes ago and have half-forgotten.
CritiqueProduct Hunt discussion, quoted by VEONIBarrow_outward
STACK IT AGAINST

The field.

Anthropic's own remote approval path for Claude Code, covered by a Claude Max subscription.

PICK IT WHENYou run exactly one Claude Code setup on Claude Max and do not want another subscription.

Generic notification channels wired to agent events, which Pushary also supports as fallback delivery.

PICK IT WHENApprovals should live where your team already discusses them and lock screen speed is not the point.

Each agent's native in-tool permission prompts.

PICK IT WHENYou work from one machine at one desk and do not need cross-agent centralization.

WHERE IT BREAKS

The honest part.

ZERO TO RUNNING

Getting started.

timerTime to first value: about 10 minutes

1

Sign up at pushary.com, grab your API key and set PUSHARY_API_KEY in your environment.

2

Run /plugin marketplace add Pushary/pushary-skill then /plugin install pushary in Claude Code, or add the hosted MCP endpoint with a Bearer token to settings.json.

3

Enable notifications from the Pushary dashboard on your phone, then trigger a throwaway approval to confirm the round trip.

STILL ASKING

Quick answers.

Is Pushary actually free?expand_more

No. The site lists a single Monthly plan at $9.99/mo after a 7-day card-first trial. Today's digest note describing it as free does not match the published pricing, so plan on the subscription.

Do I need a Claude Max subscription?expand_more

No, Pushary works without one and explicitly targets setups Anthropic Remote Control does not cover: Codex, Cursor, Claude Code without Max, and multi-agent fleets. If you do have Claude Max and only use Claude Code, Remote Control already handles that one case for free.

Can it auto-approve safe tasks so I am not tapping all day?expand_more

The permission hooks route Claude Code tool approvals through notifications and the product describes per-tool policy gating, so you can decide which classes of action need a human. Keep that list conservative at first, since the research surfaces no independent testing of how the policy layer behaves under pressure.

What is the main risk of approving from a phone?expand_more

Context loss. The sharpest public critique, from the Product Hunt discussion, is that the terminal shows you the whole scrolled session while a lock screen gives you one diff and none of the intent you set earlier in the run. Rich context notifications with file changes and error details soften this, but they do not replace reading the session.

THE BOTTOM LINE

Wire it to one agent, keep the auto-approve list boring for a week, and only then let it near anything that touches production.

Field research: 1 pages scraped · 3 search passes · 13 community sources. Reviewed by the Koda desk on 2026-08-04.

Like what you see?

Get tomorrow's brief delivered to your inbox.

One email per day. Unsubscribe anytime.