Urgent: The 1.105 VS Code base is now 5+ months old. We need a modern upstream sync

Hi Cursor Team,

I am writing to strongly urge the team to prioritize shifting Cursor to a newer VS Code base. We are currently stuck on a version based on VS Code 1.105, which is now roughly five months old.

While we all deeply appreciate the incredible AI-native innovations you are shipping (like Composer and background agents), staying this far behind the upstream repository is starting to cause friction.

We are beginning to run into critical issues that only an upstream shift can fix:

  • Extension Incompatibilities: Many popular marketplace extensions are updating their engines, causing breaks or outright failures when running on an older API host.
  • Missing Core Features: We are missing out on months of core VS Code stability patches, terminal improvements, notebook fixes, and native UI refinements.
  • Performance Lag: Upstream VS Code has introduced several memory and rendering optimizations over the last few cycles that Cursor users are missing out on.

We love this tool, and many of us rely on it as our primary, paid IDE. However, an AI-native code editor still needs a modern, stable editor foundation.

Please let the community know:

  1. Is there an active roadmap or timeline for the next major upstream VS Code sync?
  2. What are the primary technical blockers preventing this shift right now?

Thank you for your hard work, and we hope to see a base update soon!

1 Like