Thank you for the reply. I’ll give that a try. But this also doesn’t address the core issue, where you can attach the files to a prompt and Cursor makes it appear that the LLM is receiving that code for the prompt. But its very clear when you interrogate the LLM its either ignoring the attached file, or truncating it so its completely useless, or instead reverting to a cached version.
As best as I can tell it appears that Cursor is aggressively caching code, making the ability to attach the most recent file useless. Having to go in and re-index the codebase during a coding session is not practical.
It removes the agency of the developer to guide the LLM and cursor does not provide any visibility into how the LLM is making its decision.
Given the nature of LLMs to lie and produce false claims- Claude repeatedly claims it analyzes code and has found the issue - this lack of transparency by Cursor is the true productivity killer.