Cursor Themes and Appearance: Dark Mode, Fonts, Ligatures

Start here if the steps below do not match what you see. Theme controls and the Extensions view are part of the IDE, not the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition.. If you are in the Agents Window, open the command palette and run Open IDE, then continue. Both windows can be open at once, so switching back and forth costs nothing.

The editor half of Cursor is the VS Code fork, while the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. is a ground-up native surface rather than that fork, which I take to be why theme controls sit where they do. Cursor's own comparison of the two surfaces puts VS Code extensions on the editor side, and a color theme is an extension.

Missing this costs you a debugging session on the wrong thing. A shortcut that does nothing reads like a broken install, so the search starts in Settings JSON, hunting a key that was never involved.

Cursor's themes help page calls that command Open IDE. The Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. doc calls the same switch Open Editor Window, so try the other name if the first one does not come up in the palette.

Three steps through the command palette. The theme names matter: pick Default Light Modern or any theme with "Light" in the name for light mode, and Default Dark Modern or Cursor Dark for dark.

1. 1Open the command palette: ⌘+⇧+P on Mac, Ctrl+⇧+P on Windows and Linux.
2. 2Type Preferences: Color Theme and select that command.
3. 3Pick a light or dark theme from the list.

Light and dark are not a separate switch in Cursor. Both are theme choices, so the same three steps cover "put it in dark mode" and "change my theme".

Cursor's help page offers Default Dark Modern and Cursor Dark for dark mode without ranking them, and the order they appear in probably means nothing. One is the built-in, the other is Cursor's own, and past that it is preference. Step three's naming rule matters more than the choice between them does. Theme names come from whoever wrote the theme, so once you have a dozen installed, the word "Light" in a title is the only signal the list gives you before you arrow onto it.

Cursor can follow it. Open Settings with ⌘+, on Mac or Ctrl+, on Windows and Linux, search for "Auto Detect Color Scheme" and enable it, and the editor follows your OS appearance from then on.

A machine set to switch appearance on a schedule switches Cursor with it, mid-session, halfway through whatever you were reading. I have watched that land at sunset, and it is more disorienting than harmful. The setting is worth leaving off if you take screenshots or record demos out of your editor, because the appearance of the app changes underneath the recording.

If a theme you picked keeps reverting or flipping on its own, check this setting before you look at the theme.

Themes are extensions, so the Extensions view is where you get them. The shortcut is ⌘+⇧+X on Mac, Ctrl+⇧+X on Windows and Linux; search for theme and click Install on one.

Being extensions, themes inherit everything else that is true of extensions, and the registry is where that bites. Cursor installs from Open VSX rather than the VS Code Marketplace, so a theme you know by name from VS Code may not be listed at all, and what is listed does not always behave the same way. If you already had it over there, the one-click VS Code Import brings themes across with your settings, and that is less work than finding each one again.

The instinct is to install first and browse afterwards. I would flip the order. Arrow through the Color Theme list you already have before you install anything, since that list is where you end up either way and installing only adds a row to it.

Extension installs can be governed centrally, and a theme is an extension like any other. The setting is extensions.allowed, which team admins configure in the Security and Identity section of the team dashboard, and Cursor applies it to every member's client automatically.

Check how the allowlist works before you blame the theme. extensions.allowed is an allowlist, so the moment an admin adds a single entry, everything not on the list is blocked and there is no implicit allow-all underneath. An entry added for the publishers a team actually depends on will therefore block every theme nobody thought to name, which in practice means all of them. The enterprise identity page has the wildcard syntax that keeps the rest allowed.

The obvious ask is for an admin to add that one theme. It is the wrong ask, or at least the small version of it, since one entry clears one person and the next theme anyone wants is blocked exactly the same way. Ask instead for the "*": true wildcard alongside whatever entries they are deliberately denying, which restores everything else and leaves their deny list intact.

The other control is time-based. An install cooldown defers installs and updates fleet-wide, so a version has to sit public for a set number of hours before anyone can take it, and a theme published this morning may not be installable today.

On a team of four, nobody is pushing these settings and the answer is yes, install it. On four hundred I would assume something is set until an admin says otherwise. Worth asking before you tell everyone to install the same theme, because that allowlist was probably written with language servers and linters in mind.

Font settings are all in Settings rather than the command palette, and they are split so you can size the editor and the terminal independently. The table below is the search term for each one.

That split is the first thing to check when a font change looks like it did nothing. Font Size covers the editor font size, the terminal font size, or both, and changing one of them, naturally enough, leaves the other where it was. The terminal is the one people notice, since the editor grows and the terminal keeps its old size.

The Font Family field takes the name of any font installed on your system. The failure mode that follows is, I think, the most common one on this page. The field accepts a name, and a name your system spells differently, or a font that lives on your other laptop, looks exactly like a name that works. Settings that arrived from somewhere else are the usual culprit, an imported VS Code setup for instance.

Ligatures are two settings in a fixed order. Font Ligatures set to true turns on what the typeface already carries, so pick the font first and flip the toggle second. Done in the other order, nothing appears to happen and the toggle looks broken.

Keys are a separate topic. Remapping lives on Cursor's keyboard shortcuts help page, and the file behind it in the keybindings.json guide.