"Cmd+K Has Been Retired" from terminal?

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Integrated terminal is focused, I hit cmd+k to bring up the quick question box, type something like “recursively watch this directory for changes”, hit enter.

I expect it to generate the command for me and put it into my terminal like it has been. But I’m being shown a message box saying “Cmd+K Has Been Retired. Select code and press Cmd+L to add it to Agent.”

There’s no code for me to select. I’m not trying to edit or modify code. I use this all the time for having it generate shell commands for me.

Steps to Reproduce

  • open and focus the integrated terminal
  • cmd+k
  • describe what you want to do in the shell, e.g. recursively watch this directory for changes
  • press enter
  • see message box describing the wrong context

Expected Behavior

A shell command is generated and placed into the terminal waiting for me to hit enter.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

2026-10-23T21:46:59.851Z

Additional Information

This was working up until an hour ago. I thought I needed to update Cursor but it’s still no longer working.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @John_Adventive, this is expected. Cmd+K, including generating commands in the terminal, was retired today, so instead of a command you now get that message. Updating won’t bring it back. The “select code” wording is written for the editor, which is why it reads oddly in the terminal.

The closest replacement is Agent. Press Cmd+I, describe what you want (for example “recursively watch this directory for changes”), and it will write the command and can run it in a terminal for you. If you want it to work from something already in your terminal, select that output and press Cmd+L to add it to the chat first.

Ah, thanks for the quick response, but oh man…that’s sad. It’s currently much slower than Cmd+K i’m used to. I tried to speed it up a bit by adding to my AGENTS.md:

if i provide zsh context and ask for a command that does something, please just generate the command and put it back into the terminal. i don’t want or need any output in the agent window. prefer bash commands or whatever the current shell is.

It just feels much…heavier? Originally it returned commands in a second or less.

Haha, I wasn’t prepared for someone to come into my house and take my favorite hammer away from me today. “That hand-me-down hammer you inherited from your great great grandfather is garbage! Give it here!”

I’ll keep playing with it after work and see if I can better emulate the old behavior and speed.

this command is very important to me I used it all the time. to fix my writing very quickly and also to explain to me things very quickly. as using ctrl+k or ctrl+alt+k.
I did subscribe to cursor for only this. is there a way for this command to return

Any specific reason behind the adjustment? My workflow also relied heavily on its ux.

We need this feature back. Its critical for me

:frowning: this quick UI window which gives semi-manual workflow was a 40% of reason we’ve been is using Cursor in our team.

PLEASE BRING BACK Cmd+K

This is a vital feature please don’t remove it. Atleast give us the option of toggling it back on.

this is the very reason I still use and would continue to use cursor - otherwise only claude is fine.

Claude is smarter but BLACKBOX. Cursor CTRL+K was the only way I could still track and write codes…

Anyone knows the alternative? I heard copilot has similar feature

fully agreed this is one of the primary reasons I use cursor. may migrate over to copilot

This is the feature that i use everyday for and the main reason i still use the cursor as my IDE, i use ctrl+k for the quick terimal command making as well as quick ask summaries and or quick fill. Im super dissapointed now :frowning: .

Please bring this feature back to Cursor. The speed of the reply and the convenience of not having to get out of the terminal to work with commands was superb. This feels like a feature deprecation without a better alternative. VSCode keeps this feature alive, and for good reason.

Cursor is still the best AI editor I’ve used. It multiplies my output more than anything else, which is why I’m bothering to write this instead of quietly leaving (in the process lol). I’d also ask the team not to take this personally. It’s feedback from someone who wants to keep using the product, so you blocking my posts feels rather petty!

I picked Cursor over plain VS Code because I wanted fine-grained control and visibility into what the agent was doing, inside an editor I could take over at any moment. It did that better than anything else, so I switched.

Lately it feels like the product is being steered away from that. A while back it was the agent’s command output no longer opening in the real terminal pane (my earlier thread link). Then agent reasoning got harder to follow. Now Cmd+K is gone: inline edit, inline questions, and terminal command generation. The answer I’ve seen is basically “it’s retired, use Agent.”

I don’t buy that those are the same thing. Selecting ten lines, asking a question or making a quick edit, or getting a shell command in a second and running it myself doesn’t need an agent session. Agent is great for a multi-file refactor. It’s overkill for the small stuff, and it’s slower and hides more of what’s happening.

I get the business logic => Agent workflows burn more tokens and more tokens equals more revenue. I can’t know that’s why these calls were made, but when the lightweight, hands-on options keep getting removed and nobody explains why, people are going to wonder - I know I am. What was the reason? Low usage, maintenance cost, a conflict with Agent? And why couldn’t they just coexist? “It’s gone” tells us what happened, and we already know that.

The bigger thing for me is this. I think the future is AI plus human judgment, and that only works if the human can actually judge the output. A lot of the marketing, especially the influencer “I built this in an afternoon” demos, sells the opposite: you approve what you can’t evaluate. Those projects look great until someone asks about security, scale, or what happens when it breaks. I use agents heavily and they’re good. I just don’t want an editor that treats me watching as the goal. I’ve always switched back to editor mode because I want to be in the code.

If the direction is fully hands-off, I don’t see what separates Cursor from Claude Code or Codex. A VS Code fork was supposed to be the difference.

This is the first time I’m looking at alternatives. I want AI-assisted dev first, agents when I choose to hand something off. What I need:

  • A real editor, not an agent dashboard
  • Inline edit and Q&A on selected code
  • Natural-language terminal commands
  • Full visibility into what agents run and change
  • Easy manual override
  • Ideally, any model provider

I’ve looked at VS Code + Copilot, Windsurf, Continue and Zed, but I’d rather hear from people who use them daily. What would you pick? And can you make any suggestions? Colin responding to this doesn’t count! I’d rather you not respond with your boilerplate stuff!

  • I am so frustrated with Cursor that I have gone back to VS code. moreover, I might just drop my startup and start my own editing tool! And I speak highly of Cursor. If you want to create an agentic ai view (everyone is I know) do it. But you don’t have to sunset tooling that allows people who want more hands on control to get visibility into agentic workflows!

This is a very very big problem for me and all of my projects. I think there are plenty users who would like this feature to be brought back.

Also, for me, I think that it is a key feature

I hope you guys bring the feature back.

yeah man I really need it back
I love it
it was worst decision to remove it
I Loved how fast it was I dont like waiting for agents to spin up and eat 30k tokens for simple question
cmd +k was my most used tool of cursor
hate that U took it away
please bring it back

Oh! Please bring back this useful feature!!

whoah - bring it back. Or at least explain why it was retired. I only used it occasionally but found it great for small changes instead of using the heavy Agent flow, with a new tab cluttering things up