Feature request: built-in settings sync (like JetBrains/VS Code Settings Sync)

Summary

Request for a built-in settings sync feature in Claude Code, similar to JetBrains' Settings Sync or VS Code's Settings Sync — syncing config (settings.json, keybindings.json, custom commands/skills, memory files, etc.) across machines through Anthropic's own service, rather than relying on the user manually placing config in a third-party cloud-sync folder (Dropbox, Google Drive, iCloud Drive, etc.).

Motivation

Manually backing up Claude Code config into a cloud-sync folder is fragile in practice:

• Symlinking config files into a Drive/Dropbox-synced folder doesn't work reliably — cloud sync clients generally can't sync symlinks (they need real file content, not a pointer), so the sync silently fails or corrupts the client's internal sync state.
• Plain copies work but go stale immediately since they don't reflect ongoing changes.
• A recurring copy job is a reasonable workaround but is exactly the kind of thing a first-party settings-sync feature should handle natively, the way other editors already do.

Suggested behavior (roughly matching prior art)

• Opt-in sync of Claude Code settings/config across devices, tied to the user's Anthropic account.
• Cover at minimum: settings.json, keybindings.json, custom commands/skills, and (optionally) memory files.
• Conflict handling similar to JetBrains/VS Code Settings Sync (e.g., last-write-wins with a manual merge option, or per-machine overrides for local-only settings).

Happy to provide more detail on the specific pain points that led to this request if useful.