chrisor-dev/claude-autosync

Analysis updated 2026-05-18

★ 2ShellAudience · developerComplexity · 3/5LicenseSetup · moderate

Mindmap

mindmap
  root((claude-autosync))
    What it does
      Syncs CLAUDE.md rules
      Syncs project memory
      Syncs skills and commands
    How it works
      Symlinks to private repo
      Pull on session start
      Push on session end
    Setup
      Installer shell script
      Private GitHub repo
      Multi-platform support
    Security
      No data in public repo
      local.md never synced
      Opt-in for skills

mindmap root((claude-autosync)) What it does Syncs CLAUDE.md rules Syncs project memory Syncs skills and commands How it works Symlinks to private repo Pull on session start Push on session end Setup Installer shell script Private GitHub repo Multi-platform support Security No data in public repo local.md never synced Opt-in for skills

Click or tap to explore — scroll the page freely

What do people build with it?

USE CASE 1

Keep the same Claude Code rules and project memory across a laptop, desktop, and remote server.

USE CASE 2

Automatically back up your Claude Code CLAUDE.md and memory files to a private Git repository.

USE CASE 3

Add a new machine to your Claude Code setup by running a single installer script.

USE CASE 4

Selectively sync specific Claude skills and slash commands to all your machines.

What is it built with?

ShellGitPython

How does it compare?

	chrisor-dev/claude-autosync	dangerousyams/muxer	kyr0/ornith-35b-fp8-e4m3-mtp
Stars	2	2	2
Language	Shell	Shell	Shell
Setup difficulty	moderate	moderate	hard
Complexity	3/5	3/5	5/5
Audience	developer	developer	researcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires an authenticated GitHub CLI or a manually created private repo before running the installer.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Claude-autosync is a collection of shell scripts that keeps your Claude Code setup consistent across multiple machines. Claude Code, the AI coding assistant, reads its global instructions from a file called CLAUDE.md in your home directory and stores per-project notes in a memory folder. By default, these files only exist on one machine, so working across a laptop, desktop, and server means each has a different brain. This tool fixes that by linking all those files into a single private Git repository you control. The mechanism is simple. The installer replaces CLAUDE.md and the memory folders with symbolic links that point into a local clone of your private repo. Whenever you start a Claude Code session, the tool automatically pulls any changes from the remote. When the session ends, it commits and pushes the updates back. The result is that your instructions, memory, and notes travel with you across Mac, Linux, WSL, and Windows without any manual steps. Setting up the tool involves creating an empty private repository on GitHub or another host, then running the installer with that repo's URL and a project path. The installer backs up any existing files before replacing them, so nothing is lost. On each additional machine, you run the same installer against the same private repo, and the content appears. Skills and slash commands can also be synced, but they are strictly opt-in: nothing under your Claude skills folder is included until you explicitly choose to promote it. Privacy is central to the design. The public tool repository contains no personal data at all. All your actual rules, memory, and skills live in your own private repo. A special file called local.md holds machine-specific paths and other per-machine details, and it is excluded from git entirely so it never syncs anywhere. The recommendation is to keep API keys and passwords out of git completely and to use a secrets manager for those instead. This is MIT-licensed, installs via a shell script, and works across Mac, Linux, WSL, and Windows.

Copy-paste prompts

Prompt 1

Set up claude-autosync for me: create a private GitHub repo called my-claude-config, run the installer pointing at it, and verify the symlinks and hooks are in place.

Prompt 2

Using claude-autosync, add my current project directory to the central memory sync so its notes appear on all my machines.

Prompt 3

Help me promote my code-review skill to the synced set using claude-autosync's item-sync.sh script.

Prompt 4

Walk me through what sync.sh status --json output means and whether my machines are currently in sync.

Prompt 5

I cloned claude-autosync on a second machine. Install it against my existing private repo and set up the hooks.

Frequently asked questions

What is claude-autosync?

A set of shell scripts that syncs Claude Code's global rules, memory, and skills across Mac, Linux, WSL, and Windows by linking them to a private Git repo you own.

What language is claude-autosync written in?

Mainly Shell. The stack also includes Shell, Git, Python.

What license does claude-autosync use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is claude-autosync to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is claude-autosync for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub chrisor-dev on gitmyhub

Verify against the repo before relying on details.