Config Sync Settings

View and modify claudebase configuration.

Instructions

Run the config manager script with the appropriate action:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/config-manager.sh" ACTION [KEY] [VALUE]

Actions

• show (default) — Display all current settings
• set — Change a setting
• get — Read a single setting
• reset — Remove a setting (revert to default)

Configurable keys

Examples

• /sync-config — show all settings
• /sync-config set include_global true — enable global settings sync
• /sync-config set auto_push false — disable auto-push

User Arguments

$ARGUMENTS

Config Sync Profiles

Manage multiple configuration profiles stored in your GitHub backup repo.

Available actions

List profiles

bash "${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh" list

Shows all profiles with file counts, last push time, and which is active.

Create a profile

# Empty profile
bash "${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh" create NAME

# Clone from existing profile
bash "${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh" create NAME --from EXISTING

Creates a new profile. Use --from to clone an existing profile as a starting point.

Switch to a profile

Switching means pulling a different profile's config:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-pull.sh" --profile NAME

This backs up current config, then applies the target profile. The active profile is updated automatically.

Delete a profile

bash "${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh" delete NAME

Cannot delete the active profile. Switch to a different one first.

Compare two profiles

bash "${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh" diff NAME1 NAME2

Shows files that exist in only one profile or differ between them.

Profile info

bash "${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh" info NAME

Shows metadata and contents of a specific profile.

Instructions

Parse the user's action from $ARGUMENTS and run the appropriate command above.

If the user says "switch" to a profile, use the pull script with --profile rather than the profile-manager (since switching = pulling a different profile).

If no action is specified, default to list.

User Arguments

$ARGUMENTS

Config Sync Pull

Pull configuration from your GitHub backup repo and apply it to the local machine.

What happens

1. Backup — Current local config is backed up to plugin data directory (timestamped, keeps last 10)
2. Apply shared — Files from shared/ directory are applied first (base layer)
3. Apply profile — Profile-specific files overlay on top (overrides shared where both exist)
4. Apply global — User-level settings from global/ are applied to ~/.claude/
5. Verify — JSON config files are validated for correct syntax

Instructions

Parse user arguments and run the pull script:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-pull.sh" [OPTIONS]

Options:

• --profile NAME — Pull a specific profile (default: active profile)
• --dry-run — Show what would be applied without writing any files
• --no-backup — Skip backup step (use with caution)
• --yes / -y — Skip confirmation prompt (auto-approve)
• --include-global — Also pull ~/.claude/settings.json (global settings are opt-in)

Profile switching

If the user specifies a different profile than their current one, this effectively switches their setup. Let them know which profile they're switching from/to.

After pull

Tell the user:

• How many files were applied
• Any validation warnings
• That a backup was created (and where)
• They may need to restart Claude Code for some settings to take effect

User Arguments

$ARGUMENTS

Config Sync Push

Push your current local Claude Code configuration to the GitHub backup repo.

What gets pushed

All syncable files from the current project and global config:

• .mcp.json, .claude/settings.json
• .claude/agents/, .claude/commands/, .claude/skills/
• .claude/hooks/ (scripts, config, sounds)
• .claude/rules/, .claude/agent-memory/
• .auto-memory/ (memory files)
• ~/.claude/settings.json (global settings, opt-in via --include-global)

Files that are never pushed: CLAUDE.md (version-controlled with project), settings.local.json, hooks-config.local.json, conversations, sessions.

Instructions

Parse user arguments and run the push script:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-push.sh" [OPTIONS]

Options:

• --profile NAME — Push to a specific profile (default: active profile)
• --force — Skip multi-machine safety check and secret warnings
• --dry-run — Show what would be pushed without actually pushing
• --include-global — Also push ~/.claude/settings.json (global settings are opt-in)

Multi-machine warning

If the script warns about another machine having pushed more recently, advise the user to pull first (/sync-pull) or use --force if they're sure.

Secret detection

If the script warns about potential secrets, tell the user which files were flagged and suggest reviewing them before using --force.

User Arguments

$ARGUMENTS

Config Sync Setup

Initialize Claude Config Sync by connecting to GitHub and creating the backup repository.

What this does

1. Verifies gh CLI is installed and authenticated
2. Creates a private GitHub repo for config storage (or connects to existing)
3. Initializes the repo structure with a default profile
4. Performs the first push of your current Claude Code config

Instructions

Run the setup script. Parse user arguments for custom repo name and profile:

• First argument (if provided): repo name (default: claude-config)
• Second argument (if provided): initial profile name (default: default)

bash "${CLAUDE_PLUGIN_ROOT}/scripts/ensure-repo.sh" REPO_NAME PROFILE_NAME

Replace REPONAME and PROFILENAME with the user's values or defaults.

If gh is not installed

Guide the user to install it:

• macOS: brew install gh
• Linux: sudo apt install gh or sudo dnf install gh
• Windows: winget install --id GitHub.cli

Then authenticate: gh auth login

After setup succeeds

Run the first push automatically:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-push.sh" --profile PROFILE_NAME

Tell the user what was synced and show all available commands: /sync-push, /sync-pull, /sync-status, /sync-profiles, /sync-config.

User Arguments

$ARGUMENTS

Config Sync Status

Compare your local Claude Code configuration against what's stored in the GitHub backup repo.

Instructions

Run the diff script:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/diff-config.sh" --profile PROFILE_NAME

If the user doesn't specify a profile, omit the --profile flag (uses active profile).

Interpreting output

The script shows each tracked file/directory with a status:

• + local only (green) — Exists locally but hasn't been pushed yet
• + remote only (cyan) — Exists in the repo but hasn't been pulled yet
• ~ modified (yellow) — Exists in both but differs

Recommendations

Based on the output, suggest the appropriate action:

• Local-only files → suggest /sync-push
• Remote-only files → suggest /sync-pull
• Modified files → suggest checking what changed, then push or pull

User Arguments

$ARGUMENTS