Cursor Dark Theme YAML Support

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The default “Cursor Dark” theme does not have proper support for YAML files. It has been like this for at least a year and ideally is a quick fix. Yes, I know we can simply change the theme, but it’d be nice to correct. A small thing, but these days, we all tend to look at a lot of YAML!

Steps to Reproduce

Open a YAML file in the Cursor Dark theme; no related third party extensions loaded. You will see pink keys and pink values.

Expected Behavior

At a minimum they keys and values would be a different color akin to other themes. The Cursor Light default theme presents them well as an example to emulate.

Screenshots / Screen Recordings

Operating System

Windows 10/11
MacOS

Version Information

Version: 3.24.12
VS Code Extension API: 1.128.0
Commit: 37b865941ccb31e2fc90c685157534efca87f960
Date: 2026-10-09T20:56:41.904Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Thomas_Rectenwald, thanks for the report!

You’re right, Cursor Dark doesn’t give YAML keys their own color, so keys end up the same pink as string values. Cursor Light and Cursor Dark Midnight don’t have this problem. I’ve flagged it to the team.

In the meantime, you can fix it locally without switching themes. Open your user settings JSON (Command Palette, then “Preferences: Open User Settings (JSON)”) and add:

"editor.tokenColorCustomizations": {
  "[Cursor Dark]": {
    "textMateRules": [
      {
        "scope": "entity.name.tag.yaml",
        "settings": { "foreground": "#82D2CE" }
      }
    ]
  }
}

That gives YAML keys the same teal Cursor Dark uses for JSON keys, and only applies while Cursor Dark is active.

Hey @Thomas_Rectenwald,

A fix for YAML keys showing up in the same pink as their values in Cursor Dark has landed and will be included in an upcoming version of Cursor (3.25). It also covers the Dark High Contrast and Dark Colorblind variants, and YAML true/false/null values will no longer show in the string pink either.

Once you’re on that version, you can remove the editor.tokenColorCustomizations workaround if you added it. It uses the same key color, so leaving it in place won’t cause any conflict.

Let me know if you still see it after updating!

Thank you so much!