changelog

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 pages
• 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/