VibeSync v0.2.5

Sessions now arrive on a new machine when you expect them to, and a first sync tells you what it's doing.

Fixed

Sessions could stop syncing to a machine, permanently. git_roots.json was written non-atomically and every read error fell back to an empty map — so a torn write silently re-keyed every transcript, which then read as "the user deleted all of these". That flag is one-way. Writes are now atomic, an unreadable map is distinguished from an absent one, and deletion marking is suppressed when it can't be trusted.

A project could take six or more syncs to appear. Newly discovered clone locations weren't republished to the fleet until the next sync, and discovery only searched one level out per run. Both fixed: discovery now runs to a fixed point and publishes what it finds in the same sync.

Repos cloned somewhere unusual were never found. An external drive, or a tree unlike anything on your other machines — VibeSync had no way to reach it, so those sessions waited until you opened the project in a tool. Point Settings → Code folders at where you keep repositories and they're found before you start working. Not needed if your repos live under your home folder.

Claude Code could be misdetected. The setup assistant and the syncer used different probes, and both mistook VibeSync's own synced files for an installation.

Improved

• A first sync against cloud storage no longer sits on a blank spinner — it now reports Connecting, Scanning, Reading storage, Uploading, Downloading
• debug.log is bounded continuously at 5 MB with one previous file kept, instead of only being checked when a sync started
• Folder pickers work from the menu bar popover (the popover was dismissing itself and taking the dialog with it)
• No browser context menu on right-click, except in text fields
• Storage line no longer repeats "(encrypted)"

---

See the assets below to download this version. latest.json is the auto-updater manifest.