Color theme support per workspace in Cursor 3

Ideas Feature Requests
, ,
1

Feature request for product/service

Cursor IDE

Describe the request

Agent Window is good place to run multi agents. But very hard to distinguish in which workspace agent is working. That’s why I keep using Editor Window, as it supports color customize per workspace.
Please support color theme per workspace so that human can easily understand where it is working.
The color difference of list item and UI in the tab will really helpful.
And that’s what Claude doesn’t offer.

4

yes please lord

5

Would love to see this get adopted!

6

Summary: The Agents Window does not apply workbench.colorTheme. It renders in a fixed default-dark chrome regardless of user- or workspace-level theme configuration.

Environment:

  • Cursor on Windows 10 (build 26200)

  • Theme set via both user settings.json and a .code-workspace settings block

Repro:

  1. Set "workbench.colorTheme": "<any installed theme>" in user settings, and/or in a .code-workspace settings block.

  2. Open the Editor Window → theme applies correctly.

  3. Open the Agents Window → still default dark.

  4. Fully quit and relaunch (not just “Reload Window”) → Agents Window still default dark.

Expected: The Agents Window respects workbench.colorTheme, ideally resolving the active workspace’s value when one is focused.

Actual: The setting is ignored entirely — at both user and workspace scope — so the window cannot be themed at all.

Root-cause hypothesis: The Agents Window appears to run as a folderless (“empty”) window and resolves its own fixed theme rather than reading workbench.colorTheme from user/workspace settings.

Proposed resolution (in priority order):

  1. Honor workbench.colorTheme, including per-workspace overrides, so the window reflects the active workspace’s theme.

  2. At minimum, honor the user/global workbench.colorTheme so it isn’t pinned to default dark.

  3. Otherwise, expose a dedicated setting (e.g. cursor.agentsWindow.colorTheme).

Acceptance criteria: With a non-default theme configured, the Agents Window renders in that theme after a normal launch — and when multiple workspaces define different themes, the window reflects the active workspace’s theme.

Why it matters: Per-workspace colors are the primary way to tell at a glance which project a given agent is working in when running several in parallel. That signal is lost the moment focus is in the Agents Window.

Submitted this forum entry and was directed here by the Staff. If you want to review my post as well.