The app shows a six-digit code. Hand it to your agent and it claims its own endpoint and saves it. There is no account, and nothing to install where the agent runs.

curl -X POST https://ping.buzzkit.dev/pair/claim \
  -d '{"code": "482913"}'

{ "endpoint": "https://ping.buzzkit.dev/bz_…", "mcp": "https://ping.buzzkit.dev/bz_…/mcp" }

After that, every update is a single POST. A finished piece of work is a notification.

curl -X POST https://ping.buzzkit.dev/YOUR_KEY \
  -d '{"title": "Tests passed", "body": "142 passed in 38s"}'

Add a session to keep a long task live on your lock screen while it runs, and set status to waiting when the agent is stuck, so it jumps to the top and the phone reads "Waiting on you".

POST https://ping.buzzkit.dev/YOUR_KEY
{
  "session": "buzzkit/ts-sdk",
  "title": "Running migrations",
  "body": "3 of 7 applied",
  "status": "working",
  "progress": 0.43,
  "agent": "claude-code",
  "project": "buzzkit"
}

Claude Code can point at the endpoint as a remote MCP server, so the tools show up with one command. Anything else reads ping.buzzkit.dev/skill.md and sets itself up from there.

claude mcp add --transport http buzz https://ping.buzzkit.dev/YOUR_KEY/mcp

Buzz is not a custom backend. It is a small app built on BuzzKit, the open-source framework the rest of this site is about, talking to the same public SDK and API you would.

BuzzKit does the heavy lifting: one workspace holds your APNs keys, every phone is a subscriber, and a single endpoint folds a dozen agents into one Live Activity behind one push token. Buzz barely has to do anything, and that is the point. When you build your own notifications, you start exactly where Buzz did.