Cursor-agent does not work in WSL - node: cannot execute binary file: Exec format error

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

$ cursor-agent --help
/home/cnd/.local/bin/cursor-agent: line 10: /home/cnd/.local/share/cursor-agent/versions/2025.12.17-996666f/node: cannot execute binary file: Exec format error
/home/cnd/.local/bin/cursor-agent: line 10: /home/cnd/.local/share/cursor-agent/versions/2025.12.17-996666f/node: Success

Steps to Reproduce

curl Cursor CLI · Cursor -fsSL | bash
cursor-agent --help

Expected Behavior

Should work - you need to STOP SHIPPING THE BROKEN UPSTREAM NODE BINARY - this used to work, then someone there updated and didn’t test anything, and shipped it.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Current as of today - cannot get version, because you broke it

Additional Information

This bug has been reported by users MANY TIMES BEFORE for months now

Please add this into your engineering todo list as a top priority ASAP

Does this stop you from using Cursor

Yes - Cursor is unusable

3

You guys broke this back in September
PLEASE FIX IT!!!

This is the workaround, which only works for 1 day and has to be manually re-applied, because you code keeps auto-updating and re-breaking itself every time I run it!

[cnd@RoG:~/.local/share/cursor-agent/versions]$ dir `find | grep /node$`
-rwxr-xr-x 1 cnd cnd 121613584 2025-09-12 11:35 ./2025.09.12-4852336/node
-rwxr-xr-x 1 cnd cnd 121613584 2025-09-18 04:51 ./2025.09.17-25b418f/node
lrwxrwxrwx 1 cnd cnd        26 2025-10-04 02:18 ./2025.10.02-bd871ac/node -> ../2025.09.17-25b418f/node
lrwxrwxrwx 1 cnd cnd        26 2025-10-24 21:39 ./2025.10.20-f1b214f/node -> ../2025.09.17-25b418f/node
lrwxrwxrwx 1 cnd cnd        26 2025-10-24 21:41 ./2025.10.22-f894c20/node -> ../2025.09.17-25b418f/node
lrwxrwxrwx 1 cnd cnd        26 2025-12-10 07:48 ./2025.11.06-8fe8a63/node -> ../2025.09.17-25b418f/node
lrwxrwxrwx 1 cnd cnd        26 2025-12-10 07:52 ./2025.11.25-d5b3271/node -> ../2025.09.17-25b418f/node
lrwxrwxrwx 1 cnd cnd        26 2025-12-18 18:45 ./2025.12.17-996666f/node -> ../2025.09.17-25b418f/node
5

Hey, thanks for the report. To diagnose, we need to know which WSL version you’re using.

Could you run these commands and share the output?

wsl --version
uname -a

If you have WSL1, cursor-agent officially supports only WSL2. If it’s WSL2, this might be a bug.

6

The version of WSL is irrelevant - this is a linux distro problem - you’re shipping a broken node binary - it’s not even your fault!

Go back to shipping the version you had a few releases ago:-

$ 2025.09.17-25b418f/node --version
v22.18.0

THAT works fine.