LaunchWithCursor

Knowledgebase

MissionWorkflowInstallUpdatesPromptsGitEnv varsDeployHandoffTesting
Knowledgebase5 min read

Keeping up to date

Stay on the latest extension without losing your starter pack or project sync.

LaunchWithCursor ships as a .vsix file you install from the dashboard — not from the public VS Code Marketplace. That means your editor will not auto-update the extension the way Marketplace extensions do. You stay in control: update when you are ready, on your schedule.

Why this matters: Marketplace auto-updates are convenient but opaque — you can wake up to a broken extension with no clear rollback. A deliberate update flow keeps your starter pack and project sync predictable.

How to update

The interactive panel below walks through both update methods step by step. Use whichever fits your workflow:

Option 1 — Check for Updates in the editor

  1. Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P).
  2. Run LaunchWithCursor: Check for Updates.
  3. If a newer version is available, follow the prompt, then Developer: Reload Window.
  4. Starter files refresh on reload. To force a full refresh of the pack, run LaunchWithCursor: Reinstall Starter Pack.

Option 2 — Re-download the extension

  1. Download the latest .vsix from Install & sign in.
  2. Extensions sidebar (Cmd+Shift+X / Ctrl+Shift+X) → ⋯ → Install from VSIX…
  3. Select the new file and reload the window. Reinstalling over the existing version replaces it — no uninstall needed.

Why “Check for Updates” and “Reinstall Starter Pack” both matter

Check for Updates pulls the latest extension binary — bug fixes, new commands, and compatibility with platform changes.

Reinstall Starter Pack refreshes .launchwithcursor/pack/LAUNCHWITHCURSOR/ in your repo when we ship new skills, deploy rules, or phase prompts. After a major platform release, run both: update the extension, reload, then reinstall the pack so your AI assistant reads the latest instructions.

Why this matters: Updating only the .vsix without refreshing the pack can leave your editor on new code but old deploy docs — a common source of “the dashboard says X but my assistant did Y.”

Staying in sync with the dashboard

After you update:

  1. Reload the editor window.
  2. Run LaunchWithCursor: Run Full Scan on your project folder.
  3. Confirm tooling status on the dashboard looks current (extension version, pack version).

Having trouble?

  • Open only one workspace folder per window.
  • Check the LaunchWithCursor output panel in the editor for errors.
  • Keep .launchwithcursor/cache/ in .gitignore, not the whole .launchwithcursor/ folder — you should commit pack/ and root AGENTS.md.
  • If terminal install fails, run Shell Command: Install 'code' command in PATH (or the Cursor equivalent) once from the Command Palette.

New to LaunchWithCursor? Start with Install & sign in.