@beepsdev/cli

@beepsdev/cli

Command-line interface for beeps — on-call alerting and incident response with AI agents.

Manage relays, schedules, alerts, integrations, and AI agent jobs from your terminal. Includes a real-time TUI dashboard for monitoring alerts as they come in.

Install

npm install -g @beepsdev/cli

Authentication

export BEEPS_ACCESS_TOKEN=<your-access-token>
beeps relay list

Or store it in a config file (chmod 600) and forget about it.

Relays

Relays are alert routing pipelines. Create them directly or manage them as code with plan and apply.

beeps relay list
beeps relay create --name "production on-call"

# infrastructure-as-code style
beeps relay plan -f relay.yaml --dry-run
beeps relay apply -f relay.yaml
beeps relay export -o relay.yaml

Catch misconfigurations before they beep someone at 3am:

beeps relay lint --relay-id rly_abc
beeps relay simulate --relay-id rly_abc --simulate-at "2026-04-04T03:00:00Z"

Relay rules

beeps relay rule list --relay-id rly_abc
beeps relay rule create --relay-id rly_abc \
  --name "notify on-call" \
  --rule-type schedule_notify \
  --config '{"scheduleId": "sch_primary"}'

Rule types: schedule_notify, webhook, agent.

Schedules

On-call rotations with weekly or daily handoffs.

beeps schedule create \
  --name "primary rotation" \
  --relay-id rly_abc \
  --type weekly \
  --handoff-day monday \
  --handoff-time "09:00"

beeps schedule add-member --schedule-id sch_abc --email [e-mail]
beeps schedule on-call --schedule-id sch_abc

Overrides

beeps schedule override create \
  --schedule-id sch_abc \
  --user-id usr_xyz \
  --start-at "2026-04-05T00:00:00Z" \
  --end-at "2026-04-06T00:00:00Z" \
  --reason "covering PTO"

Alerts

beeps alert list --active
beeps alert get --alert-id alt_123
beeps alert on-it --alert-id alt_123
beeps alert resolve --alert-id alt_123

# see who's responding and which AI agents are working on it
beeps alert responders --alert-id alt_123
beeps alert agents --alert-id alt_123

AI agent integrations

Connect AI agents like Devin and Cursor to your relays. When an alert fires, beeps dispatches an agent to start triaging.

beeps integration create \
  --provider devin \
  --name "devin - production" \
  --api-key-env DEVIN_API_KEY

beeps agent-job list
beeps agent-job status --job-id job_456

Providers: devin, cursor, slack, discord.

JSON output

Every command supports --json for scripting and piping:

beeps alert list --active --json | jq '.[0].severity'

Global options

--base-url <url>      Custom API endpoint
--config <file>       Config file path
--timeout <ms>        Request timeout (default: 10000)
--retries <count>     Retry attempts (default: 2)

Access tokens are read from BEEPS_ACCESS_TOKEN or the accessToken field of your config file. Passing tokens on the command line is not supported — argv is visible to other local users via ps / /proc/<pid>/cmdline.

Docs

Full documentation at beeps.dev/docs/using-beeps/cli.