Request: Upgrade VS Code Extension API base beyond 1.105.1

Ideas Feature Requests
,
1

Feature request for product/service

Cursor IDE

Describe the request

Hi Cursor team,

I’m writing to request a higher VS Code Extension API / engine version in Cursor.

Current situation

  • Cursor reports: VS Code Extension API 1.105.1 (About Cursor)
  • Upstream VS Code is now at 1.125.0
  • The gap is roughly 20 minor releases, which is causing real compatibility issues in daily workflows.

Problem
Many high-quality VS Code extensions either:

  1. Refuse to install because their engines.vscode requirement exceeds 1.105.1, or
  2. Install but fail to activate / lose features that depend on newer VS Code APIs or runtime behavior.

This makes Cursor feel incomplete compared to VS Code for extension-heavy workflows, even though Cursor’s AI features are a major reason I want to stay on the platform.

Impact

  • Extension marketplace friction (Open VSX + engine version checks)
  • Missing upstream bug fixes, security patches, and editor improvements
  • Teams cannot fully migrate to Cursor if they depend on extensions that require newer VS Code versions
  • Custom / in-house extensions built against current VS Code APIs may silently break

Request

  1. Prioritize rebasing Cursor onto a newer VS Code base (target: as close to current stable as practical)
  2. Publish a clear policy on VS Code base update cadence (e.g., “within N months of upstream stable”)
  3. Communicate roadmap when a rebase is planned, especially around major Cursor releases

What would help prioritize
I’m happy to share a list of specific extensions that fail on 1.105.1 if that helps the team triage. Community threads like “Update vscode version to latest” already show strong demand (600+ replies).

Cursor is my preferred editor because of its AI-native workflow — upgrading the VS Code base would remove one of the biggest blockers to using it full-time.

Thanks for considering this.

1 Like