Set up CVC in the tool you already use.
Core CVC setup runs locally on your machine. Start with your editor or agent client now, then sign in later only if you want hosted review, private repo access, team management, or billing.
An editor extension, an MCP config entry, or a local package depending on the path you choose.
Repository setup is separate. That is when CVC metadata and any repo-level Git hooks may be added.
Optional for local use. Needed later for hosted review, private repos, team features, and billing.
Choose your setup path
Pick the tool you already work in. You can switch paths later without creating a separate onboarding flow.
VS Code
Install one extension, then start using CVC from the VS Code chat experience.
1. Prerequisites
- VS Code installed.
- A local Git repository for project-level setup.
- Internet access for the initial extension and binary download.
When login matters
No platform login is required for local editor setup. Log in later if you want hosted review, private repo access, teams, or billing features.
2. Install and configure
Install the extension
Install the Volute CVC extension from VS Code or from the command line.
code --install-extension volute.cvc
Open your project and start CVC in chat
Open the project in VS Code, then look for the CVC chat participant or CVC-powered chat entry after the extension activates.
Initialize the repository only when prompted
If the extension offers repository setup, review the prompt and continue. This is the point where local CVC metadata or Git hooks may be added to the repo.
3. Verify success
- The extension appears in VS Code as installed and enabled.
- A CVC participant or CVC chat entry is available in the chat UI.
- Your first prompt gets a response without a setup error.
What happens locally
- Installs the VS Code extension on your machine.
- May download CVC binaries locally for the extension to use.
- Repository setup can create local CVC data and install repo-level Git hooks if required for that workflow.
Hosted platform vs local setup
CVC's core capture workflow is local-first. The hosted platform is the collaboration layer: hosted review, private repo access controls, team management, and billing.
If you want the safest default
Start with VS Code unless you already rely on MCP in another client. It gives the clearest onboarding path and keeps advanced configuration out of the critical path.
Need more control?
Advanced configuration, raw MCP blocks, available tools, and hook notes are still available below once you have chosen a path.
Jump to advanced detailsAdvanced configuration and troubleshooting
Use these details only if your client needs manual MCP setup or you want to inspect what CVC changes locally.
Available MCP tools
| Tool | Purpose |
|---|---|
| commit_thought | Record a reasoning step and response. |
| read_history | Read recent interaction history. |
| get_context | Inspect file context for the current task. |
| setup_cvc | Initialize CVC in a repository and enable repo-level setup. |
Git hooks
CVC can use repo-level Git hooks for parts of its local workflow. Treat hook installation as an explicit repository setup step, not a hidden side effect. If your client prompts for repo setup, review it before continuing.
If the server does not start
- • Confirm Node.js and npm are installed.
- • Restart the client after editing MCP settings.
- • If you need a stable shell command or hook execution, prefer the global install path.
- • Try running the configured command manually to confirm it starts cleanly.