Context commands are broken

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Context is getting worse and worse. Previously only a few were broken but now nearly all useful @ commands are broken.

  • Docs
  • Git
  • Past chats
  • Terminals
  • Active tabs

The commands do not give the model any meaningful context. Instead the model seems clueless and starts searching files for information that should be available through the context reference.

Steps to Reproduce

Try asking questions about various types of @ context

Expected Behavior

The model should reply as though it is highly informed about the information in the context.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.17
VSCode Version: 1.99.3
Commit: 34881053400013f38e2354f1479c88c9067039a0
Date: 2025-09-29T03:10:26.099Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.14.0-32-generic

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like

hi @mkschreder which model did you use here and could you post a Request ID with privacy disabled so we can look into the details?

For example: a43a00b5-7f54-4c91-a3c1-5a206efcefd6

”What is the correct way to implement mcp server according to @FastMCP”

FastMCP is docs reference. Instead of searching pages in that doc reference, cursor searches files in the repository and completely goes off track because it doesn’t use the doc reference. This was working before.

1 Like

MCPs do not have @ tag. Very curious that it was working

It’s not MCP. The tag points to FastMCP docs. It should result in a semantic search through docs pages but it doesn’t do that anymore. It was working fine before. Don’t know when it broken but probably some time around 1.5.

1 Like

Hey, yes, there are issues with the docs at the moment. The team is working on a fix.

1 Like

In addition to these issues with the @ commands themselves, there are issues with the popup panel that appears when you are searching for context, either an @ command, or a file, etc. The sorting/ordering of that panel, is often very strange. The most common case, I will type a filename or directory name, and initially it will show up at teh top of the list, but by the time I hit enter, another, different file/directory has taken its place, and the wrong thing inserts into the prompt. If I delete it, and go back and try again, I can see the EXACT piece of context I want, show up at teh top of the list, for a moment, and half a second to a second later something else supplants it at the top. The timing delay there, and the oddity of the CORRECT item showing at the top, then being replaced by something else that is wrong, creates a very disconcerting experience.

Usually, the thing that supplants the correct item, is something with a LONGER NAME. I don’t know why it sorts/ranks that way, but that is very frequently wrong. It should be the opposite…the higher ranking should be the shorter-named matching items, not the longer, until you type enough to make it very clear that shorter names are not what the user is looking for. I will often look for simple directories, say @prisma/ or @schema.prisma, and they are right there the top, but by the time I hit enter, something else has replaced them, like @prisma-readme.md… Why the longer name replaces the directory I WANTED to attach, and just within a fraction of a second delay, right as I’m trying to select the item I really wanted…well, its….immensely frustrating. :stuck_out_tongue:

1 Like

Attaching files is also not ideal: Agent sees @file in the promt instead of the relative file path and wonders what the hell this is. This can sometimes be seen in his thoughts.

Any update on this issue? Seems commands are still not functioning. Would be nice to get @Docs back, and also some improvements in the context popup. Its often quite difficult to tell which piece of context you should choose as the relevant information is often truncated or cut off.

3 Likes

When i type @ in chat the option for docs not even appearing :frowning:

I have always had to type @D or even @Doc to get it to show. There are SEVERE limitations in the context popup in the prompt editor right now. It is in desperate need of some serious TLC, as it is rapidly becoming one of the most frustrating features of Cursor.

@condor Just checking up on the status here. Now that the terminal integration with the agent finally seems to be fixed, which had a tremendous impact on my velocity the last…well heck, its been a couple months I think… I am now starting to really feel the pain of not having all the context commands I was used to. @Docs in particular, @git often enough, I seem to have forgot how often I used past chats and active tabs (it apparently became second nature, but I’m also now realizing they don’t seem to work either.)

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