Native Windows Build of Cursor CLI (Without WSL Requirement)

Ideas Feature Requests
, , ,
1

Feature request for product/service

Cursor CLI

Describe the request

I’d like to request a fully native Windows build of the Cursor CLI — similar to what Claude Code provides. Their CLI can be installed directly on Windows via a PowerShell script or through WinGet, and it runs natively without requiring WSL.

Right now, Cursor CLI depends on WSL, which creates friction for many Windows users. A native executable would make the tool far more accessible, easier to integrate into Windows-based workflows, and simpler to distribute in enterprise environments where WSL may be restricted or disabled.

Why this matters:

Native performance and better compatibility with Windows tooling

No need to enable or configure WSL

Easier installation (PowerShell script, WinGet, or MSI installer)

Aligns Cursor with other modern AI developer tools that already support Windows natively

A native Windows build would significantly improve the developer experience for a large portion of your user base.

Thanks for considering this enhancement — it would be a huge quality‑of‑life improvement for Windows developers.

Operating System (if it applies)

Windows 10/11

4

Hey, good news - native Windows support for Cursor CLI already exists.

You can install it directly via PowerShell without WSL:

irm 'https://cursor.com/install?win32=true' | iex

After installation, verify with:

agent --version

Full installation docs here: Installation | Cursor Docs

Let me know if something doesn’t work as expected.

5

Thanks, now it installs without WSL. Good, but that’s only half the battle because it’s not fully native. Every now and then, my console freezes, and I have to restart the terminal and resume the session. It’s probably because it’s Node.js. If you look at Claude Code, it has a native Rust executable, and it works reliably for me.

1 Like