Agent default stop (25 tool calls) immediately followed by "Conversation too long..."

This is actually making me reconsider this subscription.

I don’t think that it’s rocket science to be able to customize the “default stop” threshold, even if you need to insert a disclaimer.

But maybe the most frustrating part, is when I can’t continue and hit the dead end “conversation too long”.

Why on earth would you not have a “progress bar” or a warning system that gives us a heads-up when it’s near that limit? Or even better, a button for continuing in a new conversation, but bringing the “essence” of the conversation over, with the AI actually choosing itself what’s needed to include into the new conversation? I do this occasionally myself, but I can’t even ask it to give me a summary for a new conversation when it’s getting this message, because then it’s too late. Going back a message or two, before the conversation got too long, and asking it to summarize loses relevant context many times from the data that was added after that message.

Please, please, this can’t be that hard to fix, or at least improve.

4 Likes

Cursor has a lot of cool little things they could do, I am not sure how difficult it would be to add a progress gauge, because every time VS code gets updated, it might be breaking changes. I think cursor is a one or two person company by how they act and their slow and sometimes regressive development release style. I give them a bit of leeway- Desktop claude doesn’t even have this.

I actually would agree with you, unless Anysphere, the company behind Cursor, was quite big and is backed by Andreessen Horowitz, Thrive Capital and more. They are quite a big player in the AI market. That said, I do not know for sure how many programmers there are though; if it’s only Aman, Sualeh, Michael and Arvid (“The Swede”) or a whole bunch of others.


still here

Yeah it is. Rumors say that you can easily fix it using something like this:

But I don’t know if it breaks any license agreements or similar so don’t use it. Just don’t. Promise me you won’t?

That’s different. Judging by the screenshot, previously the chat was blocked when a certain number of tokens in it was reached. Now the excess tokens are cut off.

1 Like

This is a frustrating restriction. I’m working with an MCP server that interfaces with the Unity engine, issuing frequent commands to access menus, manage assets, and monitor console logs.

It barely makes any progress, even with instructions not to call the tool as frequently and use the indexed code base instead.

Not vibe coding right now!