On a Mac running Sequoia the Version: 1.6.45 has lost the copy (twin square icon) and apply (triangle arrow with name of currently in focus editing tab) decorations in the ASK mode.
This makes careful use of the ask mode much more difficult
Steps to Reproduce
Open a folder containing code
Enter ask mode (auto or selected model makes no difference)
Ask a question about existing code that will suggest a code change
Observe the code change
Expected Behavior
In “observe the code change” with the existing code highlighted in the edit pane, observe the suggested change:
See the copy icon (twin staggered squares)
See the apply icon (horizontal triangle) with wording “Apply to [open filename]”
Hey, thanks for the report! This looks like a bug, the Copy and Apply buttons should appear in Ask mode for code suggestions. The fact that they sometimes show in older asks but disappear in newer ones confirms it, though I can’t repro it on my side.
It’s likely related to recent changes in how Ask mode renders code suggestions. Since you’re on the latest version and both of you see the issue, I recommend:
Fully restart Cursor
If that doesn’t help, wait for the next update, as this appears to be a UI rendering bug that needs a fix
If I drag and drop a file with more than ~95 lines, the apply/copy buttons disappear. If i click on context in the chat and manually add the context files to ask questions to it, the apply/copy options are available. It seems to be tied to the context length when dragging files into the chat
My temporary fix is to downgrade to 1.5.5, at least the apply/copy buttons are available and working there
In the very latest version, Version: 1.7.39 I’m seeing a new “Plan” mode feature. The feature may at least partially ease the issue … it looks like you can, after arriving closure in an Ask chat, switch to Plan, and see a generated markdown plan of what will be changed and where, to the file and method level. That, at least, gives some advance warning of what might happen in advance of file changes. Then it’s possible to apply the plan with a new “Build” control in the markdown preview.
First impressions of the new “Plan” mode for more careful updates is very positive. The initial workflow I’m trying looks like:
ASK: generally resolve issues with a back and forth. Try to avoid code generation unless illustrative. Once we’re resolved on a course of action:
PLAN: request a detailed plan. This will result in a markdown document that seems to do a pretty good job of summarizing the actions to be taken, the files that will be changed, and often the functions or methods that will be modified. The prompt is still active, and there is a new [Build] control at the top of the markdown
If the plan appears satisfactory, click the [Build] control. This will switch to the AGENT mode and execute the plan. Review remains available, as with past versions
If the plan seems unsatisfactory, go back to the chat context in PLAN mode and request modifications until satisfactory
Gotchas: When [Build] is activated, Cursor exits the PLAN mode and enters AGENT mode. It’s easy to accidentally forget that the mode has shifted and inadvertently execute by AGENT what you really meant to be added to the PLAN for review.
Also, if in PLAN mode you’re asked “Should I implement”, this will trigger a change to AGENT mode, which is fine, but then it’s easy to forget the mode has changed. It’s probably better to use the [Build] control unless you have really good situational awareness
Overall though, this is pretty good for avoiding catastrophes
