Claude Sync — KoNiMa

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 keeps that profile in a git repository you own, and rebuilds it on every machine you or your team use.

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 data, not just time:

	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	installs from a marketplace, tracks no one's 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.

Area	What travels
Memories	Claude's memories and per-project notes, merged and deduplicated across machines, so every machine knows what the others learned; a project is recognised by its git remote, wherever it sits on disk
Sessions	The Claude Code conversations you pick with `/sync-session` travel to your other machines, so you can resume one where you left off with `claude -r`; encrypted, private to you, never shared with the team
Configuration	Rules, skills, slash commands, agents, `settings.json` and `CLAUDE.md`, copied and switched on, so Claude Code actually uses them
Custom plugins	Your team's hand-written Claude Code plugins, 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

Each area is optional. What is available depends on your edition: one install, and your license decides what is switched on.

On a team, every item is yours to place: share a skill, rule, command, agent, hook or custom plugin with the whole team, or keep it private to your own machines. A private item syncs across the machines you use without ever reaching the team; share it back whenever you want.

The team's configuration has one owner, and everyone else can still improve it:

Propose instead of overwrite. A member who improves a team skill, rule, command, agent, hook or plugin sends it to the maintainer as a proposal. The maintainer reads every file, then accepts or declines with a reason, and the member sees the outcome in the Team tab.
Your edits are not lost. A change you make to a team item stays on your machine until the team publishes a new version of it. When that happens, your copy is kept next to the team's and you decide: compare them, keep the team's, or keep yours and propose it.
One place to decide. When the team replaces an item you changed, or a maintainer's edit conflicts with the team's, the choice waits in Waiting for your decision, on the dashboard Overview, until you make it.
Leaving is clean. A member who leaves removes only the team's items. Anything a team item had replaced is restored, everything the member created stays, and a copy of what was removed is kept for 14 days.
Hold a plugin update. When a new version of a plugin needs checking first, the maintainer holds it for the whole team until it is cleared.

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
Resume a Claude Code session on another of your machines	—	Yes	Yes
Sync runs on its own when a Claude Code session starts and ends	—	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
Keep any item private to your own machines, or share it with the team	—	—	Yes
Members propose improvements; the maintainer approves them	—	—	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. Your machines are counted in your own repository, and you can free one at any time from the dashboard.

How it works

Install Claude Sync from the VS Code Marketplace.
The setup wizard opens on first launch (or click Claude Sync in 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 what to sync and press Sync now.
Repeat on your next machine, and your setup is there.

Without a valid license, the extension does nothing.

Designed to be safe

Nothing is overwritten blindly. Every pull reconciles three versions (yours, the repository's and the last one this machine agreed on) and takes a local backup before anything is applied.
No force-push, ever. When two versions disagree, the choice waits for you in the dashboard and is never made silently.
A way back with every update. Before a new version of Claude Sync writes to your repository, it keeps the previous state there.
Running a sync twice never duplicates or loses anything, and with several VS Code windows open only one of them syncs while the others follow.
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, and credential are blanked before anything reaches the repository.
Secrets at rest. Your git token and license key are stored in the OS keychain through VS Code's secret storage. They are never written to disk or to the output channel.
Activity privacy. The repository records when each machine was last seen by the day only, so it cannot be used to track anyone's working hours.
GDPR Art. 25/32 privacy-by-design posture. For supply-chain reviews: a committed dependency lockfile, distribution signed by the Visual Studio Marketplace, and a security disclosure address (see Support).

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 to sync memories from the claude-mem plugin. Claude Code's own memory files and everything else need nothing extra.
A git repository you control, reachable over HTTPS or a local network path.
Claude Code installed, since it is what Claude Sync keeps in step.

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: assistenza@konima.it