Keyboard shortcut for agent mode incorrectly opens a new chat tab

[instanceofmel (Mel)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Switching to agent mode via keyboard shortcut opens a new chat tab

Steps to Reproduce

1. Open chat
2. Send a message
3. Switch to Ask mode
4. Switch to Agent mode via configured keyboard shortcut

Expected Behavior

Agent mode should be selected in current chat tab

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Additional Information

It was working until 1.4.

Reports by other keyboard-centric users:

Agent mode shortcut

Describe the Bug I setup “CMD + .” shortcut that toggles Ask mode without opening new window. I tried to do the same for agent mode and it just refuses to work. It always always opens new chat window in agent mode. I NUKED everything on CMD + . / - commands and it still doesnt change ■■■■. It is behaving differently then the keybinding menu suggests. Steps to Reproduce Setup keybindings for Open Chat in Ask mode and Agent mode. Ask mode should be able to toggle itself inside current active ch…

'Open Chat in Agent Mode' is broken

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug CTRL + L for ‘Open Chat in Agent Mode’ is broken. Steps to Reproduce 1 Assign ‘Open Chat in Agent Mode’ to Ctrl + L on Windows 2 Start a new chat in ‘Ask’ mode 3 Send message ‘hi’ 4 Press CTRL + L Observe: New chat created (in Agent mode) Expected Behavior Expected: Agent mode selected (in existing chat) Operating System Windows 10/11 Current Cursor Version (Menu → About Cursor → Copy) Version: 1.5.4 (user setup) …

Does this stop you from using Cursor

No - Cursor works, but with this issue

[AuspiciousSolitude]

@condor @deanrie why were the other 2 threads linked here closed, given the issue wasn’t resolved?

We have a bizarre situation where a new user has to periodically create a new thread of the issue each time a previous one closes.

In this case, @instanceofmel has had to do it with this thread.

[deanrie]

I reopened them, they closed automatically. I’ll find out the status of this issue.

[vibrant_sutherland]

I have reported this issue multiple times, but it still hasn’t been fixed as of version 1.7.

[vibrant_sutherland]

I have updated to 1.7.54, but the issue is still there. And I can’t use the old version.

[austinp (Austin Nick Piel)]

Hey all, just merged a fix for this that will be going out in the next release!