Omniscio

OmniscioGuidesClaude Code theme

The Claude Code theme: change it, and fix colors you cannot read

Three complaints bring most people here: a theme that will not match, text that stays unreadable after a theme change, and a text size that no Claude Code setting controls.

Sources read November 2, 2026. By the Omniscio team. Updated .

The short version

The theme setting changes Claude Code's own colors and nothing else. Your terminal's background, its color palette and its font belong to the terminal application. A color you cannot read can come from either layer, which is why changing the theme sometimes fixes it and sometimes leaves it exactly as it was.

Then pick the line that matches your situation:

Two layers of color

Claude Code paints its own interface: the prompt box, the panels, the diffs, the status colors. The terminal paints everything behind and around that. The theme setting is Claude Code's; the background, the palette and the font are the terminal application's.

  • The theme picks one of Claude Code's own palettes. The default is dark.
  • An ANSI theme uses your terminal's ANSI palette instead of colors Claude Code ships, so one ANSI preset can look different in two terminals.
  • The terminal's own scheme is not something Claude Code controls. The background behind the interface is drawn by the terminal, and an ANSI preset borrows the terminal's palette entries for its own text.

How to change the theme

From inside a session

  1. Run /theme. The list holds the built-in presets, an auto option, any custom themes you wrote, and any theme a plugin contributes. Pick one and the interface changes at once.
  2. Or open /config and change the row it labels Theme. It is the same setting.

Without opening the picker

/config theme=dark sets it in one line. The key=value form also works in non-interactive mode and from the Claude mobile app through Remote Control, and /config --help lists the keys it accepts.

In a settings file

The choice is stored as theme in ~/.claude/settings.json, which Claude Code creates the first time you change an option in /config that it keeps there, the theme among them. The key is accepted in any settings file, and a value in the older ~/.claude.json applies when no settings file sets it.

{
  "theme": "light"
}
ValueWhat you get
autoFollows the light or dark background your terminal reports
dark, lightThe standard dark or light preset
dark-daltonized, light-daltonizedThe same presets with colors chosen for colorblind readers
dark-ansi, light-ansiA preset drawn from your terminal's own ANSI palette
custom:<slug>A theme file in ~/.claude/themes/
custom:<plugin>:<slug>A theme that a plugin contributes

The default is dark, so an install with no setting gets the dark preset rather than one worked out from your terminal.

When auto picks the wrong one

auto detects whether its terminal's background is light or dark, and then follows operating-system appearance changes as long as the terminal does.

If the answer is wrong for the window you are looking at, name light or dark instead of leaving it on auto. That removes the guess.

A theme set to the opposite of the terminal's background puts text on a background of nearly the same color. In Issue 11371, opened by jperna7254 on November 10, 2025, Warp drew Claude Code's question text in the same color as the background, and the report was closed as not planned.

A commenter in its thread suggested the cause was Claude Code on the light theme while Warp was dark, which is the mismatch this section is about.

When the text is hard to read

Decide first which layer the color comes from. If the text and the background both come from your terminal, the theme has little to do with it. If one accent, one status color or one message color inside Claude Code's own frame is the problem, a custom theme can change that color.

The colors inside a code block are a separate case, covered further down.

Themes that borrow your terminal's palette

An ANSI theme takes its colors from the terminal, so the palette entries it reads are your terminal's own.

In Issue 38958, opened by caseman72 on March 25, 2026, question text came out white in the ANSI light theme, and the change to the terminal's palette color 8 that fixed it in the plain light theme did not carry over to the ANSI one. That report was closed as a duplicate.

Switching from an ANSI preset to light or dark takes the terminal's palette out of the question, because those presets carry their own colors.

Change the one color that is wrong

A custom theme overrides individual colors and inherits the rest from a built-in preset, which makes it the smallest fix available for a color in Claude Code's own interface: keep the preset you like, and change the one token that sits too close to the background, such as claude for the main accent, error or success for a status color.

