Your conversation is too long - after single Terminal prompt

[EarthmanMedia]

Bug Description:

This is popping up immediately in new Composer Agent threads. Problem just started this morning, 20 minutes ago. I can’t get anything done in claude sonnet or haiku, agent mode, I get locked out with “Conversation too long” almost immediately

It appears specific to when I have AI run my test via an inline terminal to analyze test results. This was working amazingly well yesterday and AI was able to review many test runs in a single thread.

Today, I can’t run a single test, let alone have it work on any code. A single prompt yields “Your conversation is too long” and locks me out : Was there a change pushed today to cause this regression?

Please help! I am subscribed to Cursor Pro

Checked the forum: I have reviewed the forum, and the issue does not appear to be reported already.

Steps to Reproduce:

See screenshot below:

• Create a new composer in agent mode - claude sonnet
• Using cursor project and global rules
• Ask it to run a Jest test to analyze output

Screenshots/Recordings:

Operating System and Cursor Version:
MacOS: 15.3.1 (24D70)
Cursor Version: 0.45.15
VSCode Version: 1.96.2
Commit: a2826398d8d8197cad72fb0cfdc1f472aa7cf050
Date: 2025-02-19T23:45:10.453Z (2 days ago)
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

Impact on Usage:
I can’t get anything done

[danperks]

Hey, my guess here is that the output in the terminal is huge, and filling up the conversation length! I’d have to check with the team how we process terminals in this case.

In v0.46, you can now @terminal to pull in context, so I’d recommend running the tests in the terminal for now, and trying to @ it to see if that stops you getting blocked here.

[T1000]

Yes im also seeing similar case more frequently.
Mostly it appears like the LLM is not seing or is ignoring some early output.
Strangely as most things happen in terminal (running tests etc…) its not clear how to avoid long outputs or if this can be done without terminal.
In any case the terminal output is not cleared between each execution of command so it has a long long history apparently.

[EarthmanMedia]

I understand why it would happening at the end of a very long thread

…but on that day in particular, all of a sudden it started happening after a single terminal output, where the previous day I had run the EXACT SAME terminal commands with the same length of output *dozens of times in the same thread, without an overrun.

So maybe a new limit was imposed at that time? Was it?

Since then I have not yet turned back to developing those jest tests, so am unclear if the issue persists…

Once the bug is fixed that keeps me from moving the Chat pane where I want it, then I will update and try out your suggestion, thanks @danperks

[danperks]

BTW You can already pop out the Chat window as an Editor, which means you can re-arrange it like any of your code windows.

You can also swap which side the sidebars are on, if you would prefer them to be flipped!

[EarthmanMedia]

Thanks, Dan, for these workaround ideas.

As mentioned in my comments, and the ones that are provided by other people here, this functionality is something that we use, and we don’t want to use the browser pop out, in my experience, it also has its own bugs, and also causes problems when opening files, because the focus is lost.

nor do we want to have the AI panel opposite to the explorer, for the reasons previously expressed as well as an ideal user experience.

rather putting the pane into the panel or into the primary side far is the functionality that we have grown accustomed to and would like restored, please

This is important functionality for giving us the interface that we love in cursor and want to preserve.

[EarthmanMedia]

Oops, it looks like we jumped threads, I suppose I should be pasting this in the other one,