Leaving a team or removing the license

Sooner or later a machine bows out: you switch computers, you leave a team, or you simply want to stop syncing here. KoNiMa Claude Sync makes leaving tidy and reversible — nothing is thrown away behind your back, and you can always come back.

Removing the license from this machine

Any role can remove the license from its own machine, without asking a maintainer. Two ways:

in the dashboard, on the System tab, the License card has a Remove license button;
or the Claude Sync: Remove license command from the command palette.

Before doing anything, the extension always asks for in-app confirmation. The message reminds you of the point that matters most: removing the license stops syncing on this machine only — “this machine stops syncing until a license is activated again; your team and the other machines are not affected.” Nobody else on the team is disturbed.

What happens after removal

Once you confirm:

syncing stops and the automatic sync around sessions is switched off;
the status bar shows the lock icon (“No valid license — click to activate.”);
the seat this machine occupied is freed for the team. If the repository is unreachable at that moment, the seat isn’t lost: it is freed at the team’s next sync. The app tells you so plainly, so you know the release is only deferred.

Two separate decisions

Removing the license and restoring your personal configuration are two separate choices. Removing the license does not touch your ~/.claude folder: the team’s configuration stays where it is. Only after removal does the product offer the restore, as a second question you can say no to. It never bundles it in on its own.

Restoring your personal configuration

The restore offer appears only if a usable copy exists of the configuration you had before joining the team. If you accept:

every synced folder is returned to its pre-enrollment snapshot and the team content is removed from this machine;
but before anything is touched, your current state is put safely aside: a backup copy is saved and kept for 14 days, so you can go back if you change your mind.

When it finishes, the product confirms where it left that copy: “Personal configuration restored — the corporate config was removed. A copy of the previous state is kept for the next 14 days.”

If you decline the offer, everything stays as it is: the team’s configuration remains on the machine until you decide otherwise.

The same offer also appears when a maintainer deactivates your machine from the team: the machine shows a farewell notice and proposes the restore in just the same way.

The restore offer modal: a question asking whether to bring back the configuration you had before joining the team, with Cancel and Restore my config buttons The restore offer that appears after you remove the license — each synced folder returns to its pre-enrollment snapshot, backed up first.

Coming back

Coming back is immediate: enter a valid license again and you resume exactly where you left off. The repository, credentials, and settings survive the removal — there is no first-run onboarding to repeat.

The only possible blocker is a full machine limit: if the team has reached its maximum number of machines, activation reports “No seats available — your team has reached its limit of machines. Ask your maintainer to free one from the Machines list.” Just free a seat (see the dashboard’s Machines tab) and try again.