Leverage the LSP / Intellisense of a connected IDE (VS Code / Visual Studio)

[pavidal-havok]

Describe the feature or problem you'd like to solve

Setting up local LSP server for Copilot CLI is unnecessary when a connected IDE can serve those operations

Proposed solution

Manually setting up an LSP server for Copilot CLI to use is non-trivial.

Suggestion: When Copilot CLI is connected to an IDE like VS Code or Visual Studio, LSP tools like go-to-definition, find-references, hover-info, etc could be forwarded to the IDE - leveraging the LSP and Intellisense functionality there.

Example prompts or workflows

• User opens Copilot CLI on a repository
• User open VS code on the same repository
• See: Agent operations on the repository leverage semantic understanding (via LSP/Intellisense) served by the IDE, rather than grep operations.

Additional context

No response

[ericnewton76]

with c# you can leverage rosyln-mcp-server, i'm sure theres lots of others mcp language servers.

this sounds like a complicated interaction thats tough to debug and maintain long term.