Chat responds to previous questions (cumulative prompt)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the Chat, the AI has started to respond to previous questions inside every new response. Instead of just answering the latest prompt, it answers to previous questions and the new one, making the output increasingly long and difficult to read.

Steps to Reproduce

  1. Open the Chat.

  2. Ask a first question (e.g., “How do I center a div?”).

  3. Cursor provides Answer 1.

  4. Ask a second, related or unrelated question (e.g., “How do I change its color?”).

  5. Cursor responds with an answer for Question 1 and Question 2 (new one, not copy paste of the previous response).

  6. Ask a third question.

  7. Cursor responds with an answer to Question 1 + Question 2 + Question 3.

Expected Behavior

The AI should only provide the answer to the current prompt.

Screenshots / Screen Recordings

Screenshot 2026-02-13 at 3.26.12 PM.png
Screenshot 2026-02-13 at 3.26.12 PM.png644×170 10.5 KB

Operating System

MacOS

Version Information

Version: 2.4.35
VSCode Version: 1.105.1
Commit: d2bf8ec12017b1049f304ad3a5c8867b117ed830
Date: 2026-02-10T02:46:56.793Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.3.0

For AI issues: which model did you use?

Opus 4.6

Additional Information

The screenshot is after asking Question 3 only

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the report and the clear repro steps.

A couple things to check:

  1. Does this happen with other models too (like Sonnet 4.5 or GPT-5.2), or only with Opus 4.6?
  2. Does starting a brand new chat help, or does it happen from the very first follow-up question in a fresh chat?
  3. Can you grab the Request ID from one of the affected chats? (Click the three-dot menu in the top right of the chat and choose “Copy Request ID”.)

As a quick workaround, try starting a new chat for now and see if the issue still happens. If it only happens in existing or long threads, that helps narrow it down.

The Request ID will help the team figure out what’s going on with the conversation context on the backend.