Cursor Upgrade MigrationSAFE

Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: cursor-upgrade-migration
description: 'Upgrade Cursor versions, migrate from VS Code, and transfer settings
  between machines. Triggers on

  "upgrade cursor", "update cursor", "cursor migration", "cursor new version", "vs
  code to cursor",

  "cursor changelog".

  '
allowed-tools: Read, Write, Edit, Bash(cmd:*)
version: 1.19.0
license: MIT
author: Jeremy Longshore <[email protected]>
tags:
- saas
- cursor
- migration
compatibility: Designed for Claude Code
---
# Cursor Upgrade & Migration

## Overview

Upgrade Cursor or migrate settings through a staged, reversible rollout that preserves policy, extensions, rules, workspace trust, and user recovery.

## Prerequisites

- Current/target versions, release-note review, supported-platform confirmation, and a settings backup.
- Pilot users, a named migration owner, and an approved rollback or previous installer.

## Instructions

1. Inventory settings, extensions, rules, integrations, and identity/privacy requirements.
2. Test the target version with a pilot using non-sensitive workspaces and required workflows.
3. Document compatibility, performance, and policy results before broader rollout.
4. Roll back or pause on sign-in, privacy, extension, or workflow regression; retain evidence for follow-up.

## Output

- A staged upgrade/migration record with pilot evidence, owner, compatibility decision, and rollback instructions.

## Error Handling

| Condition | Safe response |
|---|---|
| Upgrade breaks policy or privacy behavior | Stop rollout, revert/pause, and escalate to the tenant owner. |
| Extension/settings migration fails | Restore the verified backup and remediate in the pilot. |
| Version is unsupported | Do not force installation; use the supported version or plan platform remediation. |

## Examples

Back up a pilot user's settings, install the target version in a test profile, verify SSO, privacy, rules, indexing, and a sample repository, then expand only after the pilot receipt passes. Keep the previous installer until the observation window closes.

Upgrade Cursor IDE versions, migrate from VS Code, and transfer configurations between machines.

## Version Upgrades

### Auto-Update (Recommended)

Cursor checks for updates automatically. When available:

1. A notification appears: "A new version is available"
2. Click "Restart to Update" or go to `Help` > `Check for Updates`
3. Cursor downloads, installs, and restarts

### Manual Update

If auto-update fails or is disabled:

```bash
# macOS (Homebrew)
brew upgrade --cask cursor

# macOS/Linux/Windows: Download latest from
# https://cursor.com/download

# Linux AppImage: replace the old file
curl -fSL https://download.cursor.com/linux/appImage/x64 -o cursor.AppImage
chmod +x cursor.AppImage
```

### Pre-Upgrade Checklist

```
[ ] Note current version: Help > About
[ ] Check release notes: changelog.cursor.sh
[ ] Backup settings:
    macOS: cp -r ~/Library/Application\ Support/Cursor/User ~/cursor-settings-backup
    Linux: cp -r ~/.config/Cursor/User ~/cursor-settings-backup
[ ] Export extension list:
    cursor --list-extensions > extensions-backup.txt
[ ] Commit any unsaved work to git
[ ] Note any custom keybindings (keybindings.json)
```

### Post-Upgrade Verification

```
[ ] Cursor launches without errors
[ ] Sign-in still active (check top-right user icon)
[ ] AI features work: try Cmd+L, type a question
[ ] Tab completion works: type code, see ghost text
[ ] Extensions loaded: Cmd+Shift+X, verify list
[ ] Custom keybindings preserved: test your shortcuts
[ ] Project rules still load: @Cursor Rules in chat
[ ] Indexing status: check status bar
```

## VS Code to Cursor Migration

### Automatic Import (First Launch)

On first launch, Cursor detects VS Code and offers one-click import:

```
What migrates:
  ✅ settings.json (editor preferences)
  ✅ keybindings.json (custom shortcuts)
  ✅ User snippets
  ✅ Color themes
  ✅ Compatible extensions (from Open VSX Registry)

What does NOT migrate:
  ❌ Microsoft-exclusive extensions (Copilot, Live Share, Remote-SSH)
  ❌ Extension login states / databases
  ❌ Workspace trust settings
  ❌ Task configurations (.vscode/tasks.json -- copies but may need adjustment)
```

### Manual Migration

If you skipped the auto-import:

```bash
# Copy settings (macOS example)
cp ~/Library/Application\ Support/Code/User/settings.json \
   ~/Library/Application\ Support/Cursor/User/settings.json

# Copy keybindings
cp ~/Library/Application\ Support/Code/User/keybindings.json \
   ~/Library/Application\ Support/Cursor/User/keybindings.json

# Copy snippets
cp -r ~/Library/Application\ Support/Code/User/snippets/ \
      ~/Library/Application\ Support/Cursor/User/snippets/

# Reinstall extensions (from backup list)
while read ext; do cursor --install-extension "$ext"; done < extensions-backup.txt
```

### Extension Marketplace Differences

Cursor uses **Open VSX Registry** instead of Microsoft's VS Code Marketplace:

| Extension | Status in Cursor |
|-----------|-----------------|
| ESLint | Available (Open VSX) |
| Prettier | Available (Open VSX) |
| GitLens | Available (Open VSX) |
| Docker | Available (Open VSX) |
| Python | Available (Open VSX) |
| GitHub Copilot | Not available (Microsoft exclusive, also conflicts with Cursor AI) |
| Live Share | Not available (Microsoft exclusive) |
| Remote - SSH | Not available (Microsoft exclusive) |
| C# Dev Kit | Not available (Microsoft exclusive) |

**For unavailable extensions**, download `.vsix` from the VS Code Marketplace website and install manually:
`Cmd+Shift+P` > `Extensions: Install from VSIX...`

### Running VS Code and Cursor Side-by-Side

Both can be installed simultaneously. They use separate:

- Settings directories
- Extension directories
- Configuration files

You can open the same project in both editors at once (though be careful with file save conflicts).

## Migration Between Machines

### Export Configuration

```bash
# List all extensions
cursor --list-extensions > cu

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.