Claudebase

Your Claude Code setup is infrastructure. Agents, skills, rules, hooks, memory — these accumulate over weeks of work and represent real investment. Losing them to a disk wipe, or manually recreating them on a new machine, shouldn't happen.

Claudebase syncs your entire Claude Code environment to a private GitHub repo. Profiles let you switch between work, personal, and team configurations instantly. Secret scanning, automatic backups, and multi-machine conflict detection keep things safe.

Install

claude plugin marketplace add rohithzr/claudebase
claude plugin install claudebase@rohithzr

Then restart Claude Code or run /reload-plugins.

Update / Uninstall

# Update
claude plugins marketplace update
claude plugin update claudebase@rohithzr

# Uninstall
claude plugin uninstall claudebase@rohithzr
claude plugin marketplace remove rohithzr

Quick Start

/sync-setup          # One-time: create private GitHub repo + first push
/sync-push           # Back up current config
/sync-pull           # Restore config from GitHub
/sync-status         # Compare local vs remote
/sync-profiles list  # Manage named profiles
/sync-config         # View/change settings

> Type /sync to see all commands. Full namespaced form (/claudebase:sync-push) also works.

Why Not Just Copy the Folder?

Examples

Sync between machines

Laptop:  /sync-push               # Push your config
Desktop: /sync-pull               # Pull it down
Desktop: # ... tweak agents, add rules ...
Desktop: /sync-push --force       # Push from second machine
Laptop:  /sync-pull               # Get desktop's changes

Switch contexts during the day

/sync-profiles switch work        # Load work config
# ... deep coding session ...
/sync-push                        # Save work state
/sync-profiles switch personal    # Load personal config

Preview before committing

/sync-push --dry-run              # See what would be pushed
/sync-pull --dry-run              # See what would change locally
/sync-profiles diff work personal # Compare two profiles

More examples

Onboard a teammate

# You: push your team config to a shared profile
/sync-profiles create team-defaults --from work
/sync-push

# Teammate: on their machine
/sync-setup
/sync-pull --profile team-defaults

Recover from a bad change

/sync-pull                        # Restores from last push
                                        # Old config saved to backups/

Three-machine round-robin

Laptop:   /sync-push
Desktop:  /sync-pull && /sync-push --force
CI Box:   /sync-pull && /sync-push --force
Laptop:   /sync-pull              # Gets everything

What Gets Synced

Opt-in: Global ~/.claude/settings.json (--include-global), skills-lock.json (/claudebase:config set sync_agent_skills true — syncs the lock file; prints install commands on pull, does not auto-execute).

Never synced: settings.local.json, conversations, sessions, shell snapshots, logs.

How It Works

           ┌──────────────┐
Machine A  │ .claude/     │──push──┐
           │ .mcp.json    │        │     ┌──────────────────────┐
           │ .auto-memory/│        ├────>│  GitHub (private)    │
           └──────────────┘        │     │  profiles/default/   │
                                   │     │  profiles/work/      │
           ┌──────────────┐        │     │  shared/             │
Machine B  │ .claude/     │<─pull──┘     └──────────────────────┘
           │ .mcp.json    │
           │ .auto-memory/│
           └──────────────┘

When you pull, shared/ is applied first as a base layer, then profiles/\<name\>/ overlays on top. This lets you maintain organization-wide defaults while customizing per context.

Push is blocked if a different machine pushed since your last sync — pull first or use --force to override.

Safety

Configuration

/sync-config show                      # View all settings
/sync-config set auto_push true        # Auto-push on session end
/sync-config set include_global true   # Always sync global settings
/sync-config set machine_id my-laptop  # Custom machine identifier
/sync-config reset auto_push           # Reset to default

Claudebase also registers two lifecycle hooks:

• SessionStart — quiet diff check (tells you if config is out of sync)
• SessionEnd — auto-pushes if auto_push is enabled