A settings sync service for Zed that lets developers share editor config, keymaps, and extensions across machines with one sign-in and zero manual dotfile management
Zed's GitHub Discussion #6569 asking for settings sync has 316 reactions. A Zed maintainer explicitly stated in 2023: 'this is not currently on our roadmap, and it will likely not be added anytime soon.' The only third-party attempt (vittorius/zed-settings-sync) was rejected from the official Zed extension marketplace, has 26 stars, requires a manual CLI workaround, and cannot load settings from within the extension itself due to Zed API limitations. VS Code has Settings Sync built-in (syncs across GitHub/Microsoft account). JetBrains has IDE Settings Sync. For Zed, nothing works out of the box. The gap blocks teams adopting Zed as their standard editor because dev environment portability is a prerequisite for onboarding. Third-party opportunity: a hosted service (or extension + backend) that persists Zed settings, keymaps, tasks, and extension lists to a cloud account, with one-click restore on a new machine.
A CLI tool that keeps a Zed editor setup identical across every machine a developer works on
1.2k โฒScore Breakdown
Social Proof 2 sources
Gap Assessment
Real gap. Vendor explicitly said not on roadmap. No shipped third-party solution: the only attempt was rejected from the marketplace and requires CLI workaround. VS Code and JetBrains both have native settings sync, making this a documented migration blocker from those editors to Zed. Zed's user base is growing (active GitHub repo, 627-point HN thread 'Zed is our office'). Monetizable as a freemium hosted sync service or Zed extension with a paid cloud tier for team-shared config profiles.