WHY THIS
EXISTS.
Agent context becomes useful over time, then disappears the moment work moves from a desktop to a laptop. Copying hidden configuration folders manually creates stale files, lost lessons and risky merge conflicts.
OSS / LIVE DEMO · Tools
// One agent brain across your machines
claude-sync
A CLI that synchronizes Claude Code memory, skills, settings and activity between devices with deliberate conflict handling and optional encrypted storage.
LAST PUSH…syncing with GitHub
LANGUAGE…primary repository language
RELEASENO FORMAL RELEASElatest public GitHub release
LICENSENOT DECLAREDrepository metadata
WHY THIS
THE USEFUL
LOOP.
claude-sync detects the parts of the agent workspace that should travel, applies file-type-aware merge strategies and supports Git, cloud-drive, peer-to-peer and SSH-backed sync. Snapshots and optional encryption keep the process recoverable and inspectable.
03 // WHAT_SHIPPEDWHAT'S
WHAT'S
INSIDE.
SYNC WHAT MATTERS
Memory, skills, settings and activity logs can travel together or through a deliberately selected subset.
CONFLICTS WITH CONTEXT
Appendable memories, chronological logs and user-owned project instructions receive different merge strategies.
BACKENDS, NOT LOCK-IN
Git, common cloud folders, Syncthing, rsync and custom commands provide several paths between machines.