The AckPush story

0:00 Forty minutes for one word

It's Saturday, 6:40 a.m. Your coding agent has been working for an hour… and for the last forty minutes, it's been stuck. It needed one word from you: “yes.” Your phone buzzed. It told you something needed your attention. It just didn't let you answer.

0:25 Notifications tell. Your work needs to ask.

Notifications were built to tell us things. But the apps and agents we run today don't just need to tell us. They need to ask. Approve this payment. Run this command. Remind me tomorrow. Today that means a push from one app, an email from another, a chat bot for a third, and every answer means finding a laptop.

0:53 The answer is in the notification

AckPush is one place for every app and agent to reach you, and the notification is where you answer. Open it: Approve. Deny. Or type a reply right there, even with your phone locked.

Need more time? Snooze it from the app or the web inbox: an hour, tomorrow morning, next week. Snooze lives on the server, so the message comes back even if your phone was off. Every message has a lifecycle: sent, answered, snoozed, expired. And every answer goes straight back to the app that asked, the moment you tap.

1:35 Three ways in

There are three ways in. From any app, it's one HTTP call: a title, a body, and the buttons you want. The answer comes back two ways. Wait for it in the same request, or get a signed webhook as soon as you tap.

For Claude Code, there's a permission hook. When it wants to run a command, your phone shows Approve or Deny. Approve, and the command runs. Deny with a note, and Claude reads your note.

And any agent that speaks MCP gets the same powers: notify, ask, and wait for your reply. The buttons fit the decision: Approve and Hold. Yes and No. Accept and Decline.

2:24 A day with AckPush

Picture your property app watching the books. October rent for 4B comes in fifty dollars short. Instead of an email you'll read on Monday, it asks: reconcile October rent for 4B? $1,850 received, $1,900 due. You tap Approve in the grocery aisle, and the books are right.

Your coding agent is refactoring a service while you're at a soccer game. It wants to run the migration tests. Your phone buzzes, and you approve between plays. By halftime, the pull request is ready.

A planning agent hits a fork: ship Friday, or hold for review? You tap Hold and add a note: “need legal sign-off.” It rewrites the plan around your answer.

Not urgent? Snooze it until nine tomorrow morning. The server brings it back, so you don't have to remember.

3:31 Built for the answer

There are great push tools out there, and they're great at delivering a message. Getting a real answer back into your code, like a choice, a typed reply or a snooze, is a different job. There are agent approval tools too, but most of them work with one agent or one chat app.

AckPush is built for the answer: buttons and replies right on the notification, snooze handled on the server, one searchable history across every app and agent, ask-and-wait for any MCP assistant, and signed webhooks back to your code.

4:09 Let them ask

Your apps and agents are already doing the work. Let them ask. And answer from wherever you are: a grocery aisle, a sideline, a trail. That's AckPush: notifications you can answer. Request early access at ackpush.com.