Your agents ask. You answer from the lock screen.
AckPush sends a push notification when an app or AI agent needs a decision. Tap Approve, pick an option or type a reply, and the answer goes straight back to whatever asked.
supabase db push, project ackpush. Waiting for your answer.
Try it: tap a button.
> ask("Run 3 migrations on production?")
waiting for your answerOne question, there and back
No bot to host and no endpoint per button. You send a question, and the answer waits for you to collect it.
Your app or agent asks
One API call, or the ask tool over MCP: a title, a few words of detail and the answers you accept.
POST /v1/messages { "title": "Deploy 2.4 to production?", "body": "12 commits, all checks green.", "actions": [ { "key": "ship", "label": "Ship" }, { "key": "hold", "label": "Hold" }, { "key": "note", "label": "Reply", "kind": "reply" } ] }Your phone shows the question
A normal push notification with your buttons on it. Answer from the lock screen without opening anything.
The answer goes back
The waiting call returns it, the agent carries on, or a signed webhook delivers it to your server.
GET /v1/messages/8c1f…/wait { "state": "answered", "response": { "action_key": "ship", "channel": "app_action" } }
Works with Claude Code and any MCP client, with a permission hook that sends Claude Code's approval prompts to your phone, and with anything that can make an HTTPS request. Connect over MCP or read the guide.
See it in a minute
Watch the full story (4½ minutes)Built for questions, not alerts
Most notifications tell you something happened. An AckPush message waits for you to decide what happens next.
Buttons you choose
Approve and Deny, Yes and No, Ship and Hold: up to three answers per message.
Typed replies
Reply in a sentence right from the notification when a button is not enough.
Snooze
Not now? Snooze it and it comes back. The sender knows it was snoozed, not ignored.
Deadlines
A question can expire. If nobody answers in time, the sender is told and can fall back.
Phone or desktop
Answer on iPhone, Android or in the web inbox. Answer once and the others clear.
Counted once
A double tap or a flaky connection never approves twice. Every answer is recorded exactly once.
How it compares
Getting a yes or no from a person usually means building the return trip yourself.
| Option | How you answer | How the answer gets back | What you build |
|---|---|---|---|
| AckPush | Buttons or a typed reply, from the lock screen | Returned to the waiting call, the MCP tool or a signed webhook | Nothing |
| Push services (ntfy, Pushover and others) | Mostly one-way alerts; some offer buttons that open a link or call a URL | You host an endpoint for each button and match it to the request | The answer endpoint and the waiting |
| Chat bots (Slack, Telegram) | A message in a busy channel | Your bot reads replies and works out which question they belong to | A bot, its hosting and reply parsing |
| Whenever someone opens the inbox | Someone reads it and acts by hand | A person in the loop, with a delay |
Stop babysitting the terminal
AckPush is in a private beta, free for founding members during the beta. Tell us what you'd have it ask you, and we'll send invites in small batches.