Hi Cursor team — I’m running into a theming conflict that seems impossible to fix with current color tokens.
I use a custom dark UI / light editor theme. In Cursor, .plan.md files render with very light text (low contrast on light background), while regular .md files and Markdown preview render correctly.
When I set the theme’s global foreground to a dark value, .plan.md becomes readable — but then text in the Agents sidebar becomes too dark / low-contrast.
When I set foreground back to a light value, Agents sidebar looks correct again — but .plan.md goes back to washed out text.
Repro
-
Use a custom VS Code-compatible theme in Cursor.
-
Open a generated *.plan.md file in Cursor’s plan/workflow view.
-
Compare text rendering in:
-
normal .md editor
-
markdown preview
-
.plan.md view
-
Agents sidebar
Expected
-
.plan.md text should be readable (dark on light background in that view).
-
Agents sidebar text should remain readable independently.
Actual
-
Both surfaces appear to share a fallback foreground path.
-
Fixing one causes regression in the other.
What I tried
-
Markdown token scopes (source.gfm, markdown quote, paragraph scopes)
-
Sidebar/list tokens (list.foreground, list.deemphasizedForeground, sideBar.foreground, secondarySideBar.foreground)
-
Global fallbacks (foreground, descriptionForeground, disabledForeground)
No combination cleanly fixes both.
Request
Could Cursor expose dedicated color keys for:
-
Plan/workflow markdown text (the .plan.md surface)
-
Agents sidebar item text/meta text
That would let custom themes avoid this tradeoff and keep both views accessible.
