How it works
Your machine does the work. Every screen can drive it.
A small server wraps the provider CLIs. Desktop, web and mobile clients connect to it.
- 1
hostInstall VC on the machine that has your code and provider logins, sign in, and host on this computer.
- 2
pairReach it from web or your phone through VC Connect, a tunnel or a one-time pairing link.
- 3
shipPick a provider, start a thread, review the diff, open the PR.
Your machine
The VC server, provider CLIs and their logins, your repositories, threads and checkpoints. Agents keep working when you close the app.
Your devices
Desktop, web and mobile clients show and control that work. They keep connection settings, drafts and caches locally.
Providers you choose
Prompts, files and context you send go to the thread's provider — Codex, Claude, Cursor and others — under their terms.
VC services
Your account and plan, VC Connect when you enable it, and update downloads. They handle only what those features need.
The words we use
Environment
One running VC server and the machine, files and logins it owns.
Project
A workspace on that environment, rooted at a directory.
Thread
The durable conversation and work history for a project.
Checkpoint
A hidden git ref saved after every turn, so you can diff and restore.