I’ve been doing browser testing with Cursor’s IDE browser and noticed it’s currently running Chromium 142.0.7444.235, while the current stable Chrome is at 144.x.x.x .
My Question:
What’s Cursor’s approach/policy for keeping Chromium versions up-to-date?
Do you aim to stay within a specific number of major Chrome stable versions?
Are there plans to update to Electron 40+ (which includes Chrome 144)?
I’m asking because the version gap has practical implications for browser-based testing and development work.
My Environment:
Cursor Version: 2.4.28
Chromium: 142.0.7444.235
Electron: 39.2.7
Platform: macOS
Understanding your versioning strategy would really help me plan testing workflows. Thanks for any insights you can share!
Love the product overall! I just want to make sure I’m using the browser features effectively.
Cursor’s Chromium version is tied to the Electron framework, which comes from upstream VS Code that Cursor is built on. So when we rebase onto a newer version of VS Code, Electron and Chromium get updated along with it.
We don’t have a formal published policy that guarantees staying within a certain number of Chrome major versions. These updates happen from time to time as part of larger rebases onto upstream VS Code, and the timing depends on a few factors like compatibility, stability, and whether new features are needed.
For browser testing where you need the very latest Chrome features, you’ve got a couple options:
Use an external Chrome instance via an MCP server
Keep using the built-in browser for general testing, but validate behavior on your target Chrome version in a separate browser for features that depend on very recent APIs
The built-in browser is great for visual testing, layout checks, and general dev workflows, but because of Electron’s release cycle, it’ll always lag a bit behind the latest stable Chrome.
Let me know if you’ve got any other questions about planning your test setup.