# Quick edit doesn't work in Start plan

**URL:** <https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963>\
**Category:** Bug Reports\
**Tags:** inline-edit, auto-mode\
**Created:** [July 29, 2026, 11:34am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963 "2026-07-29T11:34:45Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![disastrous\_crocodile](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@disastrous\_crocodile](https://forum.cursor.com/u/disastrous_crocodile)\
**Post date:** [July 29, 2026, 11:34am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/1 "2026-07-29T11:34:45Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

The quick edit feature does not seem to work in the new Start plan. It gives the error:

```auto
Model unavailable on start
Start includes Composer 2.5 and Cursor Grok 4.5 with fixed settings. Switch to an included model to continue.

```

I think it is because quick edit is set to “auto” mode by default, which seems to mess with this plan. Don’t know if this is part of a feature that is not included in this plan or a bug.

Thanks!

### Steps to Reproduce

1. Open a file in the Cursor IDE
2. Press Ctrl+K (or whatever the shortcut is for the quick edit window)
3. Prompt

### Expected Behavior

The quick edit window should be calling an available model (either grok4.5 or composer2.5) and edit the code.

### Screenshots / Screen Recordings

 ![Screenshot 2026-07-29 170338.png](https://us1.discourse-cdn.com/cursor1/original/3X/a/9/a9ecf01ffe9199cdf1e4520801c68c761825ae50.png)

### Operating System

Windows 10/11

### Version Information

Version: 3.13.25 (user setup)  
VS Code Extension API: 1.128.0  
Commit: 31e8d61c448c7472e371505838a0fe34083dad50  
Date: 2026-07-28T06:17:45.069Z  
Layout: IDE  
Build Type: Stable  
Release Track: Default  
Electron: 40.10.3  
Chromium: 144.0.7559.236  
Node.js: 24.15.0  
V8: 14.4.258.32-electron.0  
xterm.js: 6.1.0-beta.256  
OS: Windows\_NT x64 10.0.26200

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [July 29, 2026, 11:57am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/5 "2026-07-29T11:57:27Z")

</div>

Hey, thanks for the detailed report. This is a real gap on our side, not something with your account.

On the Start plan, the models are fixed (Composer 2.5 and Cursor Grok 4.5 with fixed settings). Auto is intentionally not included in the plan. The problem is that Quick Edit `Cmd+K` currently defaults to Auto and hits the block, and the Switch to Composer button doesn’t help here. So Quick Edit on this plan ends up with no model it can use. I’ve reported this internally as a bug.

As a workaround for now, use Agent chat `Ctrl+L` or `Ctrl+I` with the models included in your plan. Edits work fine there.

I can’t share an ETA for a fix yet. Once I have an update, I’ll reply in the thread.

---

<div class="post-metadata">

**Author:** ![imlolman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/imlolman/32/84977_2.png) [@imlolman](https://forum.cursor.com/u/imlolman)\
**Post date:** [July 31, 2026, 4:22am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/7 "2026-07-31T04:22:52Z")

</div>

> [@deanrie](#):
>
> the Start plan, the

Thanks, hopefully team fix this fast. I’ve bought this plan just for this, I was using claude code for now and i am still using it, just for quick edits, claude take lots of time hence bought this plan. ☹

---

<div class="post-metadata">

**Author:** ![imlolman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/imlolman/32/84977_2.png) [@imlolman](https://forum.cursor.com/u/imlolman)\
**Post date:** [August 3, 2026, 5:28am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/8 "2026-08-03T05:28:29Z")

</div>

Hey, I understand you can’t give any eta for this however, don’t you think the plan is useless because of this since most people using this plan want quick edits ?

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [August 3, 2026, 5:58am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/9 "2026-08-03T05:58:27Z")

</div>

Hey, thanks for getting back to me. Totally get it, it’s frustrating. You got the plan mainly for quick edits, and that’s the one thing that isn’t working.

Until it’s fixed, you can do edits via Agent chat with `Ctrl+L` or `Ctrl+I` using the models included in your plan Composer 2.5 and Cursor Grok 4.5. That works normally. It’s not a full replacement for `Cmd+K`, but it should cover most use cases without switching to another tool.

We’re tracking the issue, but I can’t share an ETA yet. As soon as I have an update, I’ll reply right here in the thread.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 5, 2026, 7:57pm UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/11 "2026-10-05T19:57:29Z")

</div>

Hey @disastrous_crocodile, I’m back with an update.

We’ve fixed Quick Edit, `Ctrl+K`, on the Start plan since your report. Requests that previously failed with “Model unavailable on start” should now work with Composer 2.5. You don’t need to update Cursor. This was a server-side change.

Could you give it a quick try?

1. Open a file in Cursor.
2. Press `Ctrl+K`.
3. Enter a prompt and submit it.

Let me know if you still see the “Model unavailable” error.

cc @imlolman

---

<div class="post-metadata">

**Author:** ![disastrous\_crocodile](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@disastrous\_crocodile](https://forum.cursor.com/u/disastrous_crocodile)\
**Post date:** [October 6, 2026, 4:29am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/12 "2026-10-06T04:29:47Z")

</div>

Hey @deanrie, thanks for looking into this and fixing it.

Unfortunately, I won’t be able to validate it now since I upgraded to the Pro plan. However, I remember that during my last days on the Starter plan, I was able to use Quick Edit. Although that was about a month ago, so I’m not sure whether the fix was already in place at that time.

The only thing I noticed was that when I used Quick Edit to ask a quick question (Alt + Enter), the response was added as an inline comment rather than appearing in the Quick Edit window. I remember the response appearing in the Quick Edit window when I first started using Cursor about a year ago. I’m not sure whether this is an intentional change or a bug.

Edit: I tried the /explain (alt + enter on quick edit) feature on my Pro plan just now. Same problem (or not a problem, depending on whether this is a feature or a bug), the explanation is added as inline comment(s).

My current Cursor version info:

Version: 3.23.23 (user setup)  
VS Code Extension API: 1.128.0  
Commit: 2dac2428994fe34f12658d9ecad1541b98db2c00  
Date: 2026-10-05T01:43:43.807Z  
Layout: IDE  
Build Type: Stable  
Release Track: Default  
Electron: 42.10.0  
Chromium: 148.0.7778.280  
Node.js: 24.18.1  
V8: 14.8.178.38-electron.0  
xterm.js: 6.1.0-beta.291  
OS: Windows\_NT x64 10.0.26300

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 6, 2026, 11:41am UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/13 "2026-10-06T11:41:05Z")

</div>

Hey, I’m glad Quick Edit is working on the Start plan now. Thanks for the update.

About the second issue, where the answer to `Alt+Enter` or `/explain` appears as an inline comment instead of in the Quick Edit window, I’m not sure yet if that change is intended. I’d like to take a closer look.

Could you start a separate thread for this quick question behavior? That’ll make it easier to track without it getting lost in the resolved Start plan thread. If you can, please include:

- A short screen recording showing you open a file, press `Ctrl+K`, ask a question with `Alt+Enter`, and show where the answer appears
- Your Cursor version, which looks like 3.23.23, and your OS

Let me know when you’ve created the thread, or if you need help with the steps.

---

<div class="post-metadata">

**Author:** ![disastrous\_crocodile](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@disastrous\_crocodile](https://forum.cursor.com/u/disastrous_crocodile)\
**Post date:** [October 7, 2026, 4:28pm UTC](https://forum.cursor.com/t/quick-edit-doesnt-work-in-start-plan/166963/14 "2026-10-07T16:28:42Z")

</div>

Sure. Here you go: [Quick Edit (Ctrl+K) question via /explain returns answer as inline comments instead of in the Quick Edit window](https://forum.cursor.com/t/quick-edit-ctrl-k-question-via-explain-returns-answer-as-inline-comments-instead-of-in-the-quick-edit-window/173998)
