Personal Profiles

Personal profiles let you keep your own Claude Code preferences per project, on top of your organization and team configuration. They are stored outside the repository and automatically applied when you start a session.

What This Solves

• You want extra plugins or MCP servers for your workflow
• You tweak settings locally and want them to persist across sessions
• You work on multiple machines and want to sync your personal setup
• You switch teams often but still want your personal taste per project

Personal profiles are optional and never override org security rules.

Tip

Think of this as your per‑project “personal taste” layer. You still benefit from org + team defaults, while keeping your own tweaks portable.

Configuration Layers

SCC merges settings in this order:

Organization → Team → Personal Profile (project) → Workspace overrides

Note

Workspace overrides are the files inside the repo: .claude/settings.local.json and .mcp.json. SCC tracks drift to avoid overwriting your local edits.

Save a Personal Profile

Capture your current workspace settings into a personal profile:

scc profile save

If you installed plugins inside the container and they only exist in sandbox settings, SCC will detect them and offer to import them into .claude/settings.local.json before saving.

This saves into:

~/.config/scc/personal/projects/<hash>.json

Apply or Preview

# Apply profile to current workspace
scc profile apply

# Preview diff without writing
scc profile apply --preview

If SCC detects local drift, it will offer a preview diff before applying (or require --force in non-interactive mode).

Inspect Differences

scc profile diff

Status and Drift

scc profile status

This shows whether a profile exists, when it was last applied, and if local drift is detected.

List Profiles

scc profile list

Sync Across Machines (Repo-Based)

SCC can export/import profiles to any local git repo (GitHub, GitLab, or private repos all work).

# Export all profiles to a repo path
scc profile export --repo ~/dotfiles/scc-profiles

# Import profiles from a repo path
scc profile import --repo ~/dotfiles/scc-profiles

Preview import without writing:

scc profile import --repo ~/dotfiles/scc-profiles --preview

Optional commit/push:

scc profile export --repo ~/dotfiles/scc-profiles --commit
scc profile export --repo ~/dotfiles/scc-profiles --commit --push

Sync shortcut:

scc profile sync --repo ~/dotfiles/scc-profiles --pull --commit --push

Tip

SCC will never create remote repos or choose hosting providers for you. You control where the repo lives.

Recommended Workflow

Use this flow if you move between computers or just want a reliable “personal taste” layer per project.

1. Make your changes

   Install plugins or edit settings inside the container.

2. Save your profile

   scc profile save

3. Export to your sync repo

   scc profile export --repo ~/dotfiles/scc-profiles --commit --push

4. On a new machine

   scc profile import --repo ~/dotfiles/scc-profiles

   Then just run scc start in the project—your personal profile auto‑applies.

Troubleshooting

“Invalid JSON”

Your .claude/settings.local.json or .mcp.json file has invalid JSON. Fix the file before saving or applying profiles.

“No personal profile found”

Run scc profile save in the project to create one.