Isolate configs, credentials, MCP server registrations, and memories per project. Share setups with your team via cvm.yaml without ever leaking tokens or history.
Separate CLAUDE_CONFIG_DIR per project. Credentials, history, and MCP tools never collide between environments.
Share cvm.yaml manifests across teams to reproduce exact MCP servers and skills in one command.
Auth tokens, API credentials, and session history are never exported or included in manifest files.
Launch multiple cvm open <env> sessions side by side across client projects without shell interference.
Drop a .cvm file with an env name in a repo — shell hooks activate it on cd, like a lightweight direnv.
Run cvm update to pull the latest release binary from GitHub and replace the install in place.
cvm create <env> [--anonymous] [--inherit] [--open]
Create an isolated env at ~/.cvm/envs/<env>; reuse global credentials unless --anonymous; --inherit links skills and copies settings; --open launches Claude Code
One install. Zero config drift. Secrets never leave your machine.