Share a Claude Code setup with a group of friends, through one private GitHub repo.
Settings, CLAUDE.md, skills, agents, commands and plugin marketplaces stay in step on every machine.
claude-sync is a small desktop app that shares a Claude Code setup with a group of friends. The group shares settings, CLAUDE.md instructions, skills, subagents, slash commands, output styles and plugin marketplaces. Everything lives in a private GitHub repo that one member of the group owns.
The app sits in the tray and starts when you log in. When someone in the group changes a shared file, the change reaches everyone's machines within about a minute. When you edit a shared file yourself, the app asks whether to share the change with the group or keep it on your machine.
It runs on Windows and macOS. Linux (x86_64, .deb and .AppImage) is in beta: it needs a desktop with a system tray (AppIndicator), a Secret Service keyring (GNOME Keyring or KWallet) and systemd for scheduled jobs. CI builds and tests it on Ubuntu, but nobody has run it on a desktop yet.
(The screenshots use made-up people and groups.)
- One private GitHub repo holds the group's setup; a change reaches every member's machine within about a minute.
- You choose what lands on your machine: changes to the shared
CLAUDE.mdwait for your Accept or Decline. - Your own
CLAUDE.mdand Claude's memories can follow you between your computers, in a private repo on your account. - Runs in the tray, starts at login; a headless
claude-sync-clicovers servers and WSL. - Sign-in uses GitHub's device flow; the token stays in the operating system's keychain.
- The host creates a group: a private repo on their GitHub account with the shared files.
- Members join by invitation. Only the host can change the group; members propose changes as pull requests.
- The app on each machine compares the repo with your
~/.claudefolder and applies the differences, asking before it shares or replaces anything of yours. Details are in docs/architecture.md.
Download the latest version from the Releases page:
- Windows:
claude-sync_<version>_windows_x86_64-setup.exe. The installer is not code-signed, so Windows SmartScreen may say it "protected your PC". Click More info, then Run anyway. - macOS:
claude-sync_<version>_darwin_universal.dmg. The app is not notarized by Apple, so macOS may refuse to open it the first time. Open it from the Applications folder with right-click, Open, or allow it in System Settings, Privacy & Security.
The app updates itself after that.
The headless claude-sync-cli needs no display. Install it with no sudo:
curl -fsSL https://raw.githubusercontent.com/MehdiMamas/claude-sync/main/scripts/install-cli.sh | bash
claude-sync-cli login # shows a code to enter at github.com/login/device
claude-sync-cli join <owner/repo>
claude-sync-cli service install # keeps it syncing (systemd user unit, or cron)Before the first join it backs up your CLAUDE.md to ~/.claude-sync/backup/ and removes group text you had pasted into it. claude-sync-cli update installs newer releases. Run claude-sync-cli with no arguments for every command.
- Open claude-sync and click Sign in with GitHub. Your browser opens GitHub; enter the code the app shows.
- To start a group, click Create a group and give it a name. The app creates a private repo on your GitHub account. You are the group's host. The app offers your own
CLAUDE.mdinstructions as the group's startingCLAUDE.md: check what it shows, remove anything personal, and it takes them out of your own file so Claude does not read them twice. In a group you host, Share my CLAUDE.md adds them later. - To invite friends, open the group and add their GitHub logins. GitHub sends each of them an invitation. Only the host adds or removes members. Members get read-only access; the app sets a rule on the repo so nobody else can change it, and if GitHub can't (a private repo on a free plan) it still only sends changes from the host's machine and tells you.
- To join, a friend installs claude-sync and signs in. The invitation shows under Pending invitations. They click Accept and the app sets up the group on their machine. Only the host can change a group: a member's edits stay on their machine, and they propose changes to the host as a pull request on the group repo.
- In several groups? Copy to another group on a group's page copies lines of its
CLAUDE.md(pick whole sections or single lines, and check the preview), its skills, agents and settings to another group you host. Secrets are redacted first, and what the other group already has in another version is refused, never overwritten.
The app tells you when something happens (an invitation, a conflict, an update, plugins to reload). If you miss a notification, click the bell next to the app name: every notification is kept there. You can turn desktop notifications off in Settings; they are still kept in the app.
When another member adds or removes lines in a group's CLAUDE.md, nothing changes in yours until you say so. The app tells you, and the group's page shows each change with who made it, so you can Accept or Decline it. A line you decline stays out (or, for a removal, stays in) and you are not asked about it again. Declining only affects you: it never undoes the change for the rest of the group. Your own changes, from any of your computers, apply at once. Each group is reviewed on its own, so deleting a line in one group never removes it from another. To have everyone's changes apply at once, turn off Review changes others make to CLAUDE.md on the group's page.
When two of your groups, or a group and your own CLAUDE.md, say the same thing twice or the opposite, or set the same setting differently, the group's page lists them under Conflicts, with both sides and the group names. For each one, keep one side (the other is left out on your computer only, never for the rest of the group), or edit the group's line, which the other members then review. Before you share or copy lines, the app warns about the ones that would clash. The check compares words; it does not ask Claude what the rules mean.
What you tell Claude to remember about you is yours, not the group's. Turn on Settings → Personal memory and your own CLAUDE.md text and Claude's memories (the memory folder of each project) follow you to your other computers. The app keeps them in a private repo on your account, <your login>/claude-sync-personal. Your other computers join it automatically when they sign in with the same GitHub account; you can switch that off, choose what syncs, see and remove your devices, or turn it off on one computer. Turning it off leaves your files and the repo as they are.
Each person can sign in on as many computers as they like. Before the app changes one of your own files for the first time, it saves a copy in ~/.claude-sync/backups/. When two people change the same file at once, the group's version wins and your version is saved next to it.
Turn on SSH between your own computers with claude-sync-cli ssh enable (or claude-sync ssh enable, the same in the app). Each of your computers then publishes its public key and name through your personal repo, and the others add them: the key goes into a marked block of ~/.ssh/authorized_keys (only from Tailscale addresses, no agent or X11 forwarding) and the name into ~/.ssh/claude-sync.conf, which ~/.ssh/config includes on its first line. After the next sync you can type ssh mac or ssh pc; change this computer's name with ssh alias <name>. It needs Tailscale (or a reachable host name) and the SSH server turned on (macOS: Remote Login). The choice is for all your computers; ssh disable removes everything it wrote. Personal memory sync must be on, since the records travel through it. Windows gets the names but its authorized_keys is not changed.
Sign-in uses GitHub's device flow and asks for two scopes:
repo: to create the group's private repo on your account, invite members to it, accept invitations, and read and write the shared files. GitHub has no smaller scope that covers private repos.read:user: to read your GitHub login.
The app finds group repos by their claude-sync-group topic. It does not read or change your other repos.
A group can share Claude Code plugins. A plugin runs code on every member's machine. Settings, hooks and skills from the group also change what Claude Code does on your computer. Only join groups whose members you trust, and only add people you trust to your own group.
A group repo can hold a schedules.json that asks Claude Code to run a prompt on a schedule, for example a weekly refresh of everyone's setup. The tray app registers a job with Task Scheduler (Windows), launchd (macOS) or a systemd user timer (Linux) only after you accept it on the group's screen, which shows the prompt, its options, the permission mode and the schedule. Any change to the job needs your OK again, and each job has an on/off toggle. If you trust a group, you can let its jobs run without asking (off by default, per device); you then get a notification for each new or changed job instead. The app also installs the plugins a group turns on (claude plugin install) and shows on the group screen any it could not install. Details are in docs/architecture.md §17 and §18.
- Your GitHub token is kept in the operating system's keychain (Windows Credential Manager, macOS Keychain, Linux Secret Service). It is never written to files or logs.
- Your group's files stay in the private repo on GitHub and on the members' computers. There is no claude-sync server that stores them.
- Personal memory is only yours. It goes to a private repo on your own GitHub account, and only your own computers read it. It never goes into a group repo, and group members are never added to it. The app refuses to use the repo if it is made public. The same secret check runs before anything is pushed, and memory files over 256 KB stay on their computer.
- The app's update checks and the feedback form go through a small web service (the relay, in
relay/). It uses your GitHub token to check who you are and, for feedback, to open the issue under your account. It does not save the token. If GitHub does not let your account open the issue, the app shows why; the report is never filed under anyone else's name. - Explain and Summarise use your Claude Code login. The optional helper runs the
claudecommand on your computer; there is no API key. The text is checked for secrets first and only sent when you click. - Feedback is public, its attachments are not. The feedback form opens a public issue on this repo under your GitHub account. Anyone can read its title, the description and your GitHub username. The screenshot and the logs go to a private repo that only the maintainer can read, never into the issue. Logs are off by default; if you include them, tokens are removed but file paths and repo names can still show. Later the maintainer runs a triage script on their own computer, where the local Claude Code (their own Claude login, no API key) reads the report, its attachments and the code, and comments a summary with a fix plan on the issue as the triage GitHub App bot (never as the maintainer), without copying private details from the attachments.
- Before it shares a file, the app checks it for tokens and keys and refuses to share a file that has one. Tokens are also removed from the app's logs.
You need Rust (stable), Node 22 or later, and pnpm.
pnpm -C app/ui install
pnpm -C app install
pnpm -C app tauri dev
The layout:
crates/core: the sync engine (Rust libraryclaude-sync-core).app/src-tauri: the desktop app (Tauri 2): tray, background sync, commands for the window.app/ui: the app's window (TypeScript and Vite, no framework).relay/: the web service for updates and feedback (relay/README.md).
pnpm -C app/ui dev serves the window in a browser with a fake backend (?signedOut, ?empty and ?noHistory show other states).
Sign-in needs a GitHub OAuth app with device flow turned on: set CLAUDE_SYNC_GITHUB_CLIENT_ID when you build. Updates and feedback need CLAUDE_SYNC_RELAY_URL. A release build (pnpm -C app tauri build) signs its update bundles, so it also needs TAURI_SIGNING_PRIVATE_KEY and TAURI_SIGNING_PRIVATE_KEY_PASSWORD.
The design is in docs/architecture.md and releases are described in docs/releasing.md. To contribute, see CONTRIBUTING.md. To report a security problem, see SECURITY.md.
Thanks to everyone who helps, in code, docs, testing and ideas (emoji key). New here? Start with the good first issues and the Code of Conduct.
MIT. See LICENSE.