A value can be #rrggbb, #rgb, rgb(r,g,b), ansi256(n) or ansi:<name>. An unknown token or an invalid value is ignored rather than breaking the theme, so a token you invent is skipped with no error.

Syntax highlighting in code blocks is not one of those tokens. Anthropic's token reference covers the interface, the status colors, the diffs, the backgrounds and the subagent colors, and it lists no token for a keyword or a syntax color.

For that layer the lever is syntaxHighlightingDisabled, which turns the color coding off, or the terminal's own palette under an ANSI preset.

Turn the color off instead

  • syntaxHighlightingDisabled turns off syntax highlighting in diffs, code blocks and file previews, so Anthropic's own example of when to use it applies here: when the colors clash with your terminal theme.
  • prefersReducedMotion reduces or turns off spinners, shimmer and the other animations, which matters when what makes a screen hard to read is movement rather than color.

A theme of your own

Run /theme and choose New custom theme… to build one in the picker: name it, then choose the colors to override. Press Ctrl+E on a custom theme to edit it later. Themes contributed by plugins appear in the same list.

Each custom theme is a JSON file in ~/.claude/themes/. The filename without .json is the theme's slug, and selecting the theme stores custom:<slug> as your setting. Three fields are optional: name, base and overrides.

{
  "name": "Night shift",
  "base": "dark",
  "overrides": {
    "claude": "#a78bfa",
    "error": "#ff8a80",
    "success": "#7ee787"
  }
}

base names the preset the theme starts from: dark, light, dark-daltonized, light-daltonized, dark-ansi or light-ansi. It defaults to dark, and anything the overrides do not name falls through to it.

Claude Code watches that folder and reloads when a file is added or changed, so an edit in your editor reaches a running session without a restart. If the folder did not exist when Claude Code started, create your first theme file and restart once; after that, edits apply on their own.

Text size is not a Claude Code setting

The theme setting changes colors: each value it accepts names a palette, or lets auto pick one. Anthropic's settings reference, which lists the settings keys and their types, carries no font-size or text-size key at all. The size of the text is therefore decided somewhere outside Claude Code.

In a terminal, the terminal application draws the text, so its font settings are the ones that count. In the terminal inside VS Code that setting is terminal.integrated.fontSize, which Microsoft's documentation describes as the one that changes the font size of text in the terminal. Other terminals keep their font size in their own preferences.

Both VS Code keys are set the same way: open VS Code's Settings and search for the key name, or add it to your settings.json. terminal.integrated.fontSize is a number of pixels. chat.fontSize is a number of pixels too, and chat.fontFamily takes a font family the way CSS does.

Where you run Claude CodeWhat sets the text size
The CLI in a terminalThat terminal's font size. Claude Code's settings reference lists no size key.
The terminal inside VS Codeterminal.integrated.fontSize
The VS Code extension's chat panelVS Code's chat font settings (chat.fontSize), reported in issue 34196 to apply from 2.1.300
The Claude desktop appWindow zoom (Ctrl or Cmd with + and -), which scales the whole interface. The two open requests below say there is no text-only size.

That row is the one people look for inside Claude Code and do not find, and it rests on user reports rather than on Anthropic's own page: Anthropic's VS Code documentation lists no font or size setting for the panel.

Issue 34196, opened by FIL033 on March 13, 2026, asked for a font size for that panel and was closed as completed.

In October 2026 gabriel-vanca commented that chat.fontSize works, architgarg posted the same with "chat.fontSize": 14, and a commenter writing as bpasero-ant said on October 15, 2026 that it was fixed in 2.1.300 and that chat font settings should work for Claude, asking for a report if they do not.

Two limits come from the same thread. Code blocks inside the panel follow the editor's font size rather than the chat setting, as andrewroxby reported on May 11, 2026, and a window reload may be needed before a change shows. Microsoft documents chat.fontFamily beside chat.fontSize; no one in that thread reports using it here.

