VC runs coding agents on your computer and lets you control them from its desktop, web, or mobile app. Set up the machine where the agents will work first.
Requirements
Command-line use, SSH hosts, and WSL backends need Node.js 22.16+ (22.x), 23.11+ (23.x), or 24.10 and later. The native desktop app includes its server runtime.
You need an installed, authenticated provider before starting a thread. You can launch VC and configure providers afterwards.
Run this fork
From the repository root:
vp i
vp run dev
For the desktop app, install Rust and the platform build tools, then run:
vp run build:desktop
and open the app it packages under release/ (for example release/mac-arm64/VC.app).
Choosing to host on desktop starts VC’s backend inside the app and connects to it. It runs while the app is open: quitting stops its agents and terminals, and web and mobile clients reconnect when you open the app again. If a server for the same data home is already running, the app uses it instead. See Running in the background.
On the first desktop launch and after signing out, sign in with your VC account in the browser, then host on this computer or open one of your account’s servers. Connect with a pairing link instead pairs with an existing server without an account. See Welcome wizard for details. Saved sessions reopen directly. The web client shows connection controls and instructions for connecting to a running server, then asks you to sign in before the workspace opens.
In Settings → Account → Profile, edit your VC display name or refresh your account details. Session lists your signed-in browser and app devices. Sign out a selected device, or choose Sign out others to keep this desktop signed in while revoking the other sessions. These actions require access to the portal. Use Open security to review email OTP and sign-in security on the portal.
Connect web and mobile through Settings → Connections, using a separate pairing link for each client. Desktop clients can also pair to an existing backend without hosting their own. See Running in the background for service controls and login/logout behavior.
The desktop app includes a native Browser in the workspace’s right panel. On macOS, Windows and Linux it supports navigation, hard reload, zoom, DevTools, light/dark appearance, responsive viewports, screenshots, element selection, audio muting, video recording, agent automation, and a separate preview window. Closing the separate window returns the same tab to the main panel.
Use the element picker to select part of a page and add a comment. Shift-click selects multiple elements; Attach adds the selection to the selected agent’s chat draft or CLI input, and Send submits it. Escape cancels. The camera attaches a screenshot to the same agent, copies it to the clipboard, and saves a PNG you can copy or reveal.
Browser profiles keep logins separate. Incognito tabs of one environment share a session that is discarded when the last of them closes. Clear cookies clears cookies and site storage; Clear cache clears cached resources without signing you out. Both actions apply only to the selected environment and profile. Pages cannot use the camera, microphone, location or notifications. Importing sessions from another browser is not available yet.
See the mobile development guide to build the mobile client.
The CLI executable is named vc once built and installed locally. This fork is not distributed through the upstream T3 Code store listings or package-manager packages. Do not use npx vc to install this checkout: a public package with that name is not established by a local build. Remote automatic server installation requires a separately published VC package.
Moving from the Tauri desktop app
Earlier desktop releases do not update to this app. Download VC from
vce.codes/download and install it, then quit the old
app before opening the new one (the new app waits until you do); you can delete the
old app afterwards. Projects, threads and settings live in your data home (~/.vc
unless you set VC_HOME) and stay where they are. On its first launch the new app
removes the background service the old one used and keeps its port, so paired web
and mobile clients reconnect. Sign in to your VC account again; saved connections
to other servers may need to be added again.
Providers
Open Settings → Providers in the web or desktop app, select the environment, and enable the provider you want. Installation, login, and configuration belong to that environment’s machine, even when you connect from a phone or another computer.
On mobile, open Settings → Provider accounts, choose the environment, and add or edit an account there. Use Sign in to complete the provider’s link, code, or callback flow. Credentials stay on the environment. Codex and Claude can use separate account directories; providers with a shared CLI login reuse that login across entries, so adding an entry does not create a separate quota.
To install a CLI from web or desktop, select its provider and use CLI installation. Choose Install CLI, review the command in the terminal, and press Enter. Wait for installation to finish before closing the terminal; closing it stops that terminal and rechecks installation where provider status is available. The command runs on the selected environment. For platforms without an install command, open Installation guide.
| Provider | Install and authenticate |
|---|---|
| Codex | Install Codex CLI, then choose Sign in to Codex in provider settings. |
| Claude | Install Claude Code, then choose Sign in to Claude in provider settings. |
| Cursor | Install Cursor CLI, then choose Sign in to Cursor in provider settings. |
| Grok Build | Install Grok Build CLI, then choose Sign in in provider settings. |
| Command Code | Install Command Code, then choose Sign in in provider settings. |
| OpenCode | Install OpenCode, then choose Sign in and select a provider account. |
| Antigravity | Install and sign in with Google from VC’s provider settings. |
| Devin | Install Devin CLI, then choose Sign in to Devin in provider settings. |
| Muse Code | Install Muse Code on the server, run muse login, then enable it in settings. |
Provider CLIs must be on the server’s PATH. If VC cannot find one, set its
Binary path in provider settings, especially when using a version manager.
Cursor’s executable is cursor-agent. Antigravity can use its managed runtime without a PATH entry.
For Cursor, open the sign-in link and finish in your browser. The account is saved
on the selected environment, so the link also works when connecting remotely.
Cursor instances share that machine’s CLI sign-in; use Sign out of Cursor in
provider settings to disconnect it. You can still run cursor-agent login on
the environment’s machine instead.
Grok, Command Code, and OpenCode open their account flow in a setup terminal. Review the command, press Enter, and follow the prompts. Grok uses a device code that works from another device. Command Code’s browser flow needs browser access on the environment’s machine; otherwise use its manual account-key prompt. Use Sign out to disconnect, or close the terminal to cancel an unfinished flow. Closing the terminal refreshes provider status.
To switch from an API key to a subscription, remove API keys configured for the instance or inherited from its environment, then sign in with the subscription account. Signing out of the CLI does not remove keys from VC’s settings.
Kimi, Qwen, Hermes, Oh My Pi, Kiro CLI, Cline, and Qoder reuse the login and configuration of their installed CLI. Choose CLI default to let the CLI select its model. To load or update its model list, use Refresh provider status in Settings, or Refresh models in mobile thread settings. Background health checks retain that list without opening a new agent session.
When a provider CLI is behind its latest release, its provider card shows the available version. Update now appears only when VC can tell which installer owns the CLI (its own update command, Homebrew, or a global npm, pnpm, bun, or Vite+ install) and runs that installer. Otherwise update the CLI the same way you installed it. Homebrew installs compare against the version Homebrew offers, which can trail the npm release by a few hours.
Add another provider instance for a separate account or configuration. Each instance can have its own environment variables, such as API keys or a custom base URL. Mark secret values as sensitive; after saving, VC does not display their original values.
For provider-specific setup and accounts, see Codex, Claude, OpenCode, Antigravity, and Muse Code.
Next steps
- Working with threads: start tasks and organize parallel work.
- Permission modes: choose when agents ask before acting.
- Remote access: connect from another device.
- Running in the background: keep a Linux or macOS host available.
- Updating VC: update the app and connected servers.