Skip to content

Release notes

Version history for KoNiMa Claude Sync. Updates arrive from the store, like any other VS Code extension.

v1.4.0 — October 10, 2026

New

  • Proposals to the team. In the Team edition, a member proposes to the maintainer a skill, a rule, a command, an agent, a hook or a custom plugin, new or improved. The maintainer reads every file before deciding, accepts or declines with a reason, and the member finds in the Team tab their pending proposals, the declines to read and the history of every decision.
  • Your edits to team items stay yours. A team skill or rule you edit on your machine stays as it is until the team publishes a new version of it; from there you can propose it or go back to the team version.
  • One place for every choice between two versions. In the Overview, Waiting for your decision gathers every case where you decide which version to keep: you compare the two versions and choose with one click.
  • Sessions across machines. With the /sync-session command you take a Claude Code conversation to your other machines and resume it with claude -r. Only the sessions you choose travel, encrypted and visible only to you. Available with the session sync module.
  • Hooks and custom plugins that are only yours. Like skills, rules, commands and agents, hooks and custom plugins can also stay on your machines without reaching the team.
  • Keep on all my machines. An item the team doesn’t publish follows the member to every machine they use, with one click.
  • Date of the latest change next to every configuration item.
  • Hold updates for a plugin across the whole team, when a new version needs checking first.

Improved

  • A way back with every update: before a new version writes to the repository, Claude Sync keeps the previous state there.
  • A clearer skill count: the Overview separates your skills from the ones Claude Code downloads on its own.
  • Leaving the team removes only the team’s items: whoever leaves chooses whether to remove the skills, rules, commands, hooks and plugins that came from the team; whatever they replaced comes back and everything the person created stays. Remove Local Data offers the same choice.
  • Plugin updates when they don’t get in the way: they are applied when no sessions are open, and the app tells you when a session that’s already open needs restarting.
  • A faster, tidier dashboard: it opens more quickly, and your personal items stand out by the color of their row.
  • Lighter repositories: automatic maintenance keeps their size in check.
  • Clean uninstall: Remove Local Data also removes the components Claude Sync installed and the saved credentials.

v1.2.0 — July 27, 2026

  • Company-wide memory scope. On shared git services (GitHub, GitLab, Bitbucket, Codeberg, Gitea.com, SourceHut, Azure DevOps), the memories of your organization’s repositories are synced; those of personal repositories stay on the machine, and you can include them one by one. On your company’s own server the scope is the whole server.
  • Projects recognized by their remote, however they were cloned.
  • Deletion for the whole team: the maintainer deletes a shared item from every machine and can allow its name again with Revive.
  • A notice when a project folder can’t be matched to a folder on this machine, pointing to the log for the details.
  • Windows that respond right away: buttons show progress while they work, and dialogs close on success or stay open on error, so you can correct and try again.
  • Name and email on your changes: every change you send carries your identity, and the app asks for it if it’s missing.
  • Realign to the team: from User settings, any role can realign their machine to the team version with one click.
  • Pre-release channel: try upcoming features early from the extension’s page.

v1.1.0 — July 16, 2026

  • Syncing around every Claude Code session, even with the editor closed: configuration and project memories stay in step automatically at the start and end of each session, including sessions started from a terminal alone.
  • The Audit tab also records the syncs at the start and end of each session.
  • Custom Claude configuration folder: automatic detection of CLAUDE_CONFIG_DIR, a per-machine setting, and guided selection with Choose folder… in the System check.
  • A clear status when the Claude folder is missing or isn’t the right one: the Check setup warning, with a banner showing the folder it looked for.
  • Leave safely: any role can remove the license from their own machine (the seat is freed), with an optional restore of the personal configuration you had before joining the team, and a safety copy of the current state.
  • A more thorough system check: it also flags a system Node.js that is missing or too old for memory sync (23.4 or later is required; configuration sync is not affected).

v1.0.0 — July 1, 2026

First public version.

  • Configuration sync: rules, skills, slash commands, agents, settings.json and CLAUDE.md.
  • Plugin sync: a shared inventory, with installs and removals carried to every machine.
  • MCP server sync, without the credentials.
  • Memory sync (claude-mem and .md files), merged across machines and recognized per project.
  • Session hooks and custom hook sync, for every operating system.
  • Starter, Pro and Team editions on the same package: the license unlocks the modules, and you can upgrade your edition at any time without reinstalling.
  • Team edition: two repositories (shared configuration and memories), roles taken from git permissions, managed seats, invitation codes and an audit log.
  • A local safety copy before every change, and no machine overwriting another’s work.
  • Your data stays in your git repository, no telemetry. Interface in 6 languages.