If you've been running Beadbox alongside the bd CLI in embedded mode, you've probably seen flock errors. The embedded Dolt backend uses exclusive file locks, and when both Beadbox's polling and your terminal commands compete for the same lock, one of them loses. In v0.23.1, we added a 2-second debounce to Beadbox's change detection and expanded the retry window. The lock contention that caused those errors should be gone.
There was also a failure mode that Windows users noticed first, though it wasn't platform-specific: when the Node.js backend process died mid-session, Beadbox just kept rendering the last known state. No error message, no indication anything was wrong. You'd click around, eventually hit "Failed to fetch," and have no option except restarting the whole app. We added a sidecar health monitor that catches backend crashes and shows a recovery screen with a one-click restart.
@red-dot-camel filed #17 with a clear reproduction path for a Windows-specific issue: workspaces living on non-home drives would lose their connection on every tab switch. Detailed enough that we reproduced and patched it the same day. Bug reports like this one save us weeks of guessing.
Upgrade with brew upgrade beads-ui or download from beadbox.app. Full release notes in the announcement discussion.