Inconsistent File Content Reading in Cursor Chat

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

There appears to be an inconsistency in Cursor Chat’s ability to read file contents during conversations:

  1. Initial file sharing in a conversation - Content can be read successfully
  2. Subsequent file sharing in the same conversation - Content cannot be read
  3. Requesting to re-read previously shared files - Content cannot be read
  4. When files are shared via @mention - Content cannot be read
  5. When entire files are copied directly - Content cannot be read
  6. When specific parts of files are copied - Content can be read successfully

This inconsistency:

  • Disrupts the natural flow of technical discussions
  • Forces users to manually copy specific sections instead of sharing entire files
  • Creates extra work for users who need to share code context
  • May lead to incomplete code reviews or missing important context
  • Makes it difficult to reference multiple files during a single conversation
  • Forces users to start new conversations to share additional files
  • Complicates code review processes that involve multiple files

Steps to Reproduce

  1. Start a new conversation and share a file - Content is readable
  2. Continue the conversation and share another file for a while - Content cannot be read
  3. Ask to review a previously shared file’s updated version - Content cannot be read

Try to:
1.Share a file using @mention syntax
2. Copy and paste an entire file
3. Copy and paste a specific section of the same file

Expected Behavior

Cursor Chat should maintain a consistent ability to read file contents throughout the conversation.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.2.0

Additional Information

This issue significantly impacts the user experience when discussing multiple files or requiring multiple reviews of the same file during a conversation. This issue doesn’t happen all the time. At some point during the conversation, Cursor can see the files mentioned, but after a certain point, it can no longer read the files.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

We have identified some issues with the AI’s ability to read files you at sometimes, but we are working on this behind the scenes at the moment, and we’ll hopefully have some improvements out in a future update!

1 Like

Thank you for the response. I hope this update will be released soon because this issue is frustratingly affecting the application’s performance.