# Expose “Problems” as Available Context for LLM

**URL:** <https://forum.cursor.com/t/expose-problems-as-available-context-for-llm/107827>\
**Category:** Feature Requests\
**Created:** [June 23, 2025, 5:48am UTC](https://forum.cursor.com/t/expose-problems-as-available-context-for-llm/107827 "2025-06-23T05:48:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ido\_Greenfeld](https://avatars.discourse-cdn.com/v4/letter/i/ed8c4c/32.png) [@Ido\_Greenfeld](https://forum.cursor.com/u/Ido_Greenfeld)\
**Post date:** [June 23, 2025, 5:48am UTC](https://forum.cursor.com/t/expose-problems-as-available-context-for-llm/107827/1 "2025-06-23T05:48:51Z")

</div>

**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 -

 ![problems_tab](https://us1.discourse-cdn.com/cursor1/original/3X/2/b/2b8b760d8e0327ea69113fd5e79a1d8982e5dd37.png)

Thanks for considering this!

---

<div class="post-metadata">

**Author:** ![honeypot](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/honeypot/32/70564_2.png) [@honeypot](https://forum.cursor.com/u/honeypot)\
**Post date:** [July 14, 2025, 12:01pm UTC](https://forum.cursor.com/t/expose-problems-as-available-context-for-llm/107827/2 "2025-07-14T12:01:01Z")

</div>

yes please, some LSP linting errors show up in the _Problems_ tab but are not picked up by Cursor, for me this should be such a basic functionality that I consider this a bug
