Skip to main content
If you used cac before the environment manager update, here’s what changed.

​
Command mapping

Old commandNew commandNotes
cac setup—No longer needed. Auto-initializes on first use.
cac add us1 proxycac env create us1 -p proxyProxy is now a -p flag, not a positional arg.
cac us1cac us1Unchanged — shortcut for cac env activate us1.
cac lscac lsUnchanged — shortcut for cac env ls.
cac checkcac env checkMoved under env subcommand.
cac stopcac env deactivateRenamed. Deactivates the environment entirely.
cac -ccac env activate <name>Re-activate by name instead.
cac relay on/off—Relay is now automatic (TUN auto-detected).
cac deletecac self deleteMoved under self subcommand.

​
Deprecation warnings

All old commands still work but print a warning with the new equivalent: 
$ cac add us1 proxy
warning: 'cac add' → 'cac env create <name> -p <proxy>'

$ cac stop
warning: 'cac stop' → 'cac env deactivate'

​
New capabilities

FeatureCommand
Install Claude Code versionscac claude install latest
Pin environment to a versioncac claude pin 2.1.81
Create env without proxycac env create personal
Auto-install versionscac env create work -c 2.1.81
Update caccac self update

​
Existing environments

Your existing ~/.cac/envs/ environments continue to work. They will show claude: system in cac ls since they don’t have a pinned version. You can pin them: 
cac us1                      # activate old env
cac claude pin 2.1.81        # pin to a managed version
The .claude isolation directory (~/.cac/envs/<name>/.claude/) is created automatically on next activation if it doesn’t exist yet.