Install CVC with VS Code or MCP.
There are two ways to start. Use VS Code with GitHub Copilot for the watcher-based path, or use MCP for Cursor, Windsurf, Claude Desktop or Code, and similar clients.
npm install -g @volute_cvc/cvc-mcpChoose the VS Code plugin or an MCP client. You do not need to learn five separate onboarding flows.
Installing the extension or npm package changes your machine. A repository changes only after you run setup inside it.
Local setup works without signing in. Use an account later only when you want hosted review or team features.
Pick your setup path
If you are unsure, start with VS Code. If you use another AI client, choose MCP and begin with the global npm install.
VS Code plugin
This is the shortest path if you use VS Code with GitHub Copilot. Install the extension, use Copilot normally, then watch the Volute panel fill in automatically. No npm step is needed here.
1. What you need
- VS Code installed.
- GitHub Copilot available in VS Code.
- A local Git repository when you want to enable CVC for a project.
- Internet access for the initial extension install.
Before you install
No platform login is required. The watcher is built for GitHub Copilot chat storage in VS Code, not other VS Code agents such as Claude Code. Nothing changes inside a repository until you explicitly run setup there.
2. Install and use it
Install the VS Code extension
Install Volute CVC from the VS Code marketplace or from the command line.
code --install-extension volute.cvc
Open a new GitHub Copilot chat and work normally
Use GitHub Copilot in VS Code the way you already do. The watcher reads Copilot chat storage automatically, so there is nothing extra to invoke.
Open the Volute panel and watch thoughts appear
After a Copilot exchange, open the Volute timeline panel in the sidebar to see the captured thoughts show up automatically.
Commit your changes
When you commit, the captured thoughts move from pending state into commit-linked history for that unit of work.
Push and open a PR when you want hosted review
After you push and open a pull request, the same captured history appears in hosted review as the shadow timeline beside the diff.
3. Check that it worked
- The extension appears in VS Code as installed and enabled.
- GitHub Copilot chat still works the way it normally does in VS Code.
- After a Copilot exchange, a new thought appears in the Volute timeline panel.
- After a commit, that thought moves into commit-linked history.
What this changes
- Installs the VS Code extension on your machine.
- Reads GitHub Copilot chat session storage locally in VS Code for this workflow.
- May download a small local helper binary for the extension.
- Changes inside a repository happen only after you explicitly run setup there.
Not sure which path to pick?
Choose VS Code if you already work in VS Code with GitHub Copilot. Choose MCP if your main workflow lives in another AI client.
Need hosted review later?
Sign in only when you want hosted review, private repository access, team management, or billing.
Sign in for hosted reviewUsing another agent in VS Code?
The watcher targets GitHub Copilot's storage format in VS Code. If you mainly work through Claude Code or another non-Copilot agent, use the MCP path instead.
Quick peek from the terminal
This is not a primary setup path. Use it only after CVC is already working in VS Code or through MCP and you want a fast console view of local history.
Useful commands
Check what is waiting locally
cvc status
Inspect recorded history
cvc log
When to use this
- You want a quick terminal check without opening the editor.
- You want to confirm thoughts were captured before or after a commit.
- You already have the CVC CLI available in your environment.
Advanced details and troubleshooting
Use these details only if you want to inspect the available tools, understand Git hook behavior, or troubleshoot a manual MCP setup.
Available CVC tools
| Tool | Purpose |
|---|---|
| commit_thought | Save a concise task record, key reasoning, and optional result. |
| read_history | Read recent saved CVC history for prior context or decisions. |
| get_context | Inspect git-backed context for one file before summarizing or recording it. |
| setup_cvc | Initialize CVC storage and hooks for the current repository. |
Git hooks
CVC can use Git hooks as part of repository setup. They are not added at install time, and they are not enabled silently in every repository.
If the MCP server does not start
- • Run
npm install -g @volute_cvc/cvc-mcpagain to confirm the package is installed globally. - • Restart the client after editing MCP settings.
- • Try running
cvc-mcpin your terminal to confirm the command exists. - • If the repo setup fails, try it in a small test repository first.
Common questions
Do I need an account to use CVC?
No. Local VS Code and MCP setup work without signing in. An account matters later for hosted review and team features.
What is the difference between the two setup paths?
VS Code uses the extension plus a watcher for GitHub Copilot chats. Everything else uses the globally installed cvc-mcp command through MCP.
When does CVC change my repository?
Only when you explicitly run repository setup there. Installing the extension or npm package does not automatically modify every repo.
Which path should I choose if I am unsure?
Choose VS Code if you use GitHub Copilot in VS Code. Choose MCP if your main client is Cursor, Windsurf, Claude Desktop or Code, or another MCP-compatible tool.
Does CVC work with Cursor, Windsurf, or Claude Code?
Yes. Use the MCP path for Cursor, Windsurf, Claude Desktop or Code, and other MCP-compatible clients. The watcher path is specifically for GitHub Copilot in VS Code.
Why does MCP setup require a global npm install?
MCP clients need a local cvc-mcp command they can launch. The global install gives your client that command before you add the JSON config.