No account required for local setup. Open setup guide

VS Code plugin or MCP setup

Keep AI code changes reviewable.

CVC keeps the reasoning behind AI-assisted changes next to the code. Start in VS Code with GitHub Copilot, or install CVC through MCP for Cursor, Windsurf, Claude Desktop or Code, and similar clients.

Volute CVC is an AI coding context layer for commit history, code review, and pull requests, built for two entry points: a VS Code extension that watches GitHub Copilot chats, and an MCP server for Cursor, Windsurf, Claude Desktop or Code, and other MCP-compatible clients.

Start setup - no login needed

VS Code pluginGlobal npm install for MCPHosted review later

VS Code + GitHub Copilot

Install one extension, use Copilot normally, and let the watcher capture thoughts in the background.

IDE Extension

Commit context timeline

Pending context2 pending

Check the user session before protected routes...💬

Use JWT-based auth to avoid sticky sessions...💬🤖

feat: add JWT auth middlewarea1b2c3d

refactor: extract auth configb2c3d4e

MCP workflow

Install the npm package globally once, then connect CVC in Cursor, Windsurf, Claude Desktop or Code, or another MCP client.

CVC MCP setup

~/cvc$npm install -g @volute_cvc/cvc-mcp

added 1 package in 2s

Global CVC MCP command is now available.

Next: add cvc-mcp as an MCP server in Cursor, Windsurf, or Claude Desktop or Code.

~/cvc$cvc-mcp

CVC MCP server started on stdio.

Tools ready: setup_cvc, commit_thought, read_history, get_context.

~/api$setup_cvc --repo ~/api

✔ CVC is enabled for this repository.

Ready for MCP-based local workflows.

~/api$

Hosted review when you want to share context.

Keep local setup simple, then use the hosted reviewer later when teammates need the code diff and the captured reasoning in one place.

cvc-reviewer — Hosted review

src/auth/middleware.ts

12export async function updateSession(req) {

13const supabase = createServerClient(...)

14const { data: { user } } = await supabase.auth.getUser()

16if (isProtectedRoute && !user) {

17return NextResponse.redirect('/login')

18}

20return supabaseResponse

21}

Review context

Developer note

Check the user session on the server before applying protected-route redirects.

Code changes

await supabase.auth.getUser()

return NextResponse.redirect('/login')

Why it changed

Redirect added for unauthenticated requests after server-side session validation.

Reviewers can inspect the code diff alongside the captured decision note instead of guessing why the change happened.

Why CVC?

Simple setup, clearer review.

Pick the setup path that matches your client, keep the reason for each change close to the code, and add hosted review only when collaboration needs it.

Two setup paths

Use the VS Code plugin, or use MCP everywhere else. The setup guide makes the difference explicit.

See the reason beside the diff

CVC keeps the explanation for AI-assisted changes close to the code so review is faster and less guesswork-heavy.

Add hosted review later

Stay local at first, then sign in only when you want private repo review, shared links, or team workflows.

Pricing

Start local. Upgrade for hosted collaboration.

Local setup is the easiest way to try CVC in your current workflow. Add hosted review later when private repositories, shared review links, or team access matter.

Local tools

For individual developers getting started in VS Code or an MCP-compatible client.

$0/month

VS Code extension and MCP setup
Local metadata stored in your environment
Review commit context alongside code
No platform login required for local setup

Open setup guide

Closed Beta

Hosted platform

For teams that need hosted review on private repositories, shareable review links, and account-level access controls.

Hosted access is currently beta/gated

Everything in local tools
Hosted review for private repositories
Shareable review URLs for teammates and reviewers
Team access, org workflows, and billing controls