What it syncs
KoNiMa Claude Sync organizes what it syncs into independent domains. Each domain is opt-in and becomes available based on your edition: the same VSIX is installed everywhere — it’s the license that decides what’s available. Everything travels exclusively through your own git repository.
The domains at a glance
| Domain | What travels |
|---|---|
| Configuration | Rules, skills, slash commands, agents, settings.json, and CLAUDE.md — opt-in per individual domain. |
| Plugins | The inventory of installed plugins: install once, it propagates to every machine. |
| MCP servers | The MCP server definitions. Credentials are scrubbed before export and never reach the repository. |
| Memories | Claude’s memories and project notes, merged and deduplicated across machines; projects are recognized by their git remote. |
| Hooks | Claude Code’s custom hooks with their per-operating-system variants; a manifest reconnects them on any machine. |
Configuration
The heart of the product. The Claude Code configuration that lives in ~/.claude — rules, skills,
commands, agents, CLAUDE.md, and settings.json — becomes a consistent baseline across all your
machines. Every category is opt-in: you can sync skills but not commands, or the other way around.
Plugins
Your Claude Code plugin inventory travels with you. You install a plugin once and, on the next sync, every other machine receives it. Likewise, removing a plugin removes it everywhere: it’s a decision that applies to your entire fleet, so it requires explicit confirmation.
MCP servers
MCP server definitions sync across machines, but with one essential safeguard: credentials never
leave your machine. Before export, the values of keys matching token, secret, key,
password, auth, bearer, and credential are wiped. What lands in the repository is the
server’s structure, not its secrets.
Memories
Claude’s memories and project notes are merged and deduplicated across machines: each machine brings along what the others have learned. Projects are identified by their git remote, not by their local path — so the same project, cloned into different folders on different machines, is still recognized, and its memories are remapped onto the correct local folder. The Memories domain requires an edition that includes it.
Hooks
Claude Code’s custom hooks travel with their per-operating-system variants: a single manifest knows which executable variant to use on Windows, macOS, or Linux. If a hook has no valid variant for the current machine, the app reports it instead of running it to no effect.
Designed to be safe
Syncing follows a few principles that prevent lost work:
- Your changes always win. A pull never blindly overwrites local work: a three-way reconciliation is performed against a per-machine baseline, and before anything is applied a local backup snapshot is saved.
- No force-push, ever. Conflicts are shown in the dashboard and never resolved silently.
- Idempotent. Every operation is declarative and can be re-run without harm.
- Multi-window aware. A single VS Code window drives the sync; the others follow without collisions.
- Offline tolerant. Failed pushes are queued and retried; the license works offline for up to seven days from the last successful validation.
What never travels
Your data never passes through KoNiMa’s servers. The only endpoint contacted is the license API, and only for validation (and, when requesting a trial, an anonymous, one-way hash of the machine to prevent abuse). Repository credentials and the license key stay in the VS Code secret store, never written to disk.