Never set up Claude Code twice — and never lose what Claude has learned.
Why
Claude Code becomes more powerful the more you shape it: rules, skills, slash commands, agents, plugins, MCP servers, project memories. All of that lives on one machine. Switch to your laptop and Claude has forgotten who you are.
Rebuilding a Claude setup by hand costs an afternoon. What Claude learned about your projects cannot be rebuilt at all.
Claude Sync turns that per-machine profile into a versioned, portable identity that follows you — and your team — everywhere, through a git repository you own and control.
What you get that a repository alone cannot give you
Copying files is the easy part, and a git repo with symlinks does it. These are the places where that approach stops working — two of them lose you something rather than merely inconveniencing you:
| Do nothing | Git repo + symlinks | Claude Code natively | Claude Sync | |
|---|---|---|---|---|
| A new machine is ready in | hours, by hand | minutes, if you remember how | partial | minutes, automatic |
| Global skills and commands | rebuild them | copied, not activated | no mechanism | carried and registered |
| Claude's memories | lost | a git conflict: you discard one side | machine-local by design | merged and deduplicated |
| Installed plugins | reinstall each one | a list on paper | one marketplace at a time | inventory propagated |
| MCP servers | reconfigure | risk of committing credentials | — | credentials stripped before export |
| A uniform setup across a team | hope | everyone their own | marketplace = source, not inventory | approved inventory + audit |
| Where your data lives | — | your repository | — | your repository |
Why not just use a git repository?
You could sync ~/.claude with a git repository. It works — until two machines both write a
memory file: git hands you a conflict, and resolving it means discarding one side. Claude Sync
merges them. And a plain repository will happily commit your MCP credentials; Claude Sync strips
them before export.
What it syncs
The first three rows are the ones Claude Code has no mechanism for — they are why this product exists. The rest is convenience.
| Domain | What travels |
|---|---|
| Memories | Claude's memories and per-project notes, merged and deduplicated across machines — every machine carries what the others learned; projects are matched by git remote |
| Configuration | Rules, skills, slash commands, agents, settings.json and CLAUDE.md — carried and registered, so they are actually active; per-domain opt-in |
| Custom plugins | Your team's hand-written, local Claude Code plugins — distributed and installed on every machine |
| Plugins | Your installed plugin inventory; install once, propagated to every machine |
| MCP servers | Server definitions sync across machines; credential values are scrubbed before export and never reach the repository |
| Hooks | Custom Claude Code hooks travel with their cross-platform OS variants; one manifest wires them up on any machine |
All domains are opt-in. What is available depends on your edition — the same VSIX, the license decides.
Editions
| Starter | Pro | Team | |
|---|---|---|---|
| Your workstation, identical on every machine | Yes | Yes | Yes |
| Your plugins, installed everywhere | Yes | Yes | Yes |
| Your MCP servers everywhere — without exposing credentials | — | Yes | Yes |
| Claude remembers your projects wherever you work | — | Yes | Yes |
| Everything stays aligned around each session, automatically | — | Yes | Yes |
| Your custom hooks run on every machine, on any OS | — | Yes | Yes |
| Your in-house plugins, installed on every machine | — | Yes | Yes |
| The team works from the approved configuration, not their own | — | — | Yes |
| Add or free a machine when you need to | — | — | Yes |
| You know who changed what, and when | — | — | Yes |
| Multiple machines | 1 | Up to edition limit | Up to edition limit |
A free self-service trial is available for each edition directly from the extension — no card required. Machine seats are governed through your own sync repository; free a seat at any time by deactivating a machine from the dashboard.
How it works
- Install Claude Sync from the VS Code Marketplace or Open VSX.
- The setup wizard opens on first launch (or click
Claude Syncin the status bar). - Activate your license — or request a free trial right from the wizard.
- Connect your repository: any GitHub, GitLab, Gitea, Azure DevOps, or self-hosted git remote you control, over HTTPS. Your credentials stay in the OS keychain.
- Choose which domains to sync and press Sync now.
- Repeat on your next machine and watch it converge.
The extension is inert without a valid license code.
Designed to be safe
- Your edits always win. A pull never blindly overwrites local work — a 3-way reconcile against a per-machine baseline is performed, and a local backup snapshot is taken before anything is applied.
- No force-push, ever. Conflicts are surfaced in the dashboard and never resolved silently.
- Idempotent. Every operation is declarative and safe to re-run.
- Multi-window aware. One VS Code window drives the sync; the others follow without collision.
- Works around every session. Configuration and memories sync at the start and end of each Claude Code session — even with VS Code closed.
- Offline friendly. Failed pushes queue locally and retry; the license works offline for up to seven days from the last successful validation.
Privacy & security
- Your data never touches KoNiMa servers. Configuration, memories, and plugin inventory travel exclusively through your own git repository.
- No telemetry, no analytics. The extension sends nothing to anyone except one endpoint: the KoNiMa license API, contacted only for license validation and (on trial requests only) a salted, one-way device hash for abuse prevention. The raw device identifier never leaves your machine.
- MCP credentials are scrubbed on export. Values of keys matching
token,secret,key,password,auth,bearer, andcredentialare blanked before anything reaches the repository. - Secrets at rest — your git token and license key are stored in the OS keychain via VS Code's SecretStorage. They are never written to disk or to the output channel.
- Seat registry privacy — machine timestamps in the repository are recorded at day granularity by design, avoiding fine-grained activity tracking.
- GDPR Art. 25/32 privacy-by-design posture; NIS2 supply-chain readiness (SBOM, signed distribution, dependency lockfile, vulnerability disclosure channel).
Privacy Policy: https://konima.it/privacy. The terms governing your use are set out in the bundled End User License Agreement (the License tab on this listing).
Requirements
- VS Code 1.90+ on Windows, macOS, or Linux — fully native, no WSL, no extra runtime.
- Git accessible on your
PATH. - Node.js 23.4+ — only if memory sync is enabled (it reads the claude-mem database through the built-in SQLite). Configuration sync needs no Node.
- A git repository you control, reachable over HTTPS or a local network path.
- Claude Code installed — it is what we are syncing.
Languages
English, Italiano, Deutsch, Français, Español, English (UK).
Documentation
The full product manual — getting started, per-feature guides, troubleshooting and reference — is available online at documents.konima.it/claude-sync (English, Italian, German, French and Spanish). Inside the extension you can open it any time from the dashboard Guide tab → Open the full online manual.
Commercial license
Claude Sync is a commercial product by KoNiMa S.r.l. Use requires a valid license code issued by KoNiMa S.r.l. Full terms are in the End User License Agreement (EULA v1.0, effective 8 June 2026 — see the License tab on this listing). The Software is licensed, not sold; there is no free tier.
Support
Trials, licensing, general enquiries and security disclosures: [email protected]
© 2026 KoNiMa S.r.l. All rights reserved.