Tool/command allow-list gone in 2.0?

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It seems that in Cursor 2.0, the Auto-Run Mode allowlist is gone, and now your only options are:

  • Ask Every Time
  • Auto-Run in Sandbox
  • Run Everything (Unsandboxed)

If the allow-list functionality is gone, that means you have two choices:

  1. Run in “Ask Every Time” and manually approve every (for example) every pytest run, which would be a huge step backwards in the utility of Cursor for me
  2. Run in “Run Everything (Unsandboxed)” and have Sonnet 4.5 go crazy and do whatever it wants (totally unacceptable)

If this is an intentional change and the allowlist doesn’t return, I am canceling my subscription and never coming back.

Steps to Reproduce

Open Settings > Agents > Auto-Run.

Expected Behavior

You should be able to whitelist the commands you want Cursor to auto-run. You should not have to create the whitelist from scratch - it should use one you created pre Cursor 2.0.

Screenshots / Screen Recordings

Screenshot 2025-10-31 at 4.49.49 PM.png
Screenshot 2025-10-31 at 4.49.49 PM.png685×353 16.5 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.46 (Universal)
VSCode Version: 1.99.3
Commit: c9bf994907e303cf5a430bdec54af9e41e1ebed0
Date: 2025-10-31T20:49:33.175Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. The allowlist feature is still available via the Legacy Terminal Tool setting. Here’s how to enable it:

  • Open Cursor settings (Ctrl+Shift+J)
  • Go to the Agents tab
  • Find “Legacy Terminal Tool” in the Inline Editing & Terminal section
  • Turn it on

After enabling the Legacy Terminal Tool, the allowlist options for auto-run will return, and you’ll be able to whitelist commands like pytest.

Let me know if this resolves the issue.

3

Thanks @deanrie. I’ll switch back to the Legacy Terminal Tool, but candidly, I think shipping the new terminal tool without an allowlist is a very strange product choice.

2 Likes
4

Fully agreed with @Alex_Campbell above!

This is not a good choice since even in the Sandbox environment, the agent can commit when I haven’t reviewed the code yet. Please bring back the allowlist @deanrie

2 Likes
5

Agreed, I 100% need the allow list for run everything mode. I kinda baffles me they took this away. Assuming they will patch this in future verison. For now I’ll be using legacy terminal as well.

@deanrie Is there a timeline on fixing this issue?

6

Hey, @aj-hadrian, thanks for the feedback.

There’s no timeline yet for adding allowlist functionality to the new terminal. The team is aware of this request from many users. For now, if you need an allowlist, the supported option is the Legacy Terminal Tool.

I recommend continuing to use Legacy Terminal as you mentioned - it gives you the control you need while the new terminal evolves.