Cursor unable to access Docs

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor appears to be unable to retrieve custom docs. The issue first occurred in Plan mode, but now affects Agent mode as well.
The Docs are registered correctly in the Cursor Settings tab, but the chat transcript shows that Cursor can’t access them, and either runs a web search instead, or sometimes asks me whether I can provide access.

Steps to Reproduce

  1. Set up a custom Doc
  2. Reference it in a Plan

Expected Behavior

I expect Cursor to be able to access the contents of the Doc.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (user setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
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.26100

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

ac4a0d26-8faf-47bb-902b-4fc31d5ebe15

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report.

Could you please share:

  1. A screenshot from Cursor Settings > Indexing & Docs showing the custom doc status (is it fully indexed?)
  2. The URL of the custom documentation you added
  3. A screenshot of the chat showing the error/behavior when referencing the doc
  4. Does this happen with built-in docs too? (e.g., try @Docs and select React or another popular framework)

Also, try removing and re-adding the custom doc to trigger a fresh index.

3

Hi Dean Rie, thanks for this. Please see below:

image
image1421×1038 112 KB

Links to documentation:

Ardoq Batch API Aliases

Ardoq Batch API Examples

I don’t think indexing is the issue, as this issue occurs inconsistently

Request ID 08221d2e-7595-4d01-baf3-7eeed3a7ec96

Thanks

4

The above Request ID was demonstrating the issue in Plan mode using Sonnet 4.5.

Request ID d9e215f1-2981-4e73-a648-79537fe359d8 demonstrates the issue in Agent mode using GPT 5.1.

image
image638×604 34.1 KB

You can’t see the full prompt on this screenshot, but it was the same as the one above. Both Docs were tagged, but the model says “I can’t access it”.

5

I cleared my Workspace Storage %APPDATA%\Cursor\User\workspaceStorage and the issue persists.

image
image593×538 25.6 KB

Request ID c5f481d7-68a3-4081-b7c2-2e4930525eea