Expose LSP Find All References to the Agent

Ideas Feature Requests
,
1

Feature request for product/service

Cursor IDE

Describe the request

The Agent already consumes LSP diagnostics (the same store as the Problems panel). It does not get other language-server results that the IDE already computes.

In the C# extension, CodeLens shows “1 reference” on a method. Clicking it opens Peek References (LSP textDocument/references) with the call sites plus the definition. That is the same graph a human uses to judge blast radius and which tests to run.

The Agent cannot query that. It approximates with text search (grep on the identifier). That misses interface/base-class call sites, overloads, and generated code, and it over-matches comments and unrelated types. For a private method like ParseExtensions that is cheap; for Parse / Read / a public interface member it is slow and wrong.

Ask: give the Agent a first-party tool that calls the workspace language server, starting with:

  1. Find all references — input: file path + line/column (or fully qualified name); output: the same location list Peek References shows
  2. Later: go to definition / go to implementation
  3. Later: rename symbol (workspace edit), instead of rewriting files by string replace

Diagnostics already flow to the Agent. References are the next high-value slice of the same protocol. This would speed test selection, refactors, and “what calls this?” questions without standing up a second compiler workspace.

Related existing request: Support of LSP (Language Server Protocol)

Operating System (if it applies)

Windows 10/11

5

Hi @LarrySmithIDIC, thanks for the suggestion!

This isn’t on our short-term roadmap, but in the meantime you may want to explore tools that integrate with Cursor, such as the Serena MCP server.