changelog

We’ve added two more agent integrations for relay rules, so you can route alerts into either one the same way you already route into Devin or Cursor.

• AWS DevOps Agent — sends the alert to an Agent Space webhook and polls backlog task status via the AWS SDK. HMAC or bearer webhook auth, plus IAM credentials (with optional STS AssumeRole for cross-account).
• OpenCode — connects to a self-hosted OpenCode server, creates a session, and dispatches the alert as an async prompt. HTTP Basic auth, optional model pinning via openCodeModel.

Both follow the same storm detection and dedup behavior as the existing agents, so nothing changes in how you write rules.

Read more about agent integrations at: https://beeps.dev/docs/agent-integrations/overview/

We’ve shipped @beepsdev/cli on npm, so you can run your on-call from a terminal instead of clicking around the web app or writing SDK scripts.

npm install -g @beepsdev/cli

It covers relays, schedules, alerts, integrations, and agent jobs:

• Triage alerts in-flight — beeps alert list --active, beeps alert on-it, beeps alert resolve, plus beeps alert responders and beeps alert agents to see who (and which AI agents) are working on it
• Manage your rotation — create schedules, add members, drop in PTO overrides, check who’s on-call right now (beeps schedule on-call)
• JSON output — every command takes --json so you can pipe through jq and script around it
• Infrastructure as code — define relays in YAML, then beeps relay plan / apply / export to keep your on-call setup version controlled. beeps relay lint and beeps relay simulate catch misconfigs before they beep someone at 3am

Read more at: https://beeps.dev/docs/using-beeps/cli/

As we’ve been rolling out beeps to users, we’ve noticed there were some ergonomics in our SDK/API that needed cleaning up, namely properly defining handoff days and times. We previously called these startDay and startTime but now are more properly handoffDay and handoffTime.

In addition, we’ve made over 25 small fixes to improve the experience of using beeps on the web frontend during on-boarding. Please reach out to help@beeps.dev if you run into any problems and we’ll fix asap!

We’re notably building beeps without a user interface, instead building on developer paradigms for access so that developers and agents interact with beeps in a common way.

It’s a bit fun in 2026 to have a terminal experience, so we’re releasing the beeps-terminal as both a reference project for using the @beepsdev/sdk as well as an interactive ui for developers to use while they’re on-call with beeps.

Learn more at: https://beeps.dev/docs/using-beeps/terminal/

beeps now automatically detects alert storms: bursts of related alerts that fire within a short window. Instead of triggering a fix by an agent every time, storm detection groups them and makes sure you don’t waste tokens or agent effort.

• Automatic grouping — alerts from the same service within a configurable time window are collapsed
• Storm summary — responders see a count and breakdown instead of a flood of beeps
• Configurable thresholds — set the alert count and time window that triggers storm mode

Read more about alert storms at: https://beeps.dev/docs/alert-storms/overview/