First launch and setup

You’ve installed the extension: now you put it to work. In a few minutes you activate your license, connect your git repository, and bring the first machine to convergence. Everything happens from the dashboard, which opens on its own at first launch.

The showcase at first launch, before activating a license: from here you activate a code or start a trial.

The steps

1. Activate your license (or start a trial).

   Without a license, the dashboard shows the editions showcase. You have two paths:

   I already have a license

   In the Already have a license? panel, paste the code into the Paste your license code field and click Activate. The license is verified online and activated.

   A code starting with KNMI- is instead a team invite: it opens the Join the team flow (see below).

   I want a trial

   In the Choose your edition section, from the Starter / Pro / Team cards, start the self-service trial. No credit card required. To prevent abuse, an anonymous machine identifier is generated — the raw identifier never leaves your computer.

2. Prepare the repository.

   Syncing happens through your git repository — no remote is preconfigured. Before connecting it, have these ready:

   • a private, empty repository on your git host (GitHub, GitLab, Gitea, Azure DevOps, or any remote reachable over HTTPS);
   • a personal access token (PAT) with read and write permissions;
   • the repository URL.

3. Connect the repository.

   In the Connect your repository form, enter the URL and, for private repositories, your username and token. Click Connect: the extension verifies that the repository is reachable and saves the credentials in the VS Code secret store — never in plaintext on disk. Once confirmed, Connected appears along with a prompt to reload.

4. Reload and sync.

   Click Reload now (or reload the VS Code window): the sync engine starts and the dashboard switches to operating mode. Choose which domains to sync and click Sync now.

5. Repeat on the next machine.

   Install the extension, activate the same license, connect the same repository: the second machine converges on the first machine’s configuration.

Joining a team with an invite code

If you received a KNMI-… code, paste it into the showcase and click Activate: the Join the team modal activates the team license and configures the repositories with your git credentials in a single step. Enter your name, email (for commit attribution), username, and the token for your personal git account.

Team edition: two repositories

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

• CORE — the company baseline (rules, skills, commands, agents): maintainers write it, members receive it read-only;
• MEMORIES — team memories, the seat registry, and audit: everyone contributes.

A single wizard configures both. Details in Editions.

After setup

Once the engine is running, the dashboard shows the operating tabs — Overview, Claude System, Machines, Projects, and the others included by your edition. The sync status is always visible in the status bar at the bottom (Claude Sync) and at the top of the dashboard.

• What it syncs — the domains and what travels in each.
• Editions — what each edition unlocks.
• Troubleshooting — if something doesn’t add up.