Pocket Notifier sends push notifications from my coding agents to my phone while they work, not only when they stop. When an agent finishes step 3 of 5, gets a review back, needs me to pick between two options, or hits a failure it can’t fix, I get a notification with the result in one line.
It is a remote MCP server with OAuth sign-in, so connecting an agent is one command and a browser login. An agent skill tells the agent when a notification is worth sending: a finished, checked unit of work with something measurable in it, like a step count, a test result or a PR number. Starting something, reading files and “still working” don’t count.
I wrote about why I built it.
How it works
Parts: Coding agents (Claude Code, Codex), Scripts and CI (bearer token), Hono Worker (MCP · REST · app API), D1 (projects, features, messages), Firebase Cloud Messaging (data-only message), Android app (one thread per feature).
- Coding agents to Hono Worker (MCP)
- Scripts and CI to Hono Worker (REST)
- Hono Worker to D1
- Hono Worker to Firebase Cloud Messaging (push)
- Firebase Cloud Messaging to Android app
Notifications are organized the way I track work. A project is a repository or product. A feature is one workstream inside it, like login-flow or search-cache, and in the app every feature is a chat thread. An agent lists the project’s features, reuses the one that matches its task, and keeps posting there for the whole workstream, across sessions. When the work ships, it marks the feature done. Deploys and CI runs go to the project’s own thread.
Priority decides how loud a message is. Each of the five levels is its own Android channel, from silent to a popup that can break through Do Not Disturb, so a milestone stays quiet in the shade and a question for me pops up. An agent that is blocked can send an ask with quick replies, and I can answer from the notification.
The stack
The server is one Hono Worker on Cloudflare that serves the MCP server, a public REST API for scripts and CI, and the oRPC API the app uses, with D1 through Drizzle as the database and better-auth for sessions and the OAuth provider. Push goes straight to Firebase Cloud Messaging as a data-only message, and a native Android module in the Expo app builds the notification itself, so it controls the channels, conversation grouping, avatars and reply actions. Messages expire on a retention schedule run by an hourly cron.
It is invite-only and runs on my own Cloudflare account, deployed with Alchemy from GitHub Actions on every push to main. The docs at notifier.bartuozel.com cover the API, the push payload and the decisions behind them.