Feature Request: Expose “Problems” as Available Context for LLM
Summary:
Enable the “Problems” panel (e.g., diagnostics and linter outputs from extensions like ruff) to be used as part of the context available to the LLM during code completion, refactoring, and other interactions.
Motivation:
This feature already exists in VSCode Copilot, where the LLM can read problems detected by linters, type checkers, and other tools. It greatly enhances the relevance and precision of LLM suggestions by allowing it to prioritize fixing known issues and aligning with the project’s coding standards.
Use Case:
For example, if ruff reports an unused import or incorrect formatting, the LLM can proactively address it in its suggestions. This creates a smoother developer experience by:
- Reducing manual error fixing
- Keeping suggestions aligned with linting rules
- Improving overall code quality
Here’s how it looks in VSCode Co-Pilot -
Thanks for considering this!