Allow the Agents Window to honor workbench.colorTheme (per-workspace and global)

Feature request for product/service

Cursor IDE

Describe the request

Make the Agents Window honor the editor’s color theme so it can be themed like the rest of Cursor.

Today the Agents Window renders in a fixed dark chrome and ignores workbench.colorTheme entirely — both the user-level value and any .code-workspace override. The classic editor window themes correctly from the same setting, but the Agents Window does not pick it up, even after a full quit-and-relaunch (not just “Reload Window”).

I’d like one of the following, in order of preference:

Honor workbench.colorTheme in the Agents Window the same way the editor window does — including per-workspace overrides, so the Agents Window reflects the theme of whichever workspace is active.
If full per-workspace theming isn’t feasible because the Agents Window is a single multi-workspace surface, at least honor the global user-level workbench.colorTheme so it’s not locked to default dark.
Failing both, add a dedicated Agents-Window theme setting (e.g. cursor.agentsWindow.colorTheme) so it can be themed independently.
Why it matters: I rely on a different color theme per workspace to tell projects apart at a glance. Because the Agents Window can’t be themed, that visual cue disappears the moment I switch into it — which is increasingly where I spend my time.

Operating System (if it applies)

Windows 10/11

Hey @Brent_Rowe!

Right now you’re right, we don’t do any syncing of themes between the Editor and Agents Window.

That said, you can edit the Appearance of the Agent Window! Just head to Settings > Appearance > Manage Themes.

It’s not as sophisticated as matching the VSCode settings (and you have some cool ideas!), but it does mean you aren’t locked into any specific theme.

You might also want to go add your voice to this thread:

Not seeing this “Manage Themes” option on my end. Is this still behind a rollout/feature flag, or only available in certain builds/channels right now?

Hey @Evan_Mavis

You’re right – it’s behind a feature flag. :confused: Sorry about that. Edited my previous response.

That said, it is something we are working on now, so hopefully more to share soon!

No worries - thanks for the info!