Describe the Bug
When using “Ask” mode, the prompt needs to instruct whichever LLM is being called that it does not have editing tools enabled. Without this the LLM can get stuck in an infinite loop of trying to edit a file, realizing it cannot edit the file, and then trying again and again burning through usage. If it does realize it cannot edit files, it may change its suggested code revisions thinking that trying a different approach will somehow magically allow it to edit the file i.e., it confuses not having editing tools enabled with not being able to pursue a particular code revision strategy, which makes no sense.
To prevent this I have to manually add this to the end of my prompts:
“Let’s align on your understanding – keep in mind that your editing tools are disabled.” Why not just tell the LLM it does not have the ability to edit files if it’s in “Ask” mode?
Steps to Reproduce
Just use “Ask” mode a few times and eventually you will get unlucky and experience this bug.
Expected Behavior
The LLM should know it cannot edit files if the user is using “Ask” mode – seems like that should be a given?
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.2 (Universal)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:07:27.002Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin x64 23.5.0
Does this stop you from using Cursor
Yes - Cursor is unusable