Canvas becomes unresponsive when opened in a standalone window

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When a canvas is dragged out from the main IDE window into a standalone window, the new standalone canvas window becomes completely unresponsive. It does not respond to mouse clicks, scrolling, or interactions.

Steps to Reproduce

  1. Open a canvas inside the main Cursor IDE window.

  2. Click and drag the canvas tab out of the main window to open it as a standalone window.

  3. Try interacting with the canvas in the new standalone window (clicking elements, scrolling, typing).

Expected Behavior

The standalone canvas window should remain fully interactive, responsive to clicks, and scrollable, matching its behavior when embedded in the main IDE window.

Operating System

Windows 10/11

Version Information

Version: 3.13.21 (user setup)
VS Code Extension API: 1.128.0
Date: 2026-07-27T03:26:14.573Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256

OS information:
Edition Windows 11 Home Single Language
Version 25H2
Installed on ‎8/‎10/‎2025
OS build 26200.8875
Experience Windows Feature Experience Pack 1000.26100.334.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Farhan_Hossen,
This is something we’ve seen before when tabs are moved into a standalone window (the Browser Tab hits it too), and I’ve reported your Canvas case to the team.

For now the workaround is to keep the Canvas tab inside the main Cursor window; it stays fully interactive there. I don’t have a timeline to share on the fix yet, but I’ll follow up here once there’s an update.