@ericzakariasson@danperks@deanrie Hey, guys, what do you think? I’m seeing a lot of support so far. Just need quick request that is automatically consumed after every 25 tool calls
I don’t think it will have any effect on the cost of cursor. For example, if the model is 3.7 One hundred tool calls at a time, that would consume four fast requests. It just becomes auto-continue and smarter
If there’s a major issue allowing yolo runs then perhaps you could allow for a condition in passing test cases in TDD. It’s working really well to red/green/refactor until 100% passing test cases. 3/10 runs require the manual click even though I have a legit stop condition with the test output piped into a log file.
Also often I get another error after pressing continue.
Connection failed. If the problem persists, please check your internet connection or VPN.
This on my way on autonomous development. If you wont fix it soon, I will switch to Claude Code next month for sure - this does not have this issue.
So my flow is currently wait until this 25 limit comes. Then usally error comes and I need to type in \continue\ until again this 25 limit comes. This is really bad! For one feature development I need to do it 10 times or more
Important to note that GitHub Copilot provides this as a setting chat.agent.MaxRequests
“The maximum number of requests to allow Copilot Edits to use per-turn in agent mode. When the limit is reached, Copilot will ask the user to confirm that it should keep working.”
It’s been almost two months any progress to update here?
Another feature request asks to increase the limit that feels more like the correct choice here Increase the 25 tool calls limit please leave an upvote if you agree or add your thoughts.
+1 here, it stops virtually any workflow I have and it makes me be in front of the macbook staring at the AI doing things cuz at any moment I need to hit retry and workaround it when it fails. We want to automate, not to micromanage.
I understand it’s a hard pain thing so they can use it as commercial limitations, however the limits of the Business version are also unacceptable. and, if I need to code a MAS as alternative client to avoid having these limitations Cursor won’t be useful anymore anyway so not sure what are they thinking…
This feature is very much needed, especially while the Background Agent is NOT stable yet.
Please LET US set the limit OURSELVES in Settings.
The loop is BS because you developed the background agent where you removed the 25 tool call limit.
I am on a Peloton ride, watching the Agent, and every couple minutes, I have to get off the peloton and click Continue. After 30 minutes the Agent is still not done. The Agent NEVER goes in a loop. It just had to go through 120 files. Now I want to shower, but my Agent can’t continue because it will stop after 25 tool calls.
I tried the Background Agent, but it is still too buggy for these kind of tasks.
So just letting us increase the tool calls limit IS what we want, and WE are happy to pay for additional 25 tool calls. I literally will set the limit to 1000+ and see the Agent go through all my files.