Regression for canvas rendering: 3.6 -> 3.7

Describe the Bug

The canvas rendering has completely different colors in compare to the previous version

Steps to Reproduce

  1. Upgrade 3.6 → 3.7

Expected Behavior

I expect badges have color, and rows should be colorized too

Operating System

MacOS

Version Information

3.7.6 adfadf

Does this stop you from using Cursor

No - Cursor works, but with this issue

the current view score is rated as: terrible, terrible.

Canvas theming was improved in 3.7. There was a bug where canvases always rendered in dark mode regardless of your editor theme. That was fixed, so canvases now correctly follow your theme, which can look quite different from what you were used to.

To help look into this further:

  1. Which color theme are you using in Cursor? (Check via Cmd+K Cmd+T)

  2. Was this canvas created before or after the 3.7 update? If before, try asking the agent to regenerate it — it should pick up the current theme-aware color palette.

Currently, canvas theming maps light/dark from your editor theme but doesn’t pass through full custom theme colors, so some elements may not have the color contrast you’d expect. We’re aware this is a gap.

Thank you for taking care and fixing bugs.

I remember I configured Solarized. But I can not check it now because after upgrade the Cursor just crashes


But I am going to open separate issue regarding this.

I am not sure I can find it manually:

Yes, canvas was created before 3.7. I asked the agent to regenerate, but canvas still looks ugly and now how it was on 3.6. I hope the color gap will be fixed soon. Thank you.

A couple of things from your screenshots:

Finding your color theme — Cmd+K Cmd+T won’t work in Cursor (that’s the VS Code shortcut). In Cursor, Cmd+K is mapped to the AI prompt bar, so the combination never resolves, which is the “not a command” message you saw. Apologies for pointing you there. To check or change your theme, open the Command Palette with Cmd+Shift+P and run Preferences: Color Theme. The “theme” search in Settings only lists feature toggles, not the color picker, which is why it wasn’t there.

Why regenerating didn’t help - since you’re on Solarized, this is expected. Canvas currently follows only whether your editor theme is light or dark; it doesn’t pull through the specific colors of a custom theme. So a regenerated canvas uses our standard light (or dark) palette rather than your Solarized colors, which is the color gap you’re seeing. It’s a known limitation we’re aware of, and it isn’t something regenerating can fix on your end.

  1. >It’s a known limitation we’re aware of, and it isn’t something regenerating can fix on your end.

I am sad seeing this regression =(

I hope it will be fixed soon.

Now that you’ve confirmed Solarized Light, here’s what’s happening and a workaround that should bring the color back. Before 3.7, canvas was stuck rendering in dark mode for everyone (the bug that got fixed). The dark palette is more saturated than the light one, so your canvases looked more colorful in 3.6 simply because they were always dark. With the fix, canvas now follows your editor’s light/dark setting, and Solarized Light maps to our standard light palette.

If you want that more vibrant look back, switch to any dark editor theme: Cmd+Shift+P → Preferences: Color Theme → pick a dark one. Canvas will then render with the dark palette, which is the same look you had before 3.7.

Carrying the actual colors of a custom theme like Solarized into canvas is a known limitation we’re tracking, so I won’t pretend it’s an instant fix. But the dark-theme route is the closest match to your old setup for now.

Ok, Thank you for the tip. So this will make colors at canvas vibrant, but theme will be dark, right?

But then I can not work in cursor IDE. I can not read text in dark mode.