PITIR-TECH/claudecode-local-sync
Cross device and platform sync for Claude Code CLI. Sync sessions, memory, plugins, agents, skills, hooks, MCP configs, and project settings between Mac and Windows via GitHub. Per-project or all-at-once sync, automatic path fixing, platform detection, large file handling, and status checks. Push from one PC, pull on another and continue.
Platform-specific configuration:
{
"mcpServers": {
"claudecode-local-sync": {
"command": "npx",
"args": [
"-y",
"claudecode-local-sync"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
Created by Coskun Eren at [PITIR TECH](https://github.com/PITIR-TECH)
Sync your Claude Code sessions, memory, plugins, agents, skills, rules, hooks, commands, MCP configs, and project settings across Mac and Windows. Switch PCs and pick up exactly where you left off.
---
Claude Code's real power is local — MCP servers, local file access, terminal commands, build tools, test runners, browser automation, database connections. None of this works in Claude Remote, Claude Team, or cloud-based setups.
But working locally creates a problem: your sessions, memory, plugins, and configs are trapped on one machine.
| Approach | Local tools (MCP, terminal, builds) | Session sync | Project sync | |---|---|---|---| | Claude Remote / Team | No — cloud only, no local MCP or CLI | Built-in | Built-in | | Standard Git + VS Code | Yes | No — sessions stay on one PC | Yes | | Claude Sync (this repo) | Yes — full local power | Yes — sessions, memory, plugins, everything | Yes |
You're a developer. You have a desktop at work, a laptop at home, maybe a Windows machine for testing. You use Claude Code locally because you need:
But when you switch machines, your sessions are gone. Your memory files don't follow you. Your MCP configs vanish. Your plugin settings disappear. You start over on every machine.
Claude Sync gives you the best of both worlds:
Loading reviews...