No way to modify incorrect prefix for indexed Docs

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When another user has added a documentation page for indexing, e.g. https://pydantic.dev/docs/ai/overview/, using an incorrect prefix, e.g. https://pydantic.dev/docs/ai/overview/ instead of the proper prefix of https://pydantic.dev/docs/ai/, there is no way to edit the prefix. The documentation for Pydantic AI is now permanently stuck, for all Cursor users, with the wrong prefix, meaning it only crawls a small portion of the pages and is now useless.

Steps to Reproduce

  • Add https://pydantic.dev/docs/ai/overview/ to the Docs indexing
  • Set https://pydantic.dev/docs/ai/ as the prefix
  • The doc is matched to the existing entry in the system, which hsa the incorrect https://pydantic.dev/docs/ai/overview/ prefix. There is no way to fix this.

Expected Behavior

We can somehow fix the incorrect prefix for the doc.

Operating System

MacOS

Version Information

Version: 3.6.31
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hi Josh, thanks for the detailed write-up. Indexed docs are shared and de-duplicated across all users, and right now there’s no way to edit an existing entry’s crawl prefix once it’s been indexed. Re-adding the same URL just attaches you to the existing entry, so the narrow prefix sticks. This is a real limitation on our side, not something you’re doing wrong, and I’ve passed it to the team.

In the meantime, you can work around it by indexing the docs under a different entry URL so it creates a fresh entry instead of matching the broken one. For Pydantic AI, the canonical docs live at https://ai.pydantic.dev/ - adding that as the entry point (with https://ai.pydantic.dev/ as the prefix) should index the full set as a new, correctly-scoped entry rather than colliding with the stuck pydantic.dev/docs/ai/overview/ one.

If that new entry indexes cleanly for you, just @ it as usual. Let me know how it goes.