Repository maintenance

Over time a sync repository builds up history and content that is no longer needed. The maintenance operations keep it tidy. You find them in the System tab of the dashboard, on one card per repository (in the Team edition, CORE repository — governed configuration and MEMORIES repository — team memories), and they are reserved for the maintainer. Reinitialize and Compact can also be started from the Command Palette.

Every operation asks for confirmation before it starts.

The operations

Reset

Downloads the local copy used for syncing again from the repository. Your Claude Code configuration and your license are not touched. Use it when this machine needs to start again from a clean copy. From the Command Palette you get the same result with Claude Sync: Reinitialize (wipe local clones and re-sync), which is available to every role.

Compact

Reduces the repository’s history to a single point, so it stays light. The earlier history remains recoverable on your repository. Compacting also starts on its own when the repository grows a lot.

Clean up

Removes from the repository the content that is no longer synced.

Change repo

Moves the team to a new repository:

Create the new repository, empty, on your git server.
On the repository’s card, click Change repo.
Enter the new repository’s URL, the username and the token, then confirm.

The whole history is copied to the new repository, and the old one keeps a pointer: the other machines follow it on their own at the next sync (with the same credentials, the switch is automatic). Keep the old repository reachable until every machine has moved to the new one.

When to use them

Situation	Operation
This machine needs to start again from a clean copy	Reset
The repository has grown a lot and you want to make it lighter	Compact
Content that is no longer synced is still there and you want it gone	Clean up
You moved or renamed the repository, or you’re changing git server	Change repo