Two requests are still open, both about a text size that is not the whole window. Issue 78635, opened by elevyr on July 17, 2026, asks for an in-app text size for low vision; it lists OS display scaling, which enlarges everything, and app zoom, which it calls temporary and not persistent.

Issue 50543, opened by lukaemon on April 18, 2026, asks for a macOS desktop app text size and reports that Cmd plus and Cmd minus scale the whole interface and cost horizontal space.

Colorblind themes, motion and the cursor

Two presets exist for colorblind readers: dark-daltonized and light-daltonized. They change the palette rather than removing color, so a single color can still land too close to the background.

That is what Issue 32880, opened by aapeterson on March 10, 2026, reports about keywords in the dark colorblind theme on Ubuntu's stock terminal theme. It was closed as a duplicate.

  • prefersReducedMotion reduces or turns off spinners, shimmer and the other animations. It is a settings key, set to true.
  • CLAUDE_CODE_ACCESSIBILITY=1 keeps a terminal cursor visible for screen magnifiers such as macOS Zoom. It follows the input caret and, from 2.1.218, the highlighted row in menus and panels such as /config and /plugin.
  • Screen reader mode replaces the visual interface with plain, linear text and drops color-only cues. Turn it on for one session with claude --ax-screen-reader, for a shell with CLAUDE_AX_SCREEN_READER=1, or for every session with "axScreenReader": true in your user settings file.

The same question inside Omniscio

Omniscio is the desktop app we make for running many Claude Code sessions at once, and it shows a session's conversation inside its own window. It carries an appearance layer of its own, separate from the theme you set inside Claude Code.

Settings → Appearance holds a Visual Theme grid and a Custom Themes grid. Fourteen skins ship with the app, and the Theme Studio builds a new theme from the look already on screen, with a dark version and a light version you edit separately.

A theme can set the accent, the six status colors, the text and code fonts from a fixed list, and every color a theme can reach. The Studio warns when a color makes text or the accent hard to see.

Text size has its own control there. Ctrl+= and Ctrl+- step the application text size from Extra Small to XXX-Large, the same setting as Settings → Appearance → Font Size, and the isolated session view, an opt-in performance mode, follows it live.

The Visual Themes page in our library covers the theme system, the features page lists the rest of the app, and the download page has the installers.

Sources

Every key, value and command on this page rests on one of these, and each was read on the date beside it.

Claude Code ships often, and a theme name or a settings key can move between releases. Read the pages above again before you trust a copy of this one from a few months back.

Common questions

How do I change the Claude Code theme?

Run /theme and pick one from the list, or open /config and change the row labelled Theme. One command does it too: /config theme=dark. The choice is saved as the theme key in your user settings file at ~/.claude/settings.json, which Claude Code creates the first time you change an option it keeps there.

How do I turn on dark mode or light mode?

The theme setting takes dark or light by name, and auto follows the light or dark background your terminal reports. The default is dark. Set it in /theme, in /config, or as a theme key in any settings file.

Why is some of the text hard to read?

Find out which layer the color comes from. An ANSI theme draws its colors from your terminal's palette, so one palette entry that sits too close to the background makes that text unreadable. Switching to the plain dark or light preset takes the palette out of it. For a color in Claude Code's own interface, a custom theme can override that one token. For the syntax colors in a code block, syntaxHighlightingDisabled turns the color coding off.

How do I make the text bigger in Claude Code?

Change the font size in the place that draws the text. Anthropic's settings reference lists no font-size key, so in a terminal it is the terminal's font setting, and in the terminal inside VS Code it is terminal.integrated.fontSize. In the VS Code extension's chat panel, commenters on issue 34196 report that VS Code's chat.fontSize applies from 2.1.300.

Can I make my own Claude Code theme?

Yes. Choose New custom theme in /theme to build one interactively, or write a JSON file in ~/.claude/themes/ with an optional name, a base preset and a map of color overrides. Claude Code watches that folder and reloads when a file changes, so a running session picks up an edit without a restart.