: Auto-run Setting Not Working as Expected

Bug Reports
1

Bug Report: Auto-run Setting Not Working as Expected

Description

When the system is configured with:

  1. Auto-run is enabled (“Auto-run” option is selected)
  2. User specified “Don’t ask me, execute operations directly”

The system still shows “Run command” button and requires manual confirmation instead of executing commands automatically.

Expected Behavior

When both Auto-run and “Don’t ask me, execute operations directly” are enabled:

  1. Commands should execute automatically without showing the confirmation UI
  2. No “Run command” button should be visible
  3. Commands should process immediately after being entered

Actual Behavior

The system:

  1. Shows the command in a confirmation dialog
  2. Displays “Run command” button
  3. Requires manual confirmation to execute
  4. Does not respect the auto-run settings

Steps to Reproduce

  1. Enable Auto-run option
  2. Set system configuration to “Don’t ask me, execute operations directly”
  3. Enter any command (e.g., directory operations, helm commands)
  4. Observe that the system still requires manual confirmation

Environment

  • OS: Windows 10 (10.0.19045)
  • Shell: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Workspace Path: /d%3A/wt/sidecar

Impact

This bug:

  1. Breaks the automated workflow
  2. Requires unnecessary manual intervention
  3. Contradicts user settings and preferences

Additional Notes

The issue appears consistently across different command types and seems to be a fundamental issue with the command execution pipeline rather than being specific to certain commands.

Suggested Priority

High - This impacts automation capabilities and user experience

Possible Solution

Review the command execution pipeline to ensure it respects the Auto-run and execution preferences before showing any confirmation UI.

1 Like
2

Wispr_Flow_usVhBsIemf
Wispr_Flow_usVhBsIemf1698×319 32.3 KB

I don’t understand why it doesn’t work for me and it works for other people.

3

Please remove the Auto-run prompt content. It was removed in later versions of Cursor as it didnt work.

4

It doesn’t work either, in fact I just added it to see if it works, but even without the prompt it doesn’t work either.

5

The commands do not need paths usually, you have a few conflicting versions there. Also the commands cant contain wildcards

it should be just php artisan test

The Agent is able to run the command with the testfile etc after the command.

Is there a reason you are cross posting this everywhere and polluting the forum?

6

Thanks for the workaround @T1000 . I had been working hard to try and tune my allowlist prompt! but if I just delete the prompt and put the exact command I want in the list, everything goes smoothly.

1 Like
7

v0.48 which is rolling out will not have that issue as they removed the prompt.

8

It’s still not working -.-
image