CLI

Use the BeeBuzz CLI when the sender can run a command and you want the notification content encrypted before upload.

The CLI fetches your paired device public keys, encrypts locally, and sends ciphertext to BeeBuzz.

Install

With Homebrew:

brew tap beebuzz/tap https://codeberg.org/beebuzz/homebrew-tap
brew install beebuzz

With Go:

go install go.beebuzz.app/cli/cmd/beebuzz@latest

You can also download binaries from the CLI releases.

Check the install:

beebuzz version

Connect

Create an API token in the BeeBuzz web app, then run:

beebuzz connect

Paste the API token when prompted.

For hosted BeeBuzz, the CLI defaults to https://api.beebuzz.app.

Send

beebuzz send "Build finished"

Add a body:

beebuzz send "Build failed" "Deploy exited with code 1"

Send to a topic:

beebuzz send --topic alerts "CPU high"

Set priority:

beebuzz send --priority high "Door opened"

Attachments

Attach a local file:

beebuzz send --attachment ./snapshot.jpg "Motion detected"

Inline attachments sent by the CLI are encrypted before upload.

Attachment content is limited to 1 MiB.

Profiles

Profiles let one CLI install talk to more than one BeeBuzz account or instance.

beebuzz profile list
beebuzz profile use work
beebuzz profile show work
beebuzz profile delete work

Environment Variables

• BEEBUZZ_API_URL overrides the API URL
• BEEBUZZ_API_TOKEN provides the token without an interactive prompt

Precedence is:

1. flags
2. environment variables
3. profile
4. defaults

Common Issues

If the CLI cannot send:

• confirm the API token belongs to the same account as the paired device
• confirm the token can send to the target topic
• run beebuzz keys to refresh paired device keys
• check that the receiving device is still paired