The dashboard

The dashboard is the control center of KoNiMa Claude Sync: from here you see the sync status, manage this machine’s configuration, and govern machines, projects, plugins, and memories. It opens on its own at first launch, and you reopen it whenever you want from the status bar at the bottom or the Claude Sync: Open Dashboard command.

This page describes the elements common to every view — the info bar and the footer — and then each tab, one by one.

Elements common to every tab

All tabs share an info bar at the top and a footer at the bottom.

The info bar (top)

• ● {status} — the current sync status: Up to date, Pending, Syncing…, Error, or Changes pending upload.
• ↑{n} ↓{m} — the arrows count the outgoing items (local commits not yet pushed, domains with queued changes, and memories to upload) and the incoming ones. The tooltip lists what there is to send.
• ⟳ Refresh — forces a refresh of the view; the counter next to it indicates the automatic refresh (roughly every 30 seconds).
• Language selector — changes the interface language.
• Edition label — the active edition.
• Sync now — immediately starts a full sync cycle.

If the Claude folder isn’t found or isn’t the right one, a warning banner appears at the top of every tab and the status pill reads Check setup.

You won’t lose your place

The active tab, open accordions, and search filters survive the automatic refresh: you return exactly to where you were working.

Immediate feedback on every action

While an action runs, its button shows a busy state, so you can see the work is under way. Dialogs close on their own when the operation succeeds and stay open on error — with the message — so you can correct what you typed and try again without starting over.

The footer (bottom)

The footer carries the references to privacy, GDPR, and NIS2, the link to the Privacy policy, the product version (© KoNiMa S.r.l. · vX.Y.Z), and the Open on startup checkbox, which opens the dashboard when VS Code starts.

The tabs

The tab order is: Overview · Claude System · Machines · Projects · Plugins · Memory · Team · Audit · System · Help. The tabs your edition doesn’t include simply aren’t shown: they don’t appear disabled, they’re not there. Where a tab is available only from a certain edition onward, we note it below.

Overview

The big-picture view. It shows a grid of stat cards:

• Sync status — the current status and, below it, the outcome of the last sync (succeeded, failed, or not yet run). On error, the tooltip carries the message.
• Machines — how many machines are registered against your license limit (or ∞).
• Repository — number of commits, branches, and size. With the Team edition, two cards appear, Core repository and Memories repository. If the repository isn’t cloned yet, it shows —.
• Local changes — ✓ clean or ● pending, with the detail (↑x ↓y, the names of queued domains or the memories to upload).
• Projects — number of projects, with how many have synced memories.
• Memory worker — present only if memory support is installed: online or offline status, the process identifier, and uptime.

Below, the Synced configuration strip shows the count per type — Skills, Rules, Commands, Agents, Plugins, MCP servers, Project memories — and the Sync activity — last 14 days chart, one bar per day.

The Overview tab. The example is on the Team edition — that’s why some cards are “team” ones.

Claude System

Manages the configuration content present on this machine.

• Configuration files — the CLAUDE.md and settings.json cards open the respective files.
• Accordion by source — Skills, Rules, Commands, Agents: each with a count, a description, and an Open folder button. Each item has Open; a maintainer sees a Share with team switch, a member a status pill. Beyond 10 items a search filter appears.
• Team hooks — if present: for each hook you find Open, the trigger or the cadence, and — for the maintainer — the enable switch and quick access to hooks.json and the README. The note ⚠ no executable variant for this machine flags a hook that doesn’t apply here.
• Custom plugins accordion — if present: the count, the description “Team plugins installed on every machine.”, and the Open folder button; each plugin lists notes, a status pill, and Open — the maintainer also gets the enable switch, the Delete button (double-click confirmation, applies to the whole team at the next sync), and quick access to the manifest and the README. Details in Custom plugins.

Deleting a shared item is team-wide — and sticks

When a maintainer deletes a shared skill, rule, command, agent, hook, or custom plugin, the deletion reaches the whole team at the next sync and stays: a machine that was behind no longer brings the item back. At the bottom of each section the maintainer finds a Deleted by the team list with a Revive button next to each name — Revive re-allows the name so the item can be shared again; it does not restore the old content (recover that from git history or a backup). Members don’t have to do anything: a deleted item simply disappears and doesn’t come back. See Managing your configuration.

The Claude System tab (example on the Team edition).

Machines

The list of registered machines (the seats) against your license limit. The table reports the Machine (status, operating system, and name, with the this machine pill), the User, the Last sync, and any columns for memories and projects.

• Deactivate — for the maintainer only, on active machines: frees the seat occupied by that machine. Seat recovery is always manual and deliberate.
• A warning flags machines idle for 30 or more days, whose seats you can free.
• A reader (member or viewer) sees the list with others’ data masked as N/A.

Note

If your machine is deactivated, it is automatically reactivated at the next sync.

