When using YOLO (which btw is a fantastic addition), it only seems to run the command for 6-7 seconds and then sends a ctrl-c to the command. This can break installation scripts, pip commands, apt-commands, test suites and so on. This should be customizable. “Wait for X seconds OR until the prompt is shown again.”
What version of Cursor are you on? And do you have command detection enabled in your terminal?
I’m on 0.44.8. If it’s of any use it’s a “remote shell”, but I don’t expect that to make any difference.
Indeed I have Shell Integration activated:
It still keeps cancelling the npm install commands it’s trying to run and the same occasionally with pip installs.
Here, with shell integration enabled, is a prime example of how this messes things up:
And no, I didn’t press CTRL+C, Cursor did. Not only does it cancel the command, but it misinterprets it as completed successfully.
Tell it not to run commands in conjunction and to run them separately and telli it to "wait and confirm that all requirements dependencies are properly installed before proceeding to next steps.
Or decouple it from a yolo - and tell it to check in as it goes. Also tell it to narrate as it goes and produce a verbose development_diary.json, or diary.rmd about what it has accomplished.
You dont blindly throw a bto with YOLO…
YOU give it a concise goalpost and have it get to that step in a YOLO then check it progress and adjust its trajectory.
I have indeed tried that as well, and it is a temporary workaround but far from a solution. Sure, it does take a bizarre amount of time, and the amount of requests increase dramatically, but it works… at least in some cases. It’s still useless when you have a single command that can take 20-30 seconds to finish. The odd part is that it doesn’t always act this way, just most of the time.
Whenever it’s taking too long i I say “keep going” and it jolts it back itnro action.
Telling the AI to “keep going” doesn’t help if the actual terminal command is taking longer to finish on its own.
Yes, though at times I cant tell if its stuck on generating, or the calc is slow…
So it may be a subjective placebo POV, but it feels(?) faster?? 
I mean, there are times when it actually does get stuck and just can be told to “G
et a grip!”, but it’s easy to tell. When a command is not running, and never will be, the command stays in one box, without a line splitting it in have to show its output, while it still says “Generating…”. Then you can talk to it and speed things up (that would likely never start-up again anyway).
Well that happens to me many times a day… Which is why I have an AI Behavioral Complex imprinted on me MK AI-ULTRA style…
What’s this YOLO mode everyone’s talking about? I tried searching the docs for “yolo” but found nothing.
Go to cursor setting and enable the ability for the Composer Agent to write files to the files suystem, modify, delete, execture and run software - install pacage requirements, harvest code from cloned git repos to interleave into your code, use github gh cli to create, manage, update, organize, document repos in github account…
describe and create detailed readme files and access the DB directly to create databases, schemas…
I used irt to manage my shares and users on my machine - with a ps1 I yolod through a windows user, drive, share management CLI TUI…
=====
You can invoke YOLO by directing composer agent "
Do [a bunch of things]
Yolo mode is enabled OR, as I do:
>>“yolo through this until you need my input - iterate on these files and when you find an error, fix the error and look for at least one improvement to the implementation.”
###NOTE: Cursor Yolo is NOT for Prod ANYTHING
Its a sandbox feature which helps rapid proto, mvp, directory setup - super basic stuff… it dissolves log in relation to project complexity.
1 Like
EDIT: Never mind. It does work, just not 100% of the time.
EDIT2: Ok I turned off the yolo mode and it’s still yoloing. -_-’
This doesn’t work. I turned on the stuff in Chat & Composer that you have in your screensot, then opened a new chat window and tried both:
yolo extract the conversation-controls part of App.tsx into ConvoControls.tsx as a separate component.
and:
“yolo extract the conversation-controls part of App.tsx into ConvoControls.tsx as a separate component.”
(last one just incase the >> and the “” were part of the yolo-feature syntax. No changes were auto-made to my files. Chat acted as if the yolo thing wasn’t turned on at all.
Cursor version:
Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Linux x64 6.1.75-1.qubes.fc32.x86_64