Composer-1 Unreliably Creates "Context Summary" After Hitting Token Limit

Support Bug Reports
,
1

Since updating to Cursor 2.0 and starting to use the Composer-1 model, I’ve been facing a persistent issue. When the chat reaches its token limit, Composer-1 almost never generates a “context summary” automatically. Instead, it prompts me to continue in a new chat—stating that a “context automatic summary” will be included—but in practice, the new chat starts from scratch with no retained context, which disrupts my entire workflow.

In rare and seemingly random cases—often when Composer-1 has generated its own internal todo list, especially during file-related tasks—it does create a proper “context summary” and continues the conversation seamlessly. However, this behavior is inconsistent and occurs very infrequently.

I always use the latest version and am on the Ultra plan. Could you please clarify if this is a known issue and how it can be resolved? If this has already been discussed, I’d appreciate a link to the relevant thread.

3

It’s worth noting that I don’t experience this issue with other models like Claude Opus, Sonnet, etc.—they handle context continuation more reliably. The problem appears to be specific to Composer-1.

4

Hey, thanks for the report.

This is a known issue with summarization, and the team is working on a fix. What you’re describing (no automatic context summary when moving to a new chat) really isn’t expected. Cursor should automatically create a summary of the earlier messages.

To help the team understand this better, could you share:

  • The Request ID from the chat where it happened (click the three dots in the top right of the chat > Copy Request ID)
  • A screenshot of what Composer-1 shows right before you move to a new chat
  • Your exact Cursor version (Help > About)

Workaround: try running /summarize manually before the chat hits the limit.

1 Like
5

This is a massive phenomenon. I always use the latest version. The latest macOS + latest version is ALWAYS Cursor. There is only one scenario - summary is not being done, and suggests switching to a new chat, ostensibly from summary, but actually from scratch.
If the team is working on this problem, it will suit me, I will wait.

1 Like