Referencing files stops the agent from running

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Every time I reference the file by using the add symbol and referencing it, or just after I drag and drop any kind of file, this can be the actual code or it can be a markdown file with a feature description. Regardless, the agent gets stuck in infinite planning next move / it takes longer than expected mode. If I remove direct mention of the file and instead just reference its name, the agent works as expected.

So, for example, when I say : “Build feature described in the @feature” The agent won’t move. But if I say “Build feature described in the feature document,” it will

Steps to Reproduce

Mention any file from your directory in the agent chat input and try to make the agent work with it.

Operating System

MacOS

Version Information

Version: 3.0.4 (Universal)
VSCode Version: 1.105.1
Commit:
Date: 2026-04-02T09:36:23.265Z (3 days ago)
Layout: editor
Build Type: Stable
Release Track: Early Access
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

This is a known issue the team is actively working on. The “planning next moves” / “taking longer than expected” hang when referencing files has been reported by several users.

I also noticed you posted about the same hang in plan mode — these are likely the same underlying issue, so I’ll track both here.

A few things to try:

  1. Re-index your project: Cursor Settings (not VS Code settings) > Indexing > Resync Index. This has resolved similar hangs for some users.

  2. Test with an empty folder: File > Open Folder > pick an empty directory, start a new chat, reference a file with @. If it works there, the issue may be tied to your project’s index.

  3. Disable HTTP/2: Cursor Settings > search “HTTP/2” > enable “Disable HTTP/2”, then fully quit and reopen Cursor.

Also, next time it gets stuck, could you grab a Request ID? Click the three dots at the top right of the chat > Copy Request ID. That helps us trace exactly what’s happening on the backend.

Related thread with the same trigger: Infinite loading when adding file references in chat