How could I disable powershell scripts attach to a docker container

Support Help
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

My usage scenarios: Windows server 2022 – Linux sever(Ubuntu) – Docker Container(linux/ubuntu).
The cursor ID is installed in windows server. This server has a policy of strictly forbit user/apps run powershell or WSL scripts.
cursor works well when it connect to the linux server, while it could not attach to docker containers because it will invoke some powershell scripts.
Why it invokes local powershell scripts when attach to a container? Is there a method to disable this behavior?

Steps to Reproduce

usage scenarios: Windows server 2022 – Linux sever(Ubuntu) – Docker Container(linux/ubuntu).
Attach to dev containers. It will invoke local powershell scripts.

Expected Behavior

No local script run.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.20348

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Hey, thanks for the report, that’s an interesting case with a restricted policy on Windows Server.

To dig in, I’ll need the Dev Containers extension logs:

  • Press CTRL + Shift + P, then run Developer: Show Logs…, and pick Dev Containers
  • Try attaching to the container
  • Copy the error logs

This will show which scripts the extension is trying to run.

Also, as a workaround, try setting terminal.integrated.defaultProfile.windows to cmd instead of PowerShell:

"terminal.integrated.defaultProfile.windows": "Command Prompt"

And let me know if you can add a policy exception for Cursor processes. That might be the only solution if those scripts are required to work with containers.

5

hi @deanrie , Thanks for your quick response!
I find this issue disappeared when I collect logs. Cursor attach docker successfully today without any error or warning. Both cursor and Dev containers keep same without any updates. If this issue occurs again in recently days, I will attach its log here next time.
BTW, cmd.exe is also blocked. I guess the only command line tool allowed is “MobaXterm”. :pensive_face:
Thanks all the same!

1 Like