Cursor does something with truncating context to save costs on their end, you dont get the same with Cline because you're paying for each transaction - so depending on complexity I find Cline works significantly better.
I still use cursor chat with agent mode though, but I've always been indecisive. Like the others said though, its nice to see how cline behaves to assist with creating your own agentic workflows.
Totally anecdotal of course so take this with a grain of salt, but I've seen and experienced this when Cursor chats start to get very long (eg the context starts to really fill up). It suddenly starts "forgetting" things you talked about earlier or producing code that's at odds with code it already produced. I think it's partly why they suggest but don't enforce starting a new chat when things start to really grow.
I don't really have this problem of long chat that everyone seems to have. Usually I can accomplish what I need to do after less than 10 turns. If I don't, then I naturally just want to restart the conversation adding whatever discovery from last time, at that point I just accept the current state (or discard all) and create a new chat, perhaps phrase it differently. Naturally I just feel that is easier not because I encounter any regression in my task.
It helps that the task is usually self-contained, but I guess as an engineer, it's kinda in your instinct to always divide and conquer any task.
It's actually very easy to see for yourself. When the agent "looks" at a file it will say the number of lines it looks at, almost always its the top 0-250 or 0-500 but might depend on model selected and if MAX mode is utilized.
> Cursor does something with truncating context to save costs on their end
I have seen mentioning of this but is there actually a source to back it up? Tried Cline every now and then. While it's great, I don't find it better than Cursor (nor worse in any clear way)