Cursor is an AI‑assisted IDE that lets remote teams code together in real time. In this guide we walk through installing Cursor, linking it to Git, sharing sessions, and managing permissions. Follow each step and your team will move from “I’m stuck” to “We shipped” faster.
Visit cursor.com and click Sign Up. Choose the Team option. You will be asked for:
After verification you land on the Dashboard.
Click Invite, paste each colleague’s email, and set a role:
The invitation link expires after 7 days.
For Windows, macOS, and Linux download the client from the Download page. Run the installer and log in with the same credentials used on the web.
Open a new workspace, click the Git icon in the left sidebar, then Connect. Select GitHub and authorize Cursor. Paste the repository URL, for example:
https://github.com/acme/website.gitCursor clones the repo into a temporary container.
If you use a self‑hosted GitHub instance, go to Settings → Git Integration → Custom Provider. Enter:
API URL: https://github.example.com/api/v3
Token: ghp_XXXXXXXXXXXXXXXXXXXXMake sure the token has repo and admin:repo_hook scopes.
Cursor shows a branch dropdown at the top. Create a new branch with git checkout -b feature/login or click New Branch. When you push, Cursor automatically opens a Pull Request draft on GitHub.
In the workspace toolbar click Share. Choose:
Copy the generated URL and paste it in Slack or Teams.
Each participant gets a colored cursor with their initials. Hovering shows their name. The built‑in chat appears at the bottom right; you can also enable voice chat via the Integrations tab.
When two users type on the same line, Cursor flags the later edit with a yellow highlight and a suggestion button. Click Accept to keep the change, or Reject to revert.
Navigate to Team Settings → Roles. Assign one of the three roles per user. Permissions are:
| Role | Can Edit | Can Invite | Can Delete Workspace |
|---|---|---|---|
| Owner | Yes | Yes | Yes |
| Admin | Yes | Yes | No |
| Member | Yes | No | No |
For secret keys, go to Workspace Settings → Secrets. Add a key/value pair, e.g., API_KEY=abcd1234. The value is masked in the UI and never sent to the client browser.
Cursor’s AI suggests code after three characters. Turn off suggestions for large files (< 500 KB) to keep performance snappy. Settings → AI → File Size Limit.
Delete inactive workspaces weekly. In the Dashboard select a workspace and click Archive. Archived workspaces are read‑only and cost no compute credits.
Enable the built‑in ESLint integration: Settings → Linting → ESLint. Errors appear inline, and the team can fix them before committing.
The table below compares Cursor with two popular remote‑coding tools.
| Feature | Cursor | VS Code Live Share | CodeSandbox |
|---|---|---|---|
| AI Code Completion | Yes (Pro) | No | Basic |
| Built‑in Git Integration | Yes | Yes (via extension) | Yes |
| Self‑Hosted Option | Enterprise plan | No | No |
| Pricing (per user/mo) | Free / $12 Pro | Free | Free / $20 Pro |
| File Size Limit | 1 GB | 500 MB | 200 MB |
| Secret Management | Yes | No | Limited |
For most small to medium teams the AI boost and secret handling make Cursor the most efficient choice.
Cursor offers a free tier with unlimited collaborators, but the Pro plan ($12 per user per month) adds private repos, advanced AI completions, and priority support.
Yes. In Settings → Git Integration you can connect to GitHub Enterprise by providing a personal access token and the self‑hosted API URL.
Cursor uses Operational Transform (OT) to merge changes instantly. If two users edit the same line, the later edit appears as a suggestion that can be accepted or rejected.
Cursor is a web‑based IDE, so it works on any modern mobile browser. The interface scales down, but full keyboard shortcuts are only available on desktop.
All traffic is encrypted with TLS 1.3. Pro accounts store data at rest with AES‑256 encryption and support SSO via SAML or OIDC.
With these steps your remote team can adopt Cursor quickly, keep code secure, and stay productive across time zones.