Blank space appears on the right side when using Ctrl+L (Send to Agent) in new window

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Ctrl+L to send code to agent, a blank space appears on the right side of the chat panel. This happens consistently when opening a new window and using the Send to Agent feature for the first time.

Steps to Reproduce

  1. Open a new Cursor window
  2. Press Ctrl+L to use the Send to Agent feature
  3. Observe the blank space appearing on the right side of the chat panel

Expected Behavior

The chat panel should fill the available space without any blank area on the right side.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (system setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

I work across 10+ servers daily and often need to open new windows due to cache issues. This bug occurs every time I open a new window and use Ctrl+L for the first time.
It’s a recurring issue that requires manually dragging the panel each time, which disrupts workflow efficiency.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report.

Need details to reproduce and file a ticket:

  • Short video or screenshot showing empty space on the right
  • Does it happen only once after new window or after Reload Window too?
  • Run Cursor with extensions disabled: terminal cursor --disable-extensions, then Ctrl+L in new window. Does it repeat?
  • Help > Toggle Developer Tools, reproduce bug, send Console tab errors
  • Display settings: Windows Scale %, single/multi monitors, Cursor window Zoom Level

Once you send info, I’ll pass bug to engineers.

cursorai

The blank space appears on the right when using Ctrl+L for the first time.

2. Reload Window behavior
I tested Reload Window. After reloading, the blank space does not appear.
But I found a reproducible pattern:

  • If a New Chat panel is already open → first Ctrl+L causes the blank space.

  • If New Chat is closed → first Ctrl+L does not cause the issue.

This happens every time.

3. Extensions disabled
I ran cursor --disable-extensions.
The issue still occurs.

4. Developer Tools (Console log)
workbench.desktop.main.js:542 This document requires ‘TrustedScript’ assignment.
(anonymous) @ workbench.desktop.main.js:542
workbench.desktop.main.js:542 The JavaScript Function constructor does not accept TrustedString arguments. See Trusted Types for function constructor · w3c/trusted-types Wiki · GitHub for more information.
workbench.desktop.main.js:55 WARN Missing property “rpcFileLoggerFolder” in oldValue. Filling with value from initValue. Please add a migration if necessary.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-toolsai.datawrangler’ wants API proposal ‘debugFocus’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-vscode.vscode-copilot-data-analysis’ wants API proposal ‘chatVariableResolver’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-python.python’ wants API proposal ‘terminalShellType’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-python.vscode-python-envs’ wants API proposal ‘terminalShellType’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘github.copilot-chat’ wants API proposal ‘chatReadonlyPromptReference’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-azuretools.vscode-azure-github-copilot’ wants API proposal ‘lmTools’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘vscjava.vscode-java-pack’ wants API proposal ‘lmTools’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘apidev.azure-api-center’ wants API proposal ‘chatParticipant’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘apidev.azure-api-center’ wants API proposal ‘languageModels’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 ERR [Extension Host] (node:19904) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use Cursor --trace-deprecation ... to show where the warning was created)
error @ workbench.desktop.main.js:55
workbench.desktop.main.js:6377 [Extension Host] (node:19904) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use Cursor --trace-deprecation ... to show where the warning was created)
Csf @ workbench.desktop.main.js:6377
workbench.desktop.main.js:7211 Failed to get git telemetry attributes: Error: Failed to execute git
getGitAttributes @ workbench.desktop.main.js:7211
workbench.desktop.main.js:9300 [TerminalExecutionServiceProxy] v3 health check failed (took 2466ms)
_healthCheckV3 @ workbench.desktop.main.js:9300
workbench.desktop.main.js:9300 [TerminalExecutionServiceProxy] v3 health check failed, staying with current version
_initializeDelegate @ workbench.desktop.main.js:9300
workbench.desktop.main.js:9300 [TerminalExecutionServiceProxy] v3 health check failed (took 98ms)
_healthCheckV3 @ workbench.desktop.main.js:9300
workbench.desktop.main.js:9300 [TerminalExecutionServiceProxy] Cannot switch to v3: health check failed
_updateDelegateBasedOnSettings @ workbench.desktop.main.js:9300
workbench.desktop.main.js:7073 [transport] Connect error in unary AI connect ConnectError: [deadline_exceeded] the operation timed out
at t (workbench.desktop.main.js:6409:410319)
at async Object.checkNumberConfig (workbench.desktop.main.js:565:79961)
at async workbench.desktop.main.js:7103:6196
at async n (workbench.desktop.main.js:7103:5955)
at async Olo.maybeRefreshConfigInner (workbench.desktop.main.js:7103:6179)
at async Olo.getLatestConfig (workbench.desktop.main.js:7103:5568) Object
error @ workbench.desktop.main.js:7073
workbench.desktop.main.js:7073 [transport] Connect error in unary AI connect ConnectError: [unauthenticated] Error
at t (workbench.desktop.main.js:6409:410319)
at async Object.getTeamCommands (workbench.desktop.main.js:565:79961)
at async ZIo.loadTeamCommands (workbench.desktop.main.js:8976:2992) Object
error @ workbench.desktop.main.js:7073
workbench.desktop.main.js:8976 Failed to load team commands: ConnectError: [unauthenticated] Error
at t (workbench.desktop.main.js:6409:410319)
at async Object.getTeamCommands (workbench.desktop.main.js:565:79961)
at async ZIo.loadTeamCommands (workbench.desktop.main.js:8976:2992)
loadTeamCommands @ workbench.desktop.main.js:8976
workbench.desktop.main.js:9300 [TerminalExecutionServiceProxy] v3 health check failed (took 95ms)
_healthCheckV3 @ workbench.desktop.main.js:9300
workbench.desktop.main.js:9300 [TerminalExecutionServiceProxy] Cannot switch to v3: health check failed
_updateDelegateBasedOnSettings @ workbench.desktop.main.js:9300
workbench.desktop.main.js:55 ERR [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (c:\Program Files\cursor\resources\app\node_modules\@opentelemetry\otlp-exporter-base\build\src\transport\http-transport-utils.js:52:31)\n\tat [email protected] (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{“error”:“Trace spans collection is not enabled for this user”}”}
error @ workbench.desktop.main.js:55
workbench.desktop.main.js:6377 [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (c:\Program Files\cursor\resources\app\node_modules\@opentelemetry\otlp-exporter-base\build\src\transport\http-transport-utils.js:52:31)\n\tat [email protected] (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{“error”:“Trace spans collection is not enabled for this user”}”}
Csf @ workbench.desktop.main.js:6377
4workbench.desktop.main.js:9025 Error: No repository info found
at rus.refreshTabContext (workbench.desktop.main.js:2759:4409)
at async a (workbench.desktop.main.js:9025:9055)

5. Display settings

  • Windows 11

  • Scaling: 100%

  • Multi-monitor

  • Zoom Level: 0 (Reset Zoom didn’t change anything)

Even if I am already chatting with the AI, using Ctrl+L for the first time in that window always creates the blank space.
The previous conversation doesn’t matter — the issue occurs as long as it’s the first use of Ctrl+L in that window.

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