Cc Venv

cc-venv

 

English | [简体中文](./README_ZH.md)

`cc-venv` is a named environment manager for Claude Code.

The goal is simple: keep different workflows in separate Claude environments, switch when needed, and leave your default Claude Code setup untouched.

Why cc-venv

Many people do not use Claude Code for just one kind of work.

Sometimes you want a coding workflow:

• coding-focused MCP servers
• engineering or frontend-focused Skills
• project-oriented Rules

At other times you want a writing workflow:

• a different set of writing, translation, or summarization instructions
• different MCP tools, or fewer tools
• complete separation from the coding setup

If all of that lives in your default Claude Code configuration, it usually turns into this:

• mixed Skills
• MCP settings affecting each other
• Rules and CLAUDE.md instructions bleeding across workflows
• hesitation to experiment because it may break your default setup

`cc-venv` solves that by giving you isolated named environments:

• each environment has its own CLAUDE.md
• its own environment variables
• its own MCP
• its own Skills
• its own Agents / Commands / Rules

That makes it easy to maintain separate environments such as:

• coding
• writing
• research
• prod-safe

Switching environments does not affect your default Claude Code configuration.

Quick start

Option 1: Install globally with npm

npm install -g @timerzz/ccv

After installation:

# Create a virtual environment named coding
ccv create coding
# List all current virtual environments
ccv list
# Run Claude Code inside the coding environment
ccv run coding
# Pass extra arguments through to Claude Code
ccv run coding --model claude-opus -p "summarize this repo"
# Inside Claude Code running in a ccv environment, you can in