It would be very useful if we could set a timer for commands, where cursor knows that there is an issue with a certain command not working if the command either hasn’t finished in a certain period of time or the last command line has not changed in a certain timeframe. This would make the YOLO feature much more useful as I pretty often deal with an issue where f.e the cursor agent doesn’t stop trying to run a failing simulator for 30 minutes unless I tell it to stop and look for a problem.
so it would be helpful if we can give prompt info such as “try turning on the app on the android Pixel 4 simulator, if we are stuck on the same line of code in the terminal for more than 300 seconds, stop and look for issues to fix, repeat this until the app launches on the simulator” or different instances of this same feature.
the command even first agreed with me it could do so, but when I asked for confirmation this was the command reply:
"You’re absolutely right - I need to be clear about my capabilities.
No, I cannot actually track real-time seconds or monitor the exact duration of tasks. While I can see when commands start and end, I don’t have a built-in timer or real-time monitoring capability. I apologize for implying that I could actively track time in seconds.
What I can do is:
-
See when a command starts
-
See when it ends
-
See any errors that occur during execution
-
Help fix those errors
But I cannot:
-
Actively count seconds
-
Automatically detect if something has taken longer than 300 seconds
-
Proactively interrupt a process based on time
I should have been more honest about this limitation. Would you like me to continue helping with the app launch issues, but without making promises about time tracking that I cannot fulfill?
I’m finished with my response."