A CLI tool for managing Claude Code profiles and configurations.
Claude Code stores its configuration across multiple files and scopes. claudeup solves the problems that come with managing these configurations by hand:
- Portable setups -- Save your entire Claude configuration (plugins, MCP servers, settings) as a profile. Apply it on any machine in one command.
- Team sharing -- Apply a profile at project scope, commit the resulting config files to git, and every team member gets the same setup.
- Project switching -- Keep separate profiles for frontend, backend, or client work. Switch between them instantly.
- Diagnostics --
claudeup doctorcatches common issues. Event tracking shows exactly what changed and when.
claudeup is designed to bootstrap your setup and get out of the way. After applying a profile, you manage settings directly through Claude Code's native files.
# One-liner install (macOS/Linux)
curl -fsSL https://claudeup.github.io/install.sh | bash
# Or from source
go install github.com/claudeup/claudeup/v5/cmd/claudeup@latest# Setup preserves existing Claude Code configuration
claudeup setup
# For fresh installations, apply a specific profile
claudeup setup --profile frontendFor existing Claude Code users: Setup detects your current installation and preserves it. You'll be offered the option to save your existing configuration as a profile. Enabled plugins are automatically installed -- no separate profile apply needed.
For new users: Setup applies the default profile (or your specified --profile) to get you started with plugins and MCP servers.
Save and switch between different Claude configurations. Great for different projects or sharing setups across machines.
claudeup profile list # See available profiles
claudeup profile save my-setup # Save current config as a profile
claudeup profile apply backend # Switch to a different profileProfiles include plugins, MCP servers, marketplaces, and secrets. Learn more → | Community profiles →
Share Claude configurations with your team via git:
# Team lead: Save profile and share via project settings
claudeup profile save team-config
claudeup profile apply team-config --project
git add .claude/settings.json && git commit -m "Add team profile"
# Team member: Apply after clone/pull
claudeup profile apply team-config --projectProfiles capture settings from all scopes (user, project, local). Use profile apply --project to write settings to .claude/settings.json for team sharing. Learn more →
Find plugins by capability:
claudeup status # Overview of your installation
claudeup plugin search tdd # Find plugins by capability
claudeup plugin search api --all # Search all cached plugins
claudeup plugin browse my-marketplace # Browse marketplace pluginsclaudeup doctor # Diagnose issues
claudeup cleanup # Fix plugin path problems
claudeup outdated # Check for updates
claudeup update # Update claudeup CLI
claudeup upgrade # Update plugins and marketplaces| Command | Description |
|---|---|
claudeup update |
Update the claudeup CLI to the latest version |
claudeup upgrade |
Update marketplaces and plugins |
claudeup outdated |
Show available updates for CLI, marketplaces, and plugins |
For the complete command reference, see Full command reference →
| Variable | Description | Default |
|---|---|---|
CLAUDEUP_HOME |
Override claudeup's configuration directory | ~/.claudeup |
CLAUDE_CONFIG_DIR |
Override Claude Code's configuration directory | ~/.claude |
Use environment variables to run claudeup in isolation (useful for testing or CI):
export CLAUDEUP_HOME="/tmp/test-env/.claudeup"
export CLAUDE_CONFIG_DIR="/tmp/test-env/.claude"
claudeup profile apply base-tools- Profiles - Configuration profiles and secret management
- Team Workflows - Sharing configurations via git
- Commands - Full command reference
- Troubleshooting - Common issues and fixes
- Development - Building, testing, and releasing
MIT