[Windows] IDE toast proposes Cursor CLI install when already installed, then runs Unix installer in Git Bash (MINGW64)

Support Bug Reports
, , , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On Windows, Cursor IDE shows a toast notification (bottom-left of the IDE
window) proposing to install Cursor CLI, even though agent is already
installed and on PATH. When the user accepts via the toast button, the IDE
runs the Unix installer (curl https://cursor.com/install -fsS | bash) in
the default integrated terminal — Git Bash / MINGW64 — which immediately
fails. The native Windows installer
(irm 'https://cursor.com/install?win32=true' | iex in PowerShell) is
not used.

This is not triggered from a chat; it’s an IDE-level notification. There is
no Request ID associated with the action.

These are two distinct bugs:

  1. Detection: IDE does not check whether agent is already on PATH before
    showing the install toast.
  2. Installer selection: On Windows the IDE should run the native installer
    in PowerShell, not curl | bash in Git Bash/MSYS. The Unix script does
    not support MINGW64_NT-* and would otherwise risk overwriting /
    conflicting with the existing native install in
    %LOCALAPPDATA%\cursor-agent.

Steps to Reproduce

  1. On Windows, install Cursor CLI natively:
    irm 'https://cursor.com/install?win32=true' | iex (in PowerShell).
    Verify with where agent and agent --version.
  2. Set Git Bash as the default integrated terminal in Cursor IDE.
  3. Open Cursor IDE. After some time, a toast appears in the bottom-right
    corner offering to install Cursor CLI.
  4. Click the install button on the toast.
  5. IDE opens (or focuses) the integrated terminal (Git Bash) and runs
    curl https://cursor.com/install -fsS | bash.

Expected Behavior

  • If agent is already on PATH → no install toast (or at most an
    update toast that uses agent update).
  • If install/upgrade is genuinely needed on Windows → run the native
    installer in PowerShell:
    irm 'https://cursor.com/install?win32=true' | iex
    Never run the Unix curl | bash script in Git Bash/MSYS, because:
    • it does not support MINGW64_NT-* (current behavior — fails fast)
    • if it ever stops failing fast, it could install a Unix-style binary
      into ~/.local/bin and shadow / conflict with the existing native
      install.

Operating System

Windows 10/11

Version Information

Version: 3.2.16 (user setup)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Existing CLI install (working, untouched):

  • Path: C:\Users\<user>\AppData\Local\cursor-agent\agent.cmd
  • Version: 2026.04.29-c83a488
  • Installed ~1 week ago via official Windows installer:
    irm 'https://cursor.com/install?win32=true' | iex
  • where agent resolves to the path above; agent --version prints the
    version correctly.

Actual result

Installer aborts in Git Bash:

Cursor Agent Installer

▸ Detecting system architecture...
✗ Unsupported operating system: MINGW64_NT-10.0-26200

No installation/upgrade happens. Existing native install is unchanged
(luckily — the Unix script bailed out on uname detection).

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @Roman_Habrat!

It looks like we supposed to exclude Windows users from this toast, but there was a bug. We just merged a fix. Thanks for the report!