β‘ Fast and intuitive way to switch between Claude Code contexts (
~/.claude/settings.json
)
cctx (Claude Context) is a kubectx-inspired command-line tool for managing multiple Claude Code configurations. Switch between different permission sets, environments, and settings with a single command.
- π Instant context switching - Switch between configurations in milliseconds
- π― Predictable UX - Default behavior always uses user-level contexts (no surprises!)
- π‘οΈ Security-first - Separate permissions for work, personal, and project contexts
- π¨ Beautiful CLI - Colorized output with helpful hints and visual indicators
- π Shell completions - Tab completion for all major shells
- π¦ Zero dependencies - Single binary, works everywhere
- π Previous context - Quick switch back with
cctx -
- π File-based - Simple JSON files you can edit manually
- π Kubectx-inspired - Familiar UX for Kubernetes users
- π‘ Progressive disclosure - Shows project/local contexts when available
From crates.io (recommended):
cargo install cctx
From source:
git clone https://github.com/nwiizo/cctx.git
cd cctx
cargo install --path .
Pre-built binaries: Download from GitHub Releases
# 1. Create your first context from current settings
cctx -n personal
# 2. Create a restricted work context
cctx -n work
# 3. Switch between contexts
cctx work # Switch to work
cctx personal # Switch to personal
cctx - # Switch back to previous
# List all contexts (current highlighted in green)
cctx
# Switch to a context
cctx work
# Switch to previous context
cctx -
# Show current context
cctx -c
cctx respects Claude Code's settings hierarchy with a simple, predictable approach:
- Enterprise policies (highest priority)
- Command-line arguments
- Local project settings (
./.claude/settings.local.json
) - Shared project settings (
./.claude/settings.json
) - User settings (
~/.claude/settings.json
) (lowest priority)
# Default: always uses user-level contexts (predictable)
cctx # Manages ~/.claude/settings.json
# Explicit flags for project/local contexts
cctx --in-project # Manages ./.claude/settings.json
cctx --local # Manages ./.claude/settings.local.json
# All commands work with any level
cctx --in-project work # Switch to 'work' in project contexts
cctx --local staging # Switch to 'staging' in local contexts
# Create new context from current settings
cctx -n project-alpha
# Delete a context
cctx -d old-project
# Rename a context
cctx -r old-name new-name
# Edit context with $EDITOR
cctx -e work
# Show context content (JSON)
cctx -s production
# Unset current context
cctx -u
# Export context to file
cctx --export production > prod-settings.json
# Import context from file
cctx --import staging < staging-settings.json
# Share contexts between machines
cctx --export work | ssh remote-host 'cctx --import work'
Enable tab completion for faster workflow:
# Bash
cctx --completions bash > ~/.local/share/bash-completion/completions/cctx
# Zsh
cctx --completions zsh > /usr/local/share/zsh/site-functions/_cctx
# Fish
cctx --completions fish > ~/.config/fish/completions/cctx.fish
# PowerShell
cctx --completions powershell > cctx.ps1
Contexts are stored as individual JSON files at different levels:
π User Level (~/.claude/
):
π ~/.claude/
βββ βοΈ settings.json # Active user context
βββ π settings/
βββ πΌ work.json # Work context
βββ π personal.json # Personal context
βββ π .cctx-state.json # State tracking
π Project Level (./.claude/
):
π ./.claude/
βββ βοΈ settings.json # Shared project context
βββ π settings.local.json # Local project context (gitignored)
βββ π settings/
βββ π staging.json # Staging context
βββ π production.json # Production context
βββ π .cctx-state.json # Project state
βββ π .cctx-state.local.json # Local state
When no arguments are provided, cctx enters interactive mode:
- π fzf integration - Uses fzf if available for fuzzy search
- π― Built-in finder - Fallback fuzzy finder when fzf not installed
- π Color coding - Current context highlighted in green
- β¨οΈ Keyboard navigation - Arrow keys and type-ahead search
# Interactive context selection
cctx
# Create restricted work context for safer collaboration
cctx -n work
cctx -e work # Edit to add restrictions:
# - Read/Edit only in ~/work/** and current directory
# - Deny: docker, kubectl, terraform, ssh, WebFetch, WebSearch
# - Basic dev tools: git, npm, cargo, python only
# Create project-specific contexts
cctx -n client-alpha # For client work
cctx -n side-project # For personal projects
cctx -n experiments # For trying new things
# Switch based on current work
cctx client-alpha # Restricted permissions
cctx experiments # Full permissions for exploration
# Morning: start with work context
cctx work
# Need full access for personal project
cctx personal
# Quick switch back to work
cctx -
# Check current context anytime
cctx -c
# Default restricted context for screen sharing
cctx work
# Full permissions only when needed
cctx personal
# Project-specific minimal permissions
cctx -n client-project
# Configure: only access to ~/projects/client/**
π€ User-Level Development:
# Personal development with full permissions (default behavior)
cctx personal
# Work context with restrictions (default behavior)
cctx work
π Project-Level Collaboration:
# Shared team settings (committed to git)
cctx --in-project staging
cctx --in-project production
# Personal project overrides (gitignored)
cctx --local development
cctx --local debug
π Multi-Level Management:
# Check current level (always shows helpful context)
cctx # Shows: π€ User contexts + hints for project/local if available
# Switch levels in same directory
cctx personal # User level (default)
cctx --in-project staging # Project level
cctx --local debug # Local level
Use Claude Code to help create specialized contexts:
# Create production-safe context
claude --model opus <<'EOF'
Create a production.json context file with these restrictions:
- Read-only access to most files
- No docker/kubectl/terraform access
- No system file editing
- Limited bash commands for safety
- Based on my current ~/.claude/settings.json but secured
EOF
# Create template contexts for different scenarios
cctx -n template-minimal # Minimal permissions
cctx -n template-dev # Development tools only
cctx -n template-ops # Operations/deployment tools
cctx -n te
8000
mplate-restricted # Screen-sharing safe
# Sync contexts across machines
rsync -av ~/.claude/settings/ remote:~/.claude/settings/
# Or use git for version control
cd ~/.claude/settings
git init && git add . && git commit -m "Initial contexts"
git remote add origin git@github.com:user/claude-contexts.git
git push -u origin main
- π’ Work context - Restricted permissions for professional use
- π Personal context - Full permissions for personal projects
- πΊ Demo context - Ultra-restricted for screen sharing/demos
- π§ͺ Testing context - Isolated environment for experiments
# Create permission hierarchy
cctx -n restricted # No file write, no network, no system access
cctx -n development # File access to ~/dev/**, basic tools only
cctx -n full # All permissions for personal use
cctx -n demo # Read-only, safe for presentations
# Review context permissions regularly
cctx -s work # Check work context permissions
cctx -s personal # Review personal context
cctx -s production # Audit production context
# Quick security check
cctx -s restricted | grep -i "allow\|deny"
- π Use
cctx -
frequently - Quick toggle between two contexts - π― Trust the defaults -
cctx
(no flags) handles 90% of use cases perfectly - π‘ Follow the hints - When cctx shows hints, they're contextually relevant
- β¨οΈ Set up aliases -
alias work='cctx work'
,alias home='cctx personal'
- π Document your contexts - Add comments in JSON for future reference
# Add to your shell profile (~/.bashrc, ~/.zshrc)
export EDITOR=code # For cctx -e
alias cx='cctx' # Shorter command
alias cxs='cctx -s' # Show context content
alias cxc='cctx -c' # Show current context
# Git hooks for automatic context switching
# Pre-commit hook to ensure proper context
#!/bin/bash
if [[ $(cctx -c) != "work" ]]; then
echo "β οΈ Switching to work context for this repo"
cctx work
fi
# Tmux integration - show context in status bar
set -g status-right "Context: #(cctx -c) | %H:%M"
# VS Code integration - add to settings.json
"terminal.integrated.env.osx": {
"CLAUDE_CONTEXT": "$(cctx -c 2>/dev/null || echo 'none')"
}
# Fish shell prompt integration
function fish_prompt
set_color cyan
echo -n (cctx -c 2>/dev/null || echo 'no-context')
set_color normal
echo -n '> '
end
This project includes comprehensive automation tools:
Simple One-Command Release:
# Automatic release with all quality checks
./quick-release.sh patch # 0.1.0 -> 0.1.1
./quick-release.sh minor # 0.1.0 -> 0.2.0
./quick-release.sh major # 0.1.0 -> 1.0.0
The script automatically:
- β Runs quality checks (fmt, clippy, test, build)
- β Updates version in Cargo.toml
- β Creates git commit and tag
- β Pushes to GitHub
- β Triggers GitHub Actions for binary builds and crates.io publishing
# Using justfile (install: cargo install just)
just check # Run all quality checks
just release-patch # Same as ./quick-release.sh patch
just setup # Setup development environment
just audit # Security audit
just completions fish # Generate shell completions
We welcome contributions! This project includes:
- π Automated CI/CD - GitHub Actions for testing and releases
- π§ͺ Quality gates - Formatting, linting, and tests required
- π¦ Multi-platform - Builds for Linux, macOS, and Windows
- π Auto-releases - Semantic versioning with automated publishing
See CLAUDE.md for detailed development guidelines.
MIT License - see LICENSE file for details.
cctx follows the principle of "Predictable defaults with explicit overrides":
- π― Default behavior is always the same - uses user-level contexts (
~/.claude/settings.json
) - π‘ Helpful discovery - shows hints when project/local contexts are available
- π Simple when simple - 90% of usage needs zero flags
- π§ Explicit when needed -
--in-project
and--local
for specific cases
This approach eliminates surprises and cognitive overhead while maintaining full functionality.
cctx is designed to work with Claude Code configuration files. As Claude Code is actively developed by Anthropic, configuration formats and file structures may change over time.
We are committed to maintaining compatibility:
- π Active monitoring of Claude Code updates and changes
- π Prompt updates when configuration formats change
- π οΈ Backward compatibility whenever possible
- π’ Clear migration guides for breaking changes
If you encounter compatibility issues after a Claude Code update, please open an issue and we'll address it promptly.
- π― Inspired by kubectx - the amazing Kubernetes context switcher
- π€ Built for Claude Code - Anthropic's CLI for Claude
- π¦ Powered by Rust - fast, safe, and beautiful
β Star this repo if cctx makes your Claude Code workflow better!
π Report Bug β’ π‘ Request Feature β’ π¬ Discussions