The Machines tab (example on the Team edition; machine names are redacted and other users’ data shows as N/A).

Projects

The recognized projects and their remapping onto local folders. Available on editions that include memories.

• A Search projects… box filters the list.
• Each project is identified by its git remote (e.g., owner/repo) and shows the number of machines, the number of memory files, and the Synced switch, which includes or excludes the project on this machine. Inside, you find the machine → local path list: this is where the remapping is visible — the same project in different folders on different machines.
• Merge projects — for the maintainer, with at least two projects: opens a modal to merge several projects into one, useful when the same project has been registered under different names.
• Out-of-scope projects and Unmapped projects (no git remote) are listed separately. A project is out of scope when it lives outside your company scope — on a shared host (GitHub, GitLab, Bitbucket, Codeberg, Gitea.com, SourceHut, Azure DevOps) that means outside your own organization, so its memories aren’t exported to the shared repository. Each one shows the reason, and a per-project switch lets you sync it anyway. Unmapped projects lack a git remote, so they can’t travel between machines. How the scope is decided is explained in What it syncs.
• If one or more project folders can’t be matched to a folder on this machine, a warning at the top of the tab says how many, and points you to the log (in the System tab) for the details — their memories aren’t syncing until the folders are found. Previously those projects went missing without a word.

Plugins

Your Claude Code plugin inventory.

• For each plugin: name and version. The maintainer has the enable switch and the Remove button (with double-click confirmation). The reader sees only the active/inactive status.
• Custom plugins appear here as a read-only mirror, with a status pill (Installed / Pending / Setup failed): they’re managed from the Claude System tab.

Caution

Enabling, disabling, or removing a plugin from here applies to all machines at the next sync. Removal deletes it everywhere.

Memory

Manages project memory. Requires an edition that includes memories.

• If memory support is installed, you see the Memory worker (online/offline), Local observations, Not yet synced (the backlog), and Memories repository cards.
• If it’s not installed, a card carries the command to install it, with a Copy button.
• Two switches choose the sources to sync: the database memories and the project .md memories. At the bottom you find the counts of .md files and of projects with memories.

Team Team

Visible only with the Team edition.

• If this machine has no identity yet, a card asks who you are — your name and email — and saves it (Save). The email lets your git host attribute the sync commits to you; without it they stay anonymous. You can change both later from the User settings panel.
• Members — list per member with their machines and role (Maintainer, Member, or Viewer).
• Generate invite code — for the maintainer: creates a code to share, with Copy, Send by email, and an expiration. Invite codes are never stored.
• Generated invites — table with date, author, expiration, and status (pending, redeemed, expired).
• A section explains the roles, which coincide with the git repository permissions.

Audit Pro Team

The history of changes. Visible on editions that provide audit retention and if you’re not a reader. The table lists When, Machine (by name), and Action (for example Changes uploaded, Changes applied from repository, plugin operations, Session-start sync, Session-end sync). The Export CSV button saves the history.

System

The maintenance operations, the license, the sync cadence, diagnostics, and logs. A reader sees only diagnostics, re-alignment, and the read-only license.

• Repository cards (Core / Memories) — URL and the buttons Reset (clears and re-clones the local clone), Compact (compresses the history into a single commit while keeping a recovery point), Clean (removes content no longer managed), and Change repo (migrates to another URL). Each action asks for in-app confirmation.
• Hooks Pro Team — Session hooks (pull at the start of a session and push at the end of a Claude Code session, even outside VS Code) and Sync custom hooks switches.
• Sync (cadence) — if the edition allows it, the Automatic sync select chooses between On startup / manual only, Hourly, or Every N hours; otherwise the cadence is fixed.
• License — edition, Granted to, Expires on, Machine role (detected from git permissions), and the Active modules chips. Actions: Verify now (revalidates the license), Change license, and Remove license.
• System check (diagnostics) and Re-align projects and memories. The check also verifies the Claude folder: if it’s not the right one, the Choose folder… button appears to fix it (details in The Claude folder), and it flags when the system Node.js needed for memory sync is missing or too old (23.4 or newer is required); in that case only memory sync stops, configuration sync is unaffected.
• At the bottom: Show log and the link to the Terms (EULA).

Reset without risk

The local clone is only a cache: the source of truth is your ~/.claude folder. Clearing and re-cloning it with Reset resolves many anomalous states without losing anything. The maintenance operations are safe to re-run and never rewrite the remote history. Details in Repository maintenance.

Help

An in-app accordion manual that shows only the sections relevant to the active modules and your role — getting started, configuration sync, plugins, MCP servers, memories, session hooks, custom hooks, team governance, repository maintenance, and troubleshooting. At the bottom you find Contact us, Send feedback, and the support address.

Continue from here

• What it syncs — the domains and what travels in each.
• Editions — what each edition unlocks and which tabs appear.
• Troubleshooting — if a status doesn’t add up.