Claude Sync

If you use Claude Code on more than one machine, your skills, commands, agents, and memory live on whichever computer you set them up on — and they stay there. I wanted them to follow me to every machine. But the contents of a ~/.claude directory are sensitive, so “just upload them somewhere” wasn't acceptable: the sync had to work without trusting the server with my files.

A desktop app (Electron) watches ~/.claude and syncs every 15 seconds. Files are encrypted on-device with libsodium before they ever leave, so the Fastify + Postgres relay only ever sees ciphertext — it ships bytes between your machines but can't read them. A CLI does the same headless, and a read-only web client decrypts locally in the browser (with the noble crypto libraries) so you can browse and diff your files from anywhere.

The encryption isn't a feature bolted on — it's the architecture. The server is intentionally zero-knowledge:

All four surfaces shipped — relay server, CLI, Electron desktop app, and the read-only web client. The Windows desktop build is released; macOS signing & notarization is the remaining step. The hardest part wasn't the sync loop, it was making “the server can't read your files” true end to end rather than a marketing line.