Chat not opening since 0.47.5 update

:lady_beetle: Provide a clear description of the bug

Since updating to 0.47.5, I have not been able to open the chat with cmd + L or cmd + shift+ L.

I’ve also tried using cmd + shift + P to open the chat there too, but still nothing.

There’s no indication off anything happening either, kind of feels like that whole functionality has been removed.

:counterclockwise_arrows_button: Explain how to reproduce the bug (if known)

Update to 0.47.5 and try opening a chat.

:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).

:laptop: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Macbook Pro M1 - OS 15.3.1

:prohibited: Tell us if the issue stops you from using Cursor.
Yes - its the only feature I use. It looks like cmd + K still works, but thats not what I am using Cursor for.

13 Likes

I also have this situation now

2 Likes

me too!!!

ver: 0.47.5 (user setup)
submit: 1.96.2
date: 53d6da1322f934a1058e7569ee0847b24879d180
Electron: 2025-03-14T21:53:57.982Z
ElectronBuildId: 32.2.6
Chromium: undefined
Node.js: 128.0.6613.186
V8: 20.18.1
OS: 12.8.374.38-electron.0

I don’t have this problem anymore
I don’t seem to have done anything

1 Like

Update: I have tried going into keyboard shortcuts to try to rebind to make sure it wasn’t a keybind clash, but alas still not working.

I have decided to revert back to 0.46 for now and it is working again. If you are still having troubles, go to Downloads | Cursor - The AI Code Editor and pick an earlier version.

me two, i just reported this didnt see your topic. i hope this fixed soon

Having the same issue. Have had to revert back to 0.46 to “fix” this for now.

1 Like

i cant …

there are more topics with similar problem and developers are silent ;))))

I’m using a Mac. I don’t know if it’s related to this. My current 0.47 version can already be used normally

I am also using Mac, but the latest update does not fix the issue for me. I cannot use cursor.

You need to downgrade :wink:
Im on 0.46.11 and everything works fine like before … last update was really strange and dev team are silent .. why?

Same here! I have another friend having the same issue, but yeah, not all of us have it :x Autocomplete works but that’s about it.

Please have a look at following solutions that will likely work for your case.

2 Likes

I believe this was intentional, as cmd + shift + L is already a VS Code keybind to select all occurrences of the currently selected text

This was something I was hoping they would fix, as I use that command all the time in VS Code but cursor broke the functionality due to it opening the chat without being able to unbind it

Ctrl + l dont seem to open cursor tab and chat anymore after update for me aswell. It is very annoying since i just got everything working after a very long time cursor being broken for me.

i think i’m having the same issue, but not sure. it’s only for certain workspaces that i’m in a never-ending “loading chat” loop

any idea how to delete the cursor chat history for this workspace to start fresh?

I had the same problem, so I uninstalled, re-installed 0.46 to test to make sure everything worked still, and since it was fine, I made sure to change to Beta to “Standard” instead of “Early Release”, tried an “Attempt Update” and now I’m upgraded to 0.47.8 with no problems anymore.

Version: 0.47.8
VSCode Version: 1.96.2
Commit: 82ef0f61c01d079d1b7e5ab04d88499d5af500e0
Date: 2025-03-18T06:55:51.040Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

TL;DR: Try Command-N

I see growth pains as things change.

There used to be chat, composer, edit. They’re rolled into the Agent now, and the shortcut keystrokes are different too.

Go to the Command Palette with Command-Shift-P, and start typing in the search box. I see:

So there are several of the new shortcuts, and the current commands. Warning though, the commands can (and do) change during updates, new ones are added and old ones removed. Bonus tip: Start searching for Cursor: and scroll.

Also bear in mind that this is built on top of VSCode, and Code has its own features and settings that don’t always play nice with Cursor. I caused myself disasters by turning on the Auto Save stuff in VSCode, so it saved editors that I hadn’t Accepted the code changes in yet, with terrible results.

JBB