Can't select model in Quick Edit

Recently, I discovered that after upgrading Cursor, I can no longer select models in Quick Edit.

I checked the forums and found some links indicating that Cursor apparently no longer plans to provide this feature.

I have been a power user to use the QuickEdit, which is a very useful tool for students to edit note and scripts in Jupyter Notebooks (.ipynb),

In previous versions of Cursor, the QuickEdit feature allowed for model selection, which was extremely useful. However, without any prior notice, Cursor unilaterally modified its functionality and no longer allow user to select model.

I find this unprofessional behavior deeply embarrassing. People have already paid the subscription fee for the feature they need, yet the product has been compromised.

Overall, I feel this is an extremely poor experience.

1 Like

Hey, thanks for the feedback. I get that this change is annoying, especially if you’re used to a specific workflow.

This was an intentional decision. Quick Edit Cmd+K now works only with Auto. The reason is that Quick Edit has major model compatibility limits. It doesn’t support thinking models, Anthropic 4.6+, and others. Also, most requests were already going through Auto.

If you need a specific model, Agent chat supports the full model picker and also works with Jupyter Notebooks.

Thank you for your response, but the suggested workaround is completely inadequate. The ‘Auto’ model is not working as expected, and Cmd + L simply does not replace the efficiency of editing a selected cell like Quick Edit did. This is immediately obvious if you actually test it — This is not something you can just assume.

I understand that Quick Edit has compatibility limits with ‘thinking’ models, But my point is that the previous Anthropic 4.5 (without thinking) models functioned perfectly within Quick Edit. Users were perfectly fine with that limitation; no one was complaining about it.

The core issue here is that Cursor decided to completely eliminate a highly utilized feature that people actually rely on, simply to ‘fix’ a compatibility limitation that no user cared about. This is a massive step backward for the user experience.

I hope you will truly take a moment to consider whether you actually care about your customers.

2 Likes

Just FYI, this feature was the only thing keeping me from switching away from Cursor.

In VS Code, this feature feels weak, while in Cursor it was great and fast. Even though I was frustrated by the lack of reasoning models there, Sonnet 4 was still enough to keep me happy.

Now that this is gone, I won’t continue with my Cursor subscription. I think a lot of other people may feel the same way.

Please reconsider this decision and add support for thinking models.

1 Like

@geduardo 100% this. I’m right there with you.

It’s honestly mind-blowing how the Cursor team is just brushing off actual user feedback. They’re literally killing the one killer feature that made Cursor better than VS Code for us. And their excuse about “model compatibility”? Come on. We were totally fine just using the older models for Quick Edit, nobody was complaining about that! Telling us to “just use Cmd+L” proves they have zero clue how we actually use this tool day-to-day.

I’ve been a loyal subscriber for over a year now—paying every single month for well over a dozen months straight. But this whole “we know best” attitude and nuking a core feature out of nowhere is the final straw for me.

I’m canceling my sub too. It really sucks that it’s come to this, but I guess hitting them in the wallet is the only way they’ll actually listen.