Cmd + Enter doesn't work as expected on Mac

How To
1

Just activated my Trial version of Cursor and I wanted to test the Chat with the whole codebase, but I can’t figure out how can I activate this. I am using Mac M1 Pro with Sonoma.

In the top left onboarding section it says that with “CMD + Enter” it should open the chat with the whole codebase as a context but it just goes to a new line. Also this shortcut is listed on the website.

I can’t find anywhere in the menu options how to open this at all.

CMD+L works but that is just for the current file. Am I doing something wrong? It has default settings as it’s just installed.

Without this working this tool is unusable to me. Thanks!

6 Likes
2

could you share a video of what you see when you hit cmd-enter?

3

Just seconding this here – I’ve just installed Cursor too on a '20 Intel MacBook Pro 16" with default settings and am having the same issue. I installed Cursor (free) literally about an hour ago.

RE video (OP shout if this isn’t identical to you) – CMD+Enter is literally identical to just Enter/newline. Behaves as if there is no shortcut at all.

Thanks for looking into this and good luck resolving!

4

Hi, I have same problem on m2 air,.Accept Edits is bind to cmd enter but when i searched similar keybindings I got notebook and some inline text change that I deleted so Accept Edits is left but still same issue

5

Seeing the same with M1 Max Pro - tried changing the insert newline shortcut key binding to something else, and I’m still unable to get the chat w codebase functionality to pull up. This is disappointing as its the only functionality that I can see switching to Cursor will benefit me with. Hoping someone can point out how to solve this.

1 Like
6

From what I’ve used, Cmd+L brings up the chat. Ask your question, and you can either press Enter to submit, or Cmd+Enter to submit with Codebase as context.

7

@rishabhy this is what I see when I press command + enter command + return in cursor | Loom

8

Ah - cmd-enter only works in the chat. Can you try it from the chat input box? (hit cmd-L to bring chat up)

1 Like
9

Hi, yes I was going to say I’d already figured it out. But my account on this forum was frozen for a few days.

The onboarding instructions are a little unclear. Because it runs you through keyboard short cuts that work. Then it tells you to run cmd + enter without any indication that you need to be clicked in the chat. At least, that’s what I remember.

1 Like
10

This is one of the first things I’ve tried. I’ve opened the chat for a specific file, my cursor is focussed on the text input field (tried also just focussing it in the chat sidebar), I do cmd+Enter and nothing happens. It still has that same file context from which I opened it.

I can add more files to the context with ‘@’ but the whole codebase search doesn’t work.

11

I have the same problem. in the chat text field pressing keys command and return does not cause any action.

12

I noticed I had to add a bit of text and then hit CMD+return for this to work.
kind of makes sense that you first have to add prompts before scanning the whole project.

3 Likes
13

⌘ Enter on Mac still does not work (only creates a new line).
Do we have an update on this Cursor?

Alternatively, is there a work-around?

14

Command + enter still does nothing.

Pressing command + L to open chat, and anything attempted from there doesn’t allow chat with codebase. Command + enter, clicking in many different places and retrying, clicking on various parts of the ‘chat’ pane etc etc.

Please update this thread if it gets fixed or a workaround is created (like ability to chat with codebase via a button or menu option).

15

Just found the answer:

I had to add a bit of text and then hit CMD+return for this to work.

Thanks to @ stephanschulz

I expected command + enter to open a new pane just like command + L did. Until the ux is improved, simply adding a ‘chat with all of codebase’ button (and menu option) could let people download cursor and get going straight away, avoiding having to trawl through forums (important since ‘chat with codebase’ is literally the only reason I’m using cursor, since CoPilot does the other stuff just fine).

16

Adding text and CMD+Return does NOT work for me. Tried selecting and engaging post / pre comments etc.

Not much point renewing my monthly subscription is this does not work, as getting integration between files is impossible (e.g. use function x from another file - it has literally no idea what to do)

17

Oh wow, that really sucks. 100% agree on the urgency of fixing this. It’s cursor’s flagship feature (and frankly the only thing that differentiates it from Copilot).

The rest of the cursor setup process is very slick/easy. But no LLM wrapper should take more than 30 seconds to figure out how to submit a question to it.

18

Guys, hitting Cmd+Return from code editor opens a new line - you need to first hit Cmd+L to enter chat, and than hitting Cmd+Return to make your question on a global context. The cursor guide is not very clear about this but this is essentially the feature

1 Like