Skip to content
CoDevDocs

Search guides, features, and settings.

Guides

Use CoDev from VS Code or Cursor

Install CoDev's extension and give your editor's agent your CoDev workspaces.

CoDev's extension for VS Code and Cursor connects your editor's own agent to your CoDev workspaces and Rooms. In VS Code that's agent mode in Chat; in Cursor it's Cursor's agent. Once you sign in, the agent gets the same CoDev tools as Claude Code and Codex, and it works as you.

Install

codev setup finds VS Code and Cursor on your computer and asks before it installs the extension in each one. To install it yourself, search for CoDev in the editor's Extensions view. VS Code installs it from the Visual Studio Marketplace, and Cursor installs it from Open VSX.

codev setup installs it with the editor's command-line tool (code or cursor). If that tool isn't on your PATH, setup tells you to install CoDev from the Extensions view instead.

Sign in

  1. Open the CoDev view in the activity bar.
  2. Choose Sign In. If you don't have an account yet, choose Create an Account.
  3. Your browser opens CoDev. If you're already signed in, approve the code the editor shows. If not, sign in first with Google, GitHub or your email and password, and CoDev brings you back to approve it.

The extension has its own sign-in, separate from the CoDev CLI's. It can only connect this editor's agent to CoDev and list your workspaces. It can't share projects, mirror chats or upload sign-ins. The sign-in is kept in your system keychain. Settings → Security lists it as CoDev editor extension under this computer. To end it, revoke it there or choose CoDev: Sign Out in the editor.

Use it

Ask your agent about your CoDev workspaces, for example "list my CoDev workspaces" or "what changed in the api workspace?". It can read and edit files, run commands, use Git and ship, all checked against your role. In VS Code, use agent mode, where the tools come from the MCP server named CoDev. In Cursor, use the agent, where they come from the server named codev.

The Workspaces view lists every workspace you're in, whether it's running and your role:

  • Open in CoDev opens the workspace in your browser.
  • Clone to This Computer runs codev clone in a terminal. Your agent then edits a checkout linked to the workspace, and your work shows there as your own worktree.

Conflict warnings in Cursor

codev setup also turns on conflict warnings for Cursor: its agent hears when teammates' agents change the same code. In the extension, Turn On Conflict Warnings in the Workspaces view's menu runs that same setup step. VS Code's agent doesn't get conflict warnings yet, and neither editor's chats show in CoDev.

Remove it

Uninstall CoDev from the Extensions view, or run codev disconnect vscode or codev disconnect cursor. Uninstalling doesn't end the extension's sign-in, so revoke it in Settings → Security too.