Skip to content
Nilay Kabariya

Entry No.101·Agents··3 min read

Claude Code custom themes: five free ones, checked

Five original Claude Code themes as copy-paste JSON, the official file format, and what I checked: they load in /theme, token names, and contrast.

by Nilay#claude-code#themes#terminalAGENTS

Verdict

Custom themes are real, one JSON file each, and all five below load in the real /theme picker.

Tested on

Appears in /theme picker on
Claude Code 2.1.325 and 2.1.319 (Windows)
Checked
all five listed in the real /theme picker, 24 tokens each, WCAG contrast
Not checked
how each palette looks on screen (no screenshot yet)

Claude Code in the terminal lets you define your own colour theme. It is one small JSON file in ~/.claude/themes/, and the picker lists it next to the built-in themes. The format is in the official docs (Terminal configuration: create a custom theme). I made five and checked what I could, and they now live in a gallery of Claude Code themes, 58 so far, each with its own page and a one-line install.

The clip is a mock-up drawn from the theme files, not a screen recording of the CLI.

Install one

mkdir -p ~/.claude/themes
cp themes/*.json ~/.claude/themes/

Then run /theme inside Claude Code and pick it. If ~/.claude/themes/ did not exist before, restart Claude Code once so the folder is watched. The five files, a validator and the clip’s source are in nk-repro / claude-themes.

The five

Theme Base Accent (claude) text error success Designed for background
Chai at Midnight dark #f2a65a #f3e6d3 #ef6a5b #9bc77a #16100c
Monsoon, Surat dark #6fd3c6 #dbeceb #f0776c #8fd694 #0d1618
Paper Lantern light #c2410c #2b2118 #b91c1c #2f7d32 #faf5ea
Terminal Mango dark #ffb000 #f2f2f2 #ff5d5d #7ee081 #101010
Kite Festival light #d6246e #1a1c2c #c81e1e #15803d #fbfbff

A theme file has three fields: name, base (one of dark, light, dark-daltonized, light-daltonized, dark-ansi, light-ansi) and overrides, a map from token name to colour. Anything you do not list falls through to the base. This is Chai at Midnight in full:

{
  "name": "Chai at Midnight",
  "base": "dark",
  "overrides": {
    "claude": "#f2a65a",
    "claudeShimmer": "#ffd29a",
    "text": "#f3e6d3",
    "inactive": "#8a7866",
    "subtle": "#6d5d4e",
    "suggestion": "#e8b86d",
    "permission": "#d9a05b",
    "success": "#9bc77a",
    "error": "#ef6a5b",
    "warning": "#f2c14e",
    "promptBorder": "#7a5a3a",
    "planMode": "#7fb7a4",
    "autoAccept": "#c9a0dc",
    "bashBorder": "#e07a5f",
    "diffAdded": "#25361c",
    "diffRemoved": "#43211c",
    "diffAddedDimmed": "#1d2a16",
    "diffRemovedDimmed": "#341a16",
    "diffAddedWord": "#4a6b34",
    "diffRemovedWord": "#8a3a30",
    "userMessageBackground": "#241a13",
    "selectionBg": "#4a3522",
    "rate_limit_fill": "#f2a65a",
    "rate_limit_empty": "#3a2d22"
  }
}

What I checked

  • Tokens. Each theme sets 24 tokens, all from the documented list. The validator in the repo rejects unknown tokens and any colour that is not #rrggbb (the docs say unknown tokens are silently ignored, so a typo would otherwise do nothing).
  • Contrast. A Claude Code theme cannot set the terminal’s own background, so I measured every readable token (text, accent, the status colours) against the background each palette was designed for. All five clear WCAG’s 4.5:1 for every readable token; the body text is between 14.5:1 and 17:1.
  • The real picker. I started Claude Code 2.1.325 with a throwaway config folder holding these five files and "theme": "custom:chai-at-midnight", then opened /theme. The picker listed all five under the built-in themes, each marked custom, with Chai at Midnight selected, and showed its diff preview.
  • The installed version. All 24 token names also appear as strings inside the Claude Code 2.1.319 executable on my machine.

What I did not check

I read the picker as text, so I have not seen the five palettes on screen yet, and the clip above is a mock-up, not a recording. If you try one, tell me what looks wrong: the one thing a validator cannot judge is whether a palette feels right in a real session. I will add screenshots when I have them.

Good to know

  • Terminal colour depth. The docs do not say how #rrggbb colours behave in a terminal without truecolor. If yours is limited, use the ansi: colour forms from the same page.
  • Only the terminal. These files are for the terminal CLI. The Desktop app’s Code tab takes a separate kind of mod, described in the Claude Code docs.
  • Plugins can ship themes. A plugin can carry themes/<slug>.json; those are read-only, and editing one in /theme saves a copy to your own folder.

— N.K., end of entry No.101

Useful? Pass it on:Post on XFollow @EmotionalMatter

Related entries

  1. No.039

    Fix: Claude Code "Prompt is too long"

    Claude Code fails every message with Prompt is too long, or asks for usage credits. One oversized file did both in my tests, and Claude Code's guard missed it.

    > Prompt is too long

    AGENTS4 min
  2. No.036

    Fix: Claude Code "not compatible with the version of Windows"

    Windows says claude.exe won't run right after an npm install of Claude Code. Your Windows is fine. Reproduced on npm 12, with the reinstall that fixed it.

    > This version of C:\...\claude-code\bin\claude.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.

    AGENTS5 minWindows
  3. No.035

    Fix: Claude Code "Invalid API key · Fix external API key"

    Invalid API key · Fix external API key, Please run /login and 401 in Claude Code: every auth message reproduced on 2.1.314, and the Windows quoting trap.

    > Invalid API key · Fix external API key

    AGENTS5 minWindows

tip: paste the exact error text