Connect Cursor or Visual Studio Code to Cursor CoLab: sign in, open a shared session, and keep your edits in sync with the cloud so teammates see updates when you save.
What you get
Sign in with the same email and password you use on the Cursor CoLab website.
Session picker — choose a session you created or joined; the extension opens it as a workspace.
Save to sync — when you save a file, changes are sent to your Cursor CoLab server so the session stays up to date for everyone.
Session lock — helps avoid two people editing the same session at once (when your server supports it).
Requirements
A Cursor CoLab account (sign up through the web app).
Your team’s API URL running and reachable from your machine (your admin shares this).
By default the extension may point at a local development URL — change it in Settings for production.
Settings
Open Settings and search for Cursor CoLab, or edit User settings (JSON).
Setting
What it does
Cursor CoLab: Api Base Url
Base URL of your Cursor CoLab API (no trailing slash), e.g. https://api.example.com.
Cursor CoLab: Beta Password
If your server uses a beta gate, enter the password your team uses; otherwise leave default or empty if the gate is off.
Cursor CoLab: Sync On Save
When enabled, saved files are uploaded to the session API.
Cursor CoLab: Show Session Picker On Activate
When enabled, the full session picker opens after the extension loads.
Getting started
Install Cursor CoLab from the Marketplace (or install a .vsix your team provides).
Set Api Base Url to your server’s URL.
Use the Sessions icon in the activity bar, or run Cursor CoLab: Open session picker from the Command Palette.
Sign in, pick a session, then edit files — use Save to sync.
Cursor “plugins” vs this extension
This package is a VS Code–compatible extension (.vsix). Cursor also supports a separate plugin format (rules, MCP, etc.) from the Cursor Marketplace. For sign-in, session UI, and save sync, use this extension; optional Cursor plugins can add extra AI rules on top.
Help and privacy
Issues & feedback: use the Repository or Issues link on this Marketplace page.
Session files are stored in the extension’s managed workspace folder so your project opens like a normal folder; use a production HTTPS API in real deployments.
