The answer to the question after cursor chat context summarized is so disordered that it is completely out of context

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The answer to the question after cursor chat context summarized is so disordered that it is completely out of context

Steps to Reproduce

opus4.6 performs a large task. When the token consumption reaches the context threshold, it triggers summarized

Operating System

MacOS

Version Information

Version: 2.6.14 (Universal)
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z (1 天前)
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Opus 4.6 Max

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known issue. Context summarization can miss important details and cause the AI to go off track, especially in long chats with big context windows.

A couple of things that might help:

  • Start a new chat more often, before the context window fills up and summarization kicks in. You can use @ references to quickly pull in the right files for the new chat.
  • Use a .cursorrules file or a project rules file with key instructions. This helps the AI keep critical context even after summarization.

To help us look into your case, could you share the Request ID? You can get it from the chat context menu in the top right, then Copy Request ID. If you can, grab it from the message where the response went off track.

The team is aware of summarization quality issues. Your report helps increase visibility, especially for Team plan users.

The problem occurred after only two conversations in a single session. This is the request ID 897cc4dc-cb9e-4979-9548-7e2cc48fbfc7

My colleague has encountered new meetings and the first conversation. This is his request ID: 03bf5162-a3ba-4564-8dc8-ff76609f4a02

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.