Get notified when a
coding agent needs you.
BirdyBeep notifies your phone when a coding agent needs input or approval, finishes, fails, or goes idle.
npm i -g @birdybeep/cli - running tests
- editing auth/session.ts
- needs your approval
How it works
Pair each machine once.
Scan one QR on each machine. BirdyBeep installs hooks for the supported coding agents it finds and sends only lifecycle events.
- 1
Pair the machine
A short-lived QR code connects it to your phone.
birdybeep pair - 2
Install the hooks
BirdyBeep configures every supported harness it finds.
birdybeep agent install all - 3
Get notified
A session appears after its first event. BirdyBeep alerts you when it needs attention or stops running.
listening
BirdyBeep receives session starts, resumes, input and approval requests, idle states, completions, and failures. It sends nothing between events.
Supported agents
Supported coding agents.
session · permission · stop ready notify · lifecycle hooks ready session · idle · error ready session · tool · shell approval ready prompt · tool · stop ready Privacy
What BirdyBeep sends and stores.
BirdyBeep receives lifecycle events from installed hooks. Notification titles and bodies are used to deliver the push and are not stored. The CLI and adapters are open source.
- Notification content
- Never stored server-side
- Absolute paths
- Hashed or redacted
- Pairing proof
- Short-lived code, never a token
- Private Mode
- Free for every account
Install
Set up BirdyBeep in three commands.
-
1
$ npm i -g @birdybeep/cliInstall the open-source CLI.
-
2
$ birdybeep pairA QR appears. Scan it from the app to pair this machine once.
-
3
$ birdybeep agent install allConfigures every supported harness it finds. Future sessions appear automatically.
Pricing
100 beeps a month free. Unlimited with Plus.
Both plans include Private Mode. Plus has no monthly beep quota for ordinary personal use. Rate limits and abuse protections still apply. See Terms.
Questions
Before you install.
-
No — one QR pairs a machine. After
birdybeep agent install all, every session from every installed harness on that machine appears automatically. -
An existing session appears after its next event. Send a prompt, trigger an approval request, resume it, or restart it.
-
No. Adapters send lifecycle status and limited metadata. They do not send code or prompts, and BirdyBeep does not store notification titles or bodies. The CLI and adapters are public on GitHub.
-
No. BirdyBeep only sends notifications; approvals and replies still happen on your computer.
-
BirdyBeep does not poll or watch your terminal. Installed hooks send an event when the coding agent changes state.