Debug toolbar does not appear in Command Center while debugging on macOS

Support Bug Reports
,
1

When I set:

"debug.toolBarLocation": "commandCenter"

the debug toolbar does not appear in the Command Center even while the app is actively running in debug mode.

I am using Cursor on macOS and debugging a Flutter app. The application launches successfully and the debug session is active, but the Command Center does not show the debug controls at all.

Current behavior:

  • App starts and runs normally in debug mode
  • Debug session is active
  • Command Center is visible
  • Debug toolbar does not appear in the Command Center

Expected behavior:

  • When debug.toolBarLocation is set to commandCenter, the debug controls should appear in the Command Center while a debug session is running

Settings used:

"window.commandCenter": true,
"debug.toolBarLocation": "commandCenter",
"workbench.activityBar.orientation": "horizontal"

What I already tried:

  • Reloaded the window
  • Reset view locations
  • Reset menus
  • Confirmed Command Center is enabled
  • Confirmed debug session is running
  • Switched activity bar orientation
  • Switched between stable/prerelease behavior checks
  • Floating toolbar works, but Command Center does not

Notes:
This looks like a regression or unsupported behavior in Cursor, because upstream VS Code documents commandCenter as a valid value for debug.toolBarLocation, and Cursor forum threads show similar reports of the debug toolbar not appearing in the Command Center. (Visual Studio Code)

Environment:

  • OS: macOS
  • App type: Flutter
  • Cursor version: [please insert your exact version here]

Steps to reproduce:

  1. Enable Command Center
  2. Set "debug.toolBarLocation": "commandCenter"
  3. Start a debug session
  4. Observe that no debug controls appear in the Command Center

Additional context:
There are also recent Cursor UI regressions around missing Command Center and top bar elements, which may be related. (Cursor - Community Forum)

Version: 2.6.20
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: Darwin arm64 25.3.0

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

Hey, thanks for the detailed report.

This is a known issue. debug.toolBarLocation: commandCenter isn’t working correctly in Cursor right now. The team is aware, but there’s no ETA for a fix yet.

There’s also a related thread about similar debug panel issues in 2.6.20: Run and Debug controls missing from Run and Debug panel in 2.6.20

For now, the only workaround is to use "debug.toolBarLocation": "floating" or "docked", which you already found.

1 Like
5

A post was merged into an existing topic: Run and Debug controls missing from Run and Debug panel in 2.6.20