Beads changelog: what's new each month
Every stable Beads release summarised by month: the highlights, new features, improvements, fixes and anything you need to act on. 3 months covered; the current month updates daily.
September 2026
2 releases: 1.3.0 → 1.3.1
September brought Beads 1.3.0 and 1.3.1 with improvements to proxied-server mode, fixes for stalled work and clone wedging, and more reliable exit codes for scripting.
Highlights
- Proxied-server workspace backups now work correctly.
- Fan-in no longer stalls ready work.
- Smart migrate gate prevents clones from wedging when behind the remote.
- Exit codes are now reliable for scripting and automation.
- bd purge can run orchestrator wisp retention sweeps.
New
- bd purge can orchestrate wisp retention sweeps with the --wisps-plane option.
- bd show --watch now exits with status 1 when an id cannot be found in proxied or direct mode.
Improved
- Proxied-server mode now handles dolt.auto-commit batch and off settings correctly.
- Smart migrate gate prevents clones that are behind the remote from wedging.
- Exit codes and output from bd close batch commands are now suitable for scripts to rely on.
Fixed
- Proxied-server workspaces can now create backups.
- Fan-in no longer stalls ready work.
- Smart migrate gate no longer wedges clones that are behind the remote.
- Refused batch ids in bd close batch now exit with non-zero status.
August 2026
1 release: 1.2.2
August brought an urgent schema recovery for users affected by v1.2.1 and v1.2.0. This release provides guided recovery steps and prevents further silent database corruption.
- v1.2.1, v1.2.0, and v1.1.1 retracted from Go module registry; users must upgrade to v1.2.2 before database recovery to avoid silent re-corruption.
Highlights
- Schema recovery guide with one-command rollback to v53 for affected databases.
- Environment variable workaround (BDIGNORESCHEMASKEW=1) available for immediate use.
- Improved error messages that point to recovery instructions instead of outdated advice.
- Go module retraction ensures clean upgrades via go install.
Improved
- Schema-mismatch errors now recognize the accidental-release window and guide users to the recovery process.
- Recovery guide includes copy-paste SQL steps for schema cursor rollback.
Fixed
- Prevented silent database re-migration when older 1.2.1 binaries remain in use during recovery.
- Schema corruption issue introduced in v1.2.1 and v1.2.0.
July 2026
2 releases: 1.1.0 → 1.1.2
July brought important stability improvements and new safeguards for Beads. The month focused on fixing migration issues and enhancing configuration consistency.
Highlights
- Smart remote-migrate gate is now enabled by default for safer migrations
- New reminders when agent configuration files diverge to keep them in sync
- Fixed working-set reconciliation to work past dirty-table migration guards
- Improved auto-export of JSONL data in SQL-server mode
New
- Divergence reminders between AGENTS.md and CLAUDE.md configuration files
Improved
- Working-set reconciliation commands now open past dirty-table migration guard
- Auto-export of JSONL in SQL-server mode via working-set state hash
- MCP lock refreshed for better dependency management
Fixed
- Schema v53 wisp dependency drift repaired
- Storage error handling in CloseIssue for sentinel parity
- CI blocker issues with divergence reminder
Summaries are written automatically from the official release notes (full changelog ↗); check the original notes before relying on a detail. Beads: pricing, features and alternatives · All changelogs