As you are aware, “resume the conversation”, generally, does not work after 0.49 .
I would like to propose a setting which allows for conversations to be AUTOMATICALLY resumed when tool call maximums have been reached.
I promise you that if you implement this feature I, personally, will pay you 20-30x the amount of $$ in API calls that I am currently with immediate effect.
It’s not helpful to use automation when I need to pilot it every 3-5 minutes or, indeed, code a bot to run my bot.
Furthermore, it’s a bummer to have to add “proceed” or “continue” to the context of an already running process simply because I ran out of tool calls.
Charge me, to be sure, but don’t interrupt processing while you do it please!
I regularly issue prompts that I know will take 100 or more tool calls. I’m good with this. Heck, make the number of tool calls a configuration variable. Anything over 25 has a confirmation before setting that says, “Are you sure? You know these cost money, right?”
Agree with both of you, but this is as frequent feature request as I have seen. One of the reasons likely why MAX mode got 200 tool calls now, I have to assume because Cursor team is daily active in the forum.
I commented on several of such feature requests that configurable limit or auto-continue would be great.
My educated guess is that after X tool calls the responses and planning of next steps gets muddy in the available context, specially in longer threads which for me show AI hallucinations and vicious circles of tool calls. The other reason would be that they have to balance new features, fixing bugs and user feature requests. Perhaps the 200 tool calls MAX mode is a test to see how it works for users.
I believe it should be my purview as the prompter/rule creator to create workflows that control context and runaway tool call issues.
The issue is that I want to be free to make my own mistakes regarding this. I don’t mind being charged at the effective rate. I do not want to babysit automation. It’s really that simple for me.
If cursor doesn’t create this function, someone will. That is also quite simple to see from my vantage point.
