Ixion

Looks like Cursor hasn't synced with mainline VSCode yet and is still using Electron 32.2.6, which causes a crash on macOS with Vibrancy enabled. I don't follow Cursor's development cycle,...

Thanks for the update! I didn't receive Cursor 0.47.9 on my end yet, but after switching to the `prerelease` update track I got 0.48.0, which does include it. I'll look...

Vibrancy is actually based on that very same custom CSS loader, so you can use Vibrancy to load custom CSS like this: ```json "vscode_vibrancy.imports": [ "/Users/user/my_custom.css" ], ``` @RobbieMinderhoud would...

Friendly reminder that using the Custom CSS extension is redundant, as Vibrancy has the same feature that is verified to work, see my earlier comment for how to use it....

I'll work on implementing both of these themes, thank you @RobbieMinderhoud and @cncn123!

I've published v1.1.55 which includes the new Cursor theme fixes and automatically loads them alongside the default dark/light themes, as well as a setting to disable them if desired via...

The Vibrancy theme needs to match the VSCode theme, and there is an automatic theme switch feature that can be enabled via `vscode_vibrancy.enableAutoTheme` setting, documentation for which is available here:...

Just to make sure, did you reload vibrancy after changing this setting? This is a required step, and I can see you have a pending notification in your bottom right

Please confirm that you are using **Light+** as your VSCode theme, and that either automatic switching is enabled or your Vibrancy theme is set to **Default Light**. Here's what the...

@behindthepixels please make sure that you have this setting disabled: From your description, it sounds like `window.autoDetectColorScheme` is set to `true`, as otherwise there should be no changes in appearance...