Claude Env (ccx)

Environment Orchestrator and Context Switcher for Claude Code CLI

Switch AI backends with a single command. Like nvm for Node.js, but for your Claude Code AI provider.

Why?

Every time you want to switch Claude Code from the official Anthropic API to OpenRouter, DeepSeek, or a local Ollama instance, you have to manually set environment variables. This tool eliminates that friction by letting you:

• Save provider configurations as profiles
• Switch between them with a single command
• Keep your API keys encrypted and secure
• Support multiple shells (bash, zsh, fish, PowerShell, cmd)

Zero server required - Unlike proxy-based solutions, ccx just manages environment variables.

Installation

npm install -g ccenv-cli

Quick Start

1. Create a profile

# Using a template
ccx create work --template openrouter --api-key sk-or-xxxxx

# Or use the interactive wizard
ccx setup

2. Activate the profile

# Bash/Zsh
eval "$(ccx use work)"

# PowerShell
Invoke-Expression (ccx use work --shell powershell)

# Fish
ccx use work --shell fish | source

3. Run Claude Code

claude

That's it! Claude Code will now route through OpenRouter.

4. Switch back to official Anthropic

eval "$(ccx use official)"
# or
eval "$(ccx reset)"

Commands

Available Templates

Examples

Create profiles for different use cases

# High-stakes work with official Claude
ccx create pro --template official

# Budget-friendly coding with DeepSeek
ccx create budget --template openrouter-deepseek --api-key sk-or-xxxxx

# Local offline mode
ccx create local --template ollama

# Custom provider
ccx create myproxy --base-url http://localhost:8080/v1 --api-key my-key --model gpt-4

Shell integration (add to .bashrc/.zshrc)

# Function to switch profiles easily
ccx-switch() {
  eval "$(ccx use $1)"
  echo "Switched to profile: $1"
}

# Aliases
alias cc-pro='ccx-switch pro'
alias cc-budget='ccx-switch budget'
alias cc-local='ccx-switch local'
alias cc-reset='eval "$(ccx reset)"'

PowerShell integration (add to $PROFILE)

function Switch-Claude {
  param([string]$Profile)
  Invoke-Expression (ccx use $Profile --shell powershell)
  Write-Host "Switched to profile: $Profile"
}

Set-Alias cc-switch Switch-Claude

How It Works

1. Profiles are stored in ~/.config/claude-env/config.json (cross-platform via conf)
2. API keys are encrypted using AES-256 with a machine-specific key
3. ccx use outputs shell-specific export commands for eval
4. Environment variables set:
   • ANTHROPIC_BASE_URL - The API endpoint
   • ANTHROPIC_AUTH_TOKEN - Your API key
   • ANTHROPIC_MODEL - The model to use
   • ANTHROPIC_API_KEY - Unset when using proxies (important!)
   • CCX_ACTIVE_PROFILE - Tracks the active profile

Security

• API keys are encrypted at rest using AES-256-CBC
• Encryption key is derived from machine-specific info (hostname + username)
• Keys are never logged or exposed in plain text
• Export command excludes API keys by default

Comparison with claude-code-router

Use ccx if: You want simple, fast profile switching without running a server.

Use claude-code-router if: You need advanced request routing or custom transformers.

Troubleshooting

"Profile not taking effect"

Make sure you're using eval:

# Wrong
ccx use work

# Right
eval "$(ccx use work)"

"Shell not detected correctly"

Specify the shell explicitly:

ccx use work --shell zsh

"Config file location"

ccx config-path

License

MIT