Allow hardware GPU rendering for locally-launched browser instances (disable SwiftShader on macOS)

Feature request for product/service

Anysphere Extensions (Remote SSH, Python, Dev Containers, WSL, C/C++/C#)

Describe the request

The cursor-browser-extension launches Chrome with --enable-unsafe-swiftshader on macOS, forcing all GPU work through software rendering. This causes the Chrome GPU helper
process to consume 300%+ CPU continuously, making the entire machine sluggish.

The relevant code in cursor-browser-extension/dist/main.js:

"darwin" === platform() && args.push("--enable-unsafe-swiftshader")

I understand this is a reliability tradeoff that makes sense for cloud/headless agents, but for local development on a Mac with a capable GPU, it's unnecessarily punishing. A single
 automated browser tab can pin 3+ cores and push the system into heavy swap.

Request: Add a setting like cursor.browser.enableHardwareGpu (default false to preserve current behavior) that omits the --enable-unsafe-swiftshader flag when set to true, allowing
the local Chrome instance to use native GPU rendering.



### Operating System (if it applies)
MacOS