Unable to Set Focus

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Unable to Set Focus

I have configured the following keyboard shortcut:
{
“key”: “ctrl+i”,
“command”: “runCommands”,
“args”: {
“commands”: [
“composer.openChatAsEditor”,
“workbench.action.focusSideBar”,
“composer.focusComposer”,
]
}
}

Additionally, I dragged the Agent window to my second monitor. Previously, in “Editor (Classic)” mode, pressing Ctrl+I would successfully shift the focus to the input field within the Agent window on the second monitor. However, since the “Classic” mode has now been removed—leaving only the standard “Editor” mode—pressing Ctrl+I no longer shifts the focus to the Agent input field on the second monitor.

Steps to Reproduce

Unable to Set Focus

I have configured the following keyboard shortcut:
{
“key”: “ctrl+i”,
“command”: “runCommands”,
“args”: {
“commands”: [
“composer.openChatAsEditor”,
“workbench.action.focusSideBar”,
“composer.focusComposer”,
]
}
}

Additionally, I dragged the Agent window to my second monitor. Previously, in “Editor (Classic)” mode, pressing Ctrl+I would successfully shift the focus to the input field within the Agent window on the second monitor. However, since the “Classic” mode has now been removed—leaving only the standard “Editor” mode—pressing Ctrl+I no longer shifts the focus to the Agent input field on the second monitor.

Expected Behavior

The Agent input field can gain focus on the second monitor.

Operating System

Windows 10/11

Version Information

Version: 2.6.20 (user setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
4

Hey, thanks for the detailed report. This looks like a regression after removing “Editor (Classic)” mode. Focus commands route differently in the new layout, especially between windows.

A couple things to try:

  1. Simplify the keybinding. Try using just composer.focusComposer or composer.openComposer without the intermediate commands. The chained workbench.action.focusSideBar step likely isn’t needed anymore and might mess with focus in the current layout:
{
  "key": "ctrl+i",
  "command": "composer.focusComposer"
}
  1. Reload the second window after moving Agent there: Ctrl+Shift+P then Developer: Reload Window. This helped with similar multi-monitor focus issues: Bugs in Agent/Chat window when its moved to editor and on different monitor

If neither helps, this is likely a focus traversal bug on our side in cross-window cases. I flagged it with the team, let me know how it goes with the simplified binding.

5

No, if you use just a single simple command, you won’t even be able to enter any input in the second window.

1 Like
6

Got it, so it’s not just the keybinding. Input isn’t working in the second window at all. This is a known focus issue when moving Agent to another monitor.

After you move Agent to the second monitor, try reloading just that window: Ctrl+Shift+P then Developer: Reload Window. This worked for other users with a similar issue: Bugs in Agent/Chat window when its moved to editor and on different monitor

If reloading doesn’t help, let me know and I’ll pass it to the team.

9

Yes, reloading the window didn’t help either. The crux of the issue is this specific command: composer.focusComposer. In the Editor (Classic) mode, it successfully focuses on the input field located on the second monitor; however, in the new Editor mode, it fails to focus on the input field on the second monitor. Please fix this issue; it is a clear and serious problem.

1 Like
10

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.