Skip to content

Editions

KoNiMa Claude Sync ships as a single VSIX for all editions: it’s the license that decides which features are active. You can change edition — or move from a trial to a full license — without reinstalling anything. The editions differ above all in the sync domains they unlock.

What each edition unlocks

What it unlocksStarterProTeam
Configuration sync (rules, skills, commands, agents)✅✅✅
Plugin sync✅✅✅
MCP server sync❌✅✅
Memory sync (claude-mem + project .md)❌✅✅
Session hooks (automatic pull/push with Claude sessions)❌✅✅
Custom hook sync❌✅✅
Dual-repository CORE + MEMORIES governance❌❌✅
Managed seats + invite codes❌❌✅
Audit log❌❌✅

Configuration and plugins are included in all editions. Pro adds MCP servers, memories, and hooks. Team adds shared governance: dual repository, managed seats, invites, and audit. For the detail of what travels in each domain, see What it syncs.

You can upgrade at any time

You aren’t locked into the initial edition: you move up to a higher edition whenever you want, without reinstalling and without losing anything. As soon as the new license is active, the additional modules unlock immediately and the dashboard updates — the new tabs and the new sync domains appear. The same goes for moving from a trial to a full license.

A "License updated" notification listing the new modules unlocked after a license upgrade After a license upgrade, the extension lists the modules just unlocked.

Which edition to choose

  • Starter — a single workstation that wants to carry its configuration and plugins along in a versioned copy. Ideal for someone working from a single machine.
  • Pro — several personal machines with memories, MCP servers, and hooks. Designed for the developer who alternates between desktop and laptop and wants Claude to “remember” everywhere.
  • Team — several people sharing a governed company baseline, with roles, invites, managed seats, and audit.

Machine limit

Each edition allows a certain number of machines (the seats). The limit is set by your license and is always visible in the dashboard, in the Machines tab, in the form {used}/{max}.

Seats are freed at any time by deactivating a machine from the dashboard: recovery is manual and deliberate.

Team governance: two repositories

With the Team edition, setup requires two repositories, because governance separates managed configuration from shared memories:

  • CORE repository — governed configuration. The company baseline (rules, skills, commands, agents). Maintainers write it; members receive it read-only.
  • MEMORIES repository — team memories. Project memory, the seat registry, and audit. All participants contribute, including those who are read-only on CORE.

A single wizard configures both when the provider and organization match.

Roles and permissions

The role isn’t configured in the app: it’s derived from your account’s permissions on the git repository.

  • Maintainer — writes CORE: manages the baseline, plugins, invites, and repository maintenance, can deactivate machines and merge projects.
  • Member — read-only on CORE, read-write on the MEMORIES repository: receives the configuration and contributes memories.
  • Viewer — read-only view.

Seats and invite codes

In the Team edition, new members join via an invite code (KNMI-…) generated by a maintainer: in a single step it activates the team license and configures the repositories with the new member’s credentials. Invite codes are never stored.

Effects on the dashboard

The dashboard shows only what your edition includes — unavailable tabs don’t appear, they don’t look disabled:

  • without the Plugins module, the Plugins tab is absent;
  • without Memories, the Memory and Projects tabs are absent;
  • without Audit, the Audit tab is absent;
  • with the Team module, the Team tab appears, the roster views are renamed “team”, and setup requires the two repositories.