WSL: "Run in Sandbox" not available

Support Help
1

I run Cursor in WSL. Based on https://cursor.com/docs/agent/terminal “Run in Sandbox” should be available in the “Auto-Run Mode” drop-down. It is not there. I have confirmed I meet these requirements:
* Kernel 6.2 or later with Landlock v3 support (CONFIG_SECURITY_LANDLOCK=y)
* Unprivileged user namespaces enabled (most modern distributions have this by default)
I am also running Cursor version 2.3.18
Am I correct that sandbox should be available for me? If yes, is there a known issue?

Thanks

3

Hey, thanks for the report.

The “Run in Sandbox” option is only available with the new terminal. You need to turn off Legacy Terminal if it’s enabled:

  • Open Cursor Settings Ctrl+Shift+J
  • Search for “Legacy Terminal Tool” under Agents > Inline Editing & Terminal
  • Disable this setting

After that, the “Run in Sandbox” option should show up in the dropdown.

4

Sadly, that doesn’t solve it. I didn’t know that, but unfortunately, the “Legacy Terminal Tool” had already been turned off. I confirmed “Run in Sandbox” is still not available.

image
image1017×100 3.14 KB

image
image1027×232 8.16 KB

1 Like
7

@dmschlot Sorry for the issues! Can you open the Output pane (on the same section as terminal) and look at the “Extension Host” and “Extension Host (remote)” logs to see if there is anything Interesting in there?

8

@ani-anysphere
I do not see anything containing “Host”. I just restarted Cursor, checke settings again, and this is all that was in “Output”. As shown below there is one error: Failed to patch code.sh launcher

2026-01-05 09:36:30.297 [info] Resolving wsl remote authority 'wsl+ubuntu' (attempt #1)
2026-01-05 09:36:30.297 [info] Installing cursor-server with options: {"id":"795ca53be97e55773dd744e8","commit":"68e0a0385b87408d050869ea543e3778ad53f780","line":"production","realCommit":"68e0a0385b87408d050869ea543e3778ad53f78a","extensionIds":[],"serverApplicationName":"cursor-server","serverDataFolderName":".cursor-server","forceReinstall":false,"killRunningServers":false}
2026-01-05 09:36:30.297 [error] Failed to patch code.sh launcher: Error: ENOENT: no such file or directory, open 'c:\Users\david\AppData\Local\Programs\cursor\resources\app\bin\code'
2026-01-05 09:37:01.794 [info] [wsl exec: installServerScript][stderr]: 2026-01-05 09:37:01 URL:https://downloads.cursor.com/production/68e0a0385b87408d050869ea543e3778ad53f78a/linux/x64/cursor-reh-linux-x64.tar.gz [76616155/76616155] -> "/tmp/tmp.Cr3QXKIcFP" [1]
2026-01-05 09:37:05.336 [info] [wsl exec: installServerScript][stderr]: your 131072x1 screen size is bogus. expect trouble
2026-01-05 09:37:05.468 [info] Successfully connected to Cursor server at http://127.0.0.1:33505/version from Windows
2026-01-05 09:37:05.468 [info] Returning resolved authority for Cursor server at http://127.0.0.1:33505/version from Windows. Returning token: 72bbe5e2-6a67-45e1-9855-d5b442a3e2fa
10

@ani-anysphere Sorry, in a rush I misread your message. I do see some interesting info in “Extension Host (Remote)”. See below. There are a number of “undefined” references

2026-01-05 09:37:15.116 [error] [shell-exec:sandbox] [isSandboxHelperSupported] Starting sandbox support check... undefined
2026-01-05 09:37:15.116 [error] [shell-exec:sandbox] [checkBinaryAvailable] Resolved binary path: /home/davidsch/.cursor-server/bin/68e0a0385b87408d050869ea543e3778ad53f780/resources/helpers/cursor-sandbox undefined
2026-01-05 09:37:15.116 [error] [shell-exec:sandbox] [checkBinaryAvailable] Binary path exists: true undefined
2026-01-05 09:37:15.116 [error] [shell-exec:sandbox] [isSandboxHelperSupported] Running preflight with binary: /home/davidsch/.cursor-server/bin/68e0a0385b87408d050869ea543e3778ad53f780/resources/helpers/cursor-sandbox undefined
2026-01-05 09:37:15.116 [error] [shell-exec:sandbox] [isSandboxHelperSupported] CWD: /mnt/c/Users/david/AppData/Local/Programs/cursor undefined
2026-01-05 09:37:15.116 [error] [shell-exec:sandbox] [isSandboxHelperSupported] Preflight succeeded, sandbox supported! undefined
12

Has anyone seen this issue before, or have a guess as to what the problem could be?

Thanks

14

Has anyone seen this issue before, or have a guess as to what the problem could be?

Thanks

16

@ani-anysphere and @deanrie ,

Sorry to bother but based on my logs, do either of you know what I should do next?

Thanks

18

We’ve made some fixes to this in the next release coming out soon, hold tight for a bit (enable beta releases and it should show up sooner)