[ENHANCEMENT] Consider lowering VS Code engine minimum to support Cursor and other VS Code fork users #591
Description
Is your enhancement request related to a problem? Please describe.
Starting with RobotCode 2.3.0, the minimum VS Code engine requirement was bumped from ^1.103.0 to ^1.108.0. Cursor IDE currently ships VS Code engine 1.105.1 (as of Cursor 2.6.21), which means Cursor users are stuck on RobotCode 2.2.0 and cannot access any improvements from 2.3.0 through 2.5.1 — notably the Robocop 8 integration introduced in 2.3.0.
Cursor does not follow VS Code's monthly release cadence for engine updates and typically lags by several months. There is currently no published timeline for when Cursor will rebase onto 1.108+.
Describe the solution you'd like
If feasible, lower the engines.vscode minimum back to ^1.105.0 (or even ^1.103.0). This would restore compatibility with Cursor IDE and potentially other VS Code forks (Windsurf, etc.) that may lag behind the upstream engine.
If 1.108-specific APIs are being used, a conditional/graceful fallback for older engines would be the next best option.
Describe alternatives you've considered
- Waiting for Cursor to update their engine — but there is no timeline and the gap keeps growing with each RobotCode release.
- Installing the VSIX manually — but Cursor enforces the engine check and rejects incompatible versions.
- Using VS Code alongside Cursor specifically for Robot Framework editing — works but defeats the purpose of a unified IDE.
- Staying on Robocop v7 — functional, but means missing out on Robocop 8 improvements and new rules.
Additional context
| Version | Engine requirement |
|---|---|
| RobotCode 2.2.0 | ^1.103.0 |
| RobotCode 2.3.0+ | ^1.108.0 |
| Cursor 2.6.21 (latest stable) | ships VS Code 1.105.1 |