AI-assisted changes, with the why attached

Capture the why behind AI-assisted code changes.

Start in the tools you already use. CVC helps you keep commit context with the code, then add hosted review and team workflows later when you need them.

Set up locally Read docs and specs

1. Start locally2. Review the why with the code3. Add hosted team workflows later

Capture commit context in your existing workflow.

Use local setup with the CLI, editor, or agent tools you already have.

cvc cli — Terminal

CVC session active. Watching for commit context in this repo...

Captured context: "Using JWT for stateless auth to avoid sticky sessions."

1 local note ready to attach on commit.

~/api$git commit -m "feat: add JWT auth middleware"

[main a1b2c3d] feat: add JWT auth middleware

2 files changed, 45 insertions(+)

cvc-post-commit ran.

✔ Attached 1 captured note to commit a1b2c3d

~/api$

Keep the why attached to each change.

Review captured notes and commit context without rebuilding your development flow.

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

Review why a change happened, not just the diff.

When you need to share reviews beyond localhost, the hosted surface gives teammates and reviewers the code diff alongside the captured context.

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?

A clearer path from local setup to shared review.

The product story is simple: capture context locally, make review easier, and use hosted collaboration only when that becomes useful.

Start in your current tools

Set up locally in VS Code, Cursor, Windsurf, Claude Desktop, or a CLI-based workflow.

Make AI-assisted changes easier to review

Keep commit context near the code so you can understand what changed and the reasoning captured for that workflow.

Add hosted collaboration later

Use the hosted platform when you need private repo review, shareable review links, or team and billing workflows.

How it works

Local-first by default.

Use local setup to get started in your own workflow, then sign in later when you want hosted review, private repo access, or team features.

Capture context where supported: CVC can attach commit context from supported local workflows so AI-assisted changes are easier to inspect and discuss later.
Hosted review when you need it: You can start without a platform login. Hosted review is intended for collaboration flows such as private repo review and shared access, with repository access handled through GitHub-based auth.
Git-based storage model: Captured context is designed to travel with repository history using Git-compatible data, so local and shared review workflows can reference the same changes.

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 inside their editor, terminal, or agent workflow.

$0/month

Local CLI and editor setup
Local metadata stored in your environment
Review commit context alongside code
No platform login required for local setup

Set up locally

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

Hosted access