timerzz

Cc Venv — AI skill for Claude Code

AI community

cc-venv 是一个面向 Claude Code 的命名环境管理器,用来隔离不同工作流的 CLAUDE.md、MCP、Skills、Rules、环境变量和 LLM 配置, 并支持 Web 管理界面以及整环境导入导出.

How to install Cc Venv

This entry records only its repository, not the path inside it, so there is no exact command to give. Open timerzz/cc-venv and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cc Venv does

cc-venv 是一个面向 Claude Code 的命名环境管理器,用来隔离不同工作流的 CLAUDE.md、MCP、Skills、Rules、环境变量和 LLM 配置, 并支持 Web 管理界面以及整环境导入导出。cc-venv is a named environment manager for Claude Code that isolates workflow-specific CLAUDE.md, MCP, Skills, Rules, environment variables, and LLM settings, with an embedded Web UI and full environment import/export

Alternatives in AI

  • Firecrawl MCP Server — 🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM c 6.1k ★
  • Agentrq — AgentRQ: Human-in-loop realtime conversational task manager for AI Agents 1.1k ★
  • Session Kit — Close the terminal windows, not the AI coding sessions 649 ★

README

cc-venv

![GitHub License](https://img.shields.io/github/license/timerzz/cc-venv) ![Static Badge](https://img.shields.io/badge/github-repo-blue%3Flogo%3Dgithub?color=blue)

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