I can no longer add context from another chat to the new chat

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Previously, we could add contacts from other chats to new or ongoing chats. My cursor no longer allows this when typing @, and chats no longer appear in the options list. This feature has been removed.

My chats reach 93% usage and then do nothing else after that.

Steps to Reproduce

start a new chat

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.42 (user setup)
VSCode Version: 1.105.1
Commit: 2e353c5f5b30150ff7b874dee5a87660693d9de0
Date: 2025-12-01T02:18:26.377Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey there!

I think you’re looking for @Past Chats

1 Like

That option doesn’t appear for me. :frowning: @Colin

Make sure you’re using 2.2. :slight_smile:

but this actions was removed on before version? And its always with

image

I see the Past chat as an option for to add context, but when I click it it writes " No option available.
In the same case, you can export the old chat that you want to add as context, and then add the exported chat file to the new chat prompt that is opened.
It works in the same way as adding the chat as context.

1 Like

Not the best UX, but try typing something and see if any chats show up.

(on my nightly build, this is much more stable)

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

No available options in past chats

Steps to Reproduce

input @ in chatbox

Screenshots / Screen Recordings

20251217093805.jpg

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (Universal)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

I’m seeing the same issue!

https://forum.cursor.com/t/unable-to-link-past-chats-to-new-chat/146834/2

same, can’t see past chats

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Description

Not sure if dupe, But this feature seems to be broken. Past chats dont show up in dropdown. Drag drop to context window also doesnt work.

Its pretty annoying as I’m forced to stay on thread or completely lose context between them. A hacky bypass is to get one to export an MD and then pull it into the new chat. But this is time consuming, pollutes the filespace and potentially wastes tokens

Steps to Reproduce

Try to referencer a previous chat in a agent chat thread. Previous chats dont show up in agent reference dropdown. Drag drop to context window also doesnt work.

Expected Behavior

It should link a previous chat to context.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.36 (Universal)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z (22 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.3.0

For AI issues: which model did you use?

Not relevant, but Opus 4.5

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Yep, I dont seem to be the only one:

Thanks, everyone. The team is aware of the issue and is working on a fix. It will take a little bit of time.

@lipecss You marked this as solved – does that mean it’s working well for you now?

Hi,The issue still persists.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cannot reference past chat as context for agent

Steps to Reproduce

press @ in agent and dont see an option for past chats.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.29
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

I’m still experiencing this issue. Any update as to when we can expect to see a solution rolled out?

Sorry that I can’t be more precise than “soon”!