New version does not respect autorun

Support Bug Reports
1

in 3.2.18 everything ok
in 3.2.20 i do not have nay auto run command, i have allow list and it is empty, but agent runs commands on its own

Version: 2.3.20 (user setup)
VSCode Version: 1.105.1
Commit: e3fd5c7abddff43abcd46fd93c25e85145200ad0
Date: 2026-01-02T20:39:53.706Z
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.19045

2

it appears to affect only the first command agent tries to run, the next ones ask for permission

3

Hey, thanks for the report.

I can see the issue. The first command runs without permission even though the allow list is empty. This might be related to a known bug that was fixed before, but it looks like it may be back.

Could you please share:

  1. What is your Auto-Run Mode setting? (Cursor Settings > Agents > Auto-Run)
  2. Which exact command runs without permission?
  3. Can you check if Legacy Terminal Tool is enabled? (Settings > search “legacy terminal”)
  4. If you can reproduce it, please share the Request ID (chat context menu > Copy Request ID)

This will help us figure out if this is a regression or a new issue.

4

image
image662×530 15 KB

(havent changed anything in past few weeks)
2. cd, git, php, anything really
3.
image
(always had this disabled)
4. request id: 956e3e55-33e8-415e-85c2-389d31ca06f4

7

Thanks for the info.

It looks like a regression related to bypassing the allow list for the first command. Similar bugs were fixed before, but it seems the issue is back in version 2.3.20.

Unfortunately, with Privacy Mode enabled, the logs aren’t available, which makes debugging harder. If you can, please temporarily turn off Privacy Mode (Cursor Settings > Privacy > Privacy Mode), reproduce the issue, then share the new Request ID. That’ll help the team find the cause.

I’ll pass this to the dev team to investigate.

8

this problem was fixed, but now is present again in this version:
Version: 2.3.41 (user setup)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
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.19045

9

I do not mean to intrude, but I am really curious how does Cursor’s versioning work internally, because it happens quite often:

a certain error is present in one version, fixed in next but in a newer version is present again… it is rather annoying

to me it seems that there are changes being merged into the public version that discard the previous fixes..