Hey, thanks for the detailed feature request. I can tell you’ve thought it through.
The direction makes sense. Instead of having the agent rebuild the project structure every time via grep plus embeddings plus file reads, give it access to what the language service LSP or Roslyn already knows in a deterministic way like find references, go to definition, call hierarchy, inheritance, symbols, and combine that with the semantic index into a single layer.
This is something we’re already discussing, and similar requests have come up in other threads:
- Bring LSP Support to Cursor CLI Bring LSP (Language Server Protocol) Support to Cursor CLI for Production-Grade Code Intelligence
- How are users handling context across different AI coding tools? How are people handling context across different AI coding tools?
- Graph-enabled RAG module Graph-enabled RAG module
I’ve logged your request and attached it to the right internal track. Your wording is especially helpful since it’s language agnostic, not just about TypeScript. I can’t share a timeline or make any promises, but there is interest in this.
If there’s an update, I’ll reply in the thread.