Debug Toolbar and Status bar disappears

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor version: Version: 3.14.7 (user setup)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
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.291
OS: Windows_NT x64 10.0.26200

Windows 10/11
Flutter/Dart extension versions
Repro: start Flutter debug → UI loses debug bar → Stop disabled → Start says session already running
That orphaned flutter run --machine processes remain after the UI disconnects

Steps to Reproduce

Start the debugger, let the cursor screen lose focus, and the status bar and debugger bar will both disappear.

Expected Behavior

The bars and the debugger context tool bar should stay visible.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.14.7 (user setup)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
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.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report and versions, that helps. The symptoms disappearing bars + Stop disabled + “session already running” + orphaned flutter run --machine look more like a floating toolbar layout getting out of sync when the window state changes, not the usual panel being hidden.

To narrow it down, could you check three things when it happens again:

  1. View → Appearance → Status Bar in newer versions “Show Status Bar”. Is it unchecked, or still checked while the bar isn’t visible? This helps separate a stuck hidden setting workbench.statusBar.visible from a viewport desync.
  2. Do the bars come back specifically when you click maximize or restore in the window title bar? Asking about maximize or restore, not normal resizing. That’s the most likely trigger, and if it reproduces the issue it’s a good diagnostic signal.
  3. What is debug.toolBarLocation set to, and was a second Cursor window or Agents Window open at the time? Your screenshot shows an Agents Window open, I want to see if it’s related.

For now, some temporary workarounds:

  • If the status bar got stuck hidden, bring it back via View → Appearance → Status Bar.
  • For the toolbar, try debug.toolBarLocation: docked. It pins the controls in the Run and Debug panel and avoids losing the floating toolbar. Note one docked limitation: the session drop-down isn’t visible, and starting a second session while one is active is harder, which matches the “session already running” message. As an alternative, try debug.toolBarLocation: commandCenter which moves controls to the title area, but it requires Command Center enabled and window.titleBarStyle: custom.
  • For orphaned flutter run --machine processes, you’ll need to kill them via Task Manager for now.

Share what you find and I can pass it to the team with concrete details.

If deanrie’s “layout getting out of sync when the window state changes” read is right, there are two quick checks that would confirm it and usually restore the bars without a full reinstall:

  1. Command Palette → Developer: Reload Window (Cmd/Ctrl+R in the palette). If the toolbar and status bar come back after a reload but vanish again on the next window-state change, that points squarely at layout state, not a corrupted install.
  2. If a reload doesn’t do it, Command Palette → View: Reset View Locations resets the workbench layout to defaults, which clears an orphaned floating-toolbar position.

To rule out an extension nudging the layout, it’s worth launching once with --disable-extensions and repeating whatever triggered it (looks like the flutter run --machine session in your case). If the bars stay put with extensions off, the culprit is one of them re-registering a toolbar contribution on session start.

Curious whether the reload alone brings them back for you — that answer narrows it a lot.