Composer won't run commands anymore

Bug Report
1

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already – don’t see any

:lady_beetle: Provide a clear description of the bug:

No matter what I tell composer, it no longer runs commands - neither asks nor auto-runs when “YOLO” is on.

:arrows_counterclockwise: Explain how to reproduce the bug (if known)

Example:

  1. me: run tests with npm test
  2. composer: I’ll need to see the test output to help diagnose any issues. Could you please run npm test and share the results/errors?

Example:

  1. me: run “ls”
  2. composer: I don’t have direct access to run commands on your system.

This was working a week ago.

:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).

image
image2586×1450 409 KB

:computer: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Macos

  • 15.1.1 (24B2091

Cursor:

  • Version: 0.45.11
  • VSCode Version: 1.96.2
  • Commit: f5f18731406b73244e0558ee7716d77c8096d150
  • Date: 2025-02-07T09:43:58.555Z (1 wk ago)
  • Electron: 32.2.6
  • Chromium: 128.0.6613.186
  • Node.js: 20.18.1
  • V8: 12.8.374.38-electron.0
  • OS: Darwin arm64 24.1.0

Model:

  • claude-3.5-sonnet

:no_entry_sign: Tell us if the issue stops you from using Cursor.
This is slows collaboration with composer considerably. It’s a major impact on my (cursor-enhanced) productivity.

2

Could I confirm:

  • Your specific “YOLO mode” settings
  • That you’ve restarted the app after turning “YOLO mode” on (just in case)
  • That you’re definitely in agent mode in composer
  • Demonstrate the test query in agent mode running a basic command that you’ve whitelisted (or just give a description that “all commands are allowed” (maybe just turn on the mode preventing deletion of files).
3

FIXED!

I included my settings in the screen shot for this reason, but…

I didn’t even know there was a difference between “agent” and “normal” modes! Somehow I’d accidentally flipped that switch - it’s small, and right next to submit I guess and I must of miss clicked.

So, this could get converted to feedback/feature request: make it clearer what mode you are in. A simple suggestion: if you ask the “normal” mode prompt to run a command, it could explain you need to run it in “agent” mode to run commands.

Cheers! Thanks so much for the help. Hopefully others who have this problem will benefit.

1 Like
4

No problem, happy it was an easy fix :slight_smile:

5

Somehow I’d accidentally flipped that switch

sadly the switch sometimes switches by itself :frowning:
it taught me to look for the color of the submit button

  • blue = Agent
  • gray = Normal

Screenshot-2025-02-21T16.51.02