Inter-office memo
- To
- Everyone using Claude Code in the Claude Desktop app
- From
- Mo, Chief Executive
- Date
- November 15, 2026, 6:09 AM CST
- Re
- Custom themes in Claude Code
Claude Code’s desktop app now takes custom themes. How to set one, and what to check
Since November 13, 2026, the Code tab of the Claude Desktop app takes custom themes, colors and an animated background, built as mods. Install Anthropic’s theme-examples plugin and run /custom-theme, or ask Claude for a look; colors need Claude Code 2.1.324 or later. A theme is code that runs with your permissions, and the terminal and cloud sessions don’t draw one.
What Anthropic released
On November 13, 2026, Anthropic’s ClaudeDevs account announced: “You can now build custom themes for Claude Code on desktop with mods! Change the colors, add an animated background, and make it your own.” A second post set the terms: “Update to the latest version of the desktop app to try it. Themes work in local sessions in the desktop app today, support for cloud sessions is coming soon.”
A theme is a mod: a plugin whose JavaScript or TypeScript runs inside Claude Code. One call, $.theme.set, sets both the Code tab’s colors and a backdrop behind the conversation. A backdrop can be still, such as a gradient or a picture, or a moving scene, and frosted glass over it keeps the text readable. Anthropic’s docs add that a session has one theme at a time: whichever mod calls $.theme.set last replaces the colors and the backdrop of any earlier one.
The same day, Anthropic added theme-examples to its official plugin marketplace: “Twenty scenes to paint behind your Claude Code desktop window, light and dark,” among them a lagoon seen from above, a koi pond and a departure board. Eight of the twenty come as light and dark twins. The plugin paints scenes, not the Code tab’s colors.
Where themes show
| Where you run Claude Code | A mod’s colors | A mod’s backdrop |
|---|---|---|
| Desktop app, Code tab, local session | Yes, with Claude Code 2.1.324 or later | Yes |
| Desktop app, cloud session | Not yet, “coming soon” | Not yet |
| Desktop app, WSL session | No, plugins don’t load there | No |
| Terminal | No, it keeps its own colors | No, “The terminal draws no backdrop” |
claude -p, the Agent SDK and apps built on them |
No | No |
The Desktop app bundles its own copy of Claude Code. To check it, type /status in a local session in the Code tab and read the Claude Code row. If it’s older than 2.1.324, update the app. The docs also name the mobile app as a place that draws backdrops; Anthropic’s announcement and its examples are about the desktop app.
Three ways to get one
- Try Anthropic’s examples. In a local session in the Code tab, select + beside the prompt box, then Add plugins (or Plugins, then Browse plugins), and install theme-examples. From a terminal,
claude plugin install theme-examples@claude-plugins-officialdoes the same (on a computer that has never run Claude Code in a terminal, first runclaude plugin marketplace add anthropics/claude-plugins-official), and the plugin docs say a plugin installed for your user in the terminal is available in the Desktop app’s local sessions too. Then/custom-themeshows a card of every theme with a preview button,/custom-theme <name>applies one to the project, and addingsessionlimits it to the session you’re in. The plugin also has/fireworks, which goes off on its own when Claude says “merged”;/fireworks auto offstops that. Its pull request calls it an example to read and copy, and says: “It is not a set of themes that will be maintained long-term.” - Ask Claude for one. Describe the look in a local session in the Code tab. The docs’ example is
make a mod that makes the app cream in light mode and dark brown in dark mode. Claude writes the mod into the session’s mods folder,~/.claude/dev-mods/and the session’s ID. In the default and accept-edits modes you approve each file, then answer whether to turn on hot reloading; in auto and bypass-permissions modes it can load without asking. A mod Claude writes loads only in the session that made it, and Claude Code deletes that folder aftercleanupPeriodDays, so copy it somewhere of your own to keep it. - Write one. The docs build a colors theme with
makeColors, a helper from Claude Code’s built-in plugin-authoring skill that turns a few hex colors into a full palette, and a backdrop with aui.renderhook onBackdrop. Pass colors and backdrop in the same$.theme.setcall, and use one theme mod at a time.
The terminal has its own, older system. In /theme, New custom theme… builds one, saved as a JSON file in ~/.claude/themes/ with a name, a base preset such as dark, and overrides for individual colors, as the terminal docs describe. It changes colors only.
Why a theme may not show
Theme-examples covers its own case: a new session, or one after /clear, shows no theme until you send a message. Beyond that, people running Desktop 5.11492.5 with Claude Code 2.1.325 reported three problems on GitHub on November 14, and Anthropic hasn’t replied to them yet:
- A scene hidden behind solid glass. In issue 109853, a Windows user found the scene drawn but covered: with Settings > Personalization > Colors > Transparency effects off, the app makes the glass fully opaque. Their workaround is to turn the setting on. In issue 109844, a Mac user found the same with System Settings > Accessibility > Display > Reduce transparency on. The rule they found applies to high-contrast modes too.
- Scenes that don’t move. Issue 109766 reports scenes drawn as still pictures on macOS, though another user says they animate on theirs. If your system asks for reduced motion, theme-examples rests every scene in a still picture on purpose.
- Picture backgrounds refused. JPEG and PNG backdrops don’t draw on Windows or macOS, and the app logs that the mod’s backdrop “holds a value outside ThemeGround.” Gradients work.
Two more causes, from the docs: on Desktop 5.11492.5 or earlier with a third-party provider instead of a Claude account, the Code tab keeps its own colors, and any other mod that sets or clears a theme takes yours off.
What a theme can reach
A theme that only paints needs little, but a mod gets everything. Anthropic’s mods overview warns: “A mod is code that runs with your permissions. It can read and write your files, start processes, and make network requests.” It can read environment variables and settings files, “including an API key you keep in either,” see every prompt and tool call, approve a tool call before you’re asked, and call a model on your plan. “Mods aren’t sandboxed,” and turning on Claude Code’s sandbox doesn’t contain them. A mod can’t change what a permission prompt shows.
On Team and Enterprise logins, and on computers with managed settings, a built-in guard stops a user’s mod from approving calls that your deny or ask rules would stop, and administrators can block users’ own mods with allowManagedModsOnly. Everywhere else, check a theme before you install it. With its files on your computer, claude plugin validate ./the-theme lists the events it hooks and the calls it makes without running it. Anthropic’s own examples use session.start and, for a scene, a ui.render hook on Backdrop; calls such as $.fs.read, $.process.run, $.http.fetch or $.env.get need a reason. Theme-examples hooks your sessions’ start, your prompts and Claude’s replies, but says it reads no prompt text, scans replies only for “merged,” keeps none of it, and “sends nothing anywhere.”
How to remove one
For theme-examples, /custom-theme off clears the project’s theme and /custom-theme off session clears only the session’s. For any other theme, turn its mod off first, because a mod that’s still on sets its colors again. Disable or uninstall its plugin, or move the folder Claude wrote out of the mods folder, then start a new local session. If colors stay, the docs say to open Settings from the Code tab, search for code appearance, and select Remove colors.
What Anthropic hasn’t said
- When cloud sessions get themes. Only that it’s “coming soon.”
- When the reported bugs will be fixed, or whether reduced transparency will keep a scene visible.
- Whether any themes will be maintained. Theme-examples is an example, by its own pull request, and we found no set of themes Anthropic says it will keep up.
Themes in apps that run Claude Code
Apps that drive Claude Code through claude -p or the Agent SDK don’t draw mods. Anthropic’s table says a mod’s hooks run there, but nothing it draws appears, so a theme changes nothing in their windows. Enjoy is one of those apps: it runs the copy of Claude Code on your computer, on the Claude plan you already have, through its print mode. A theme you installed for Claude Code still loads there, and so does whatever else that mod does.
Enjoy has a theme system of its own instead. You ask JOY, Enjoy’s assistant, for a look, such as “warmer, like a coffee shop at night,” and Enjoy wears it at once. Its themes can change only colors, type, corners and shadows, and the desktop app can put a moving background behind the window. Because the look is Enjoy’s, it’s the same whichever agent you’re talking to.
9.Questions.
How do I add a custom theme to Claude Code on desktop?
- Update the Claude Desktop app and open a local session in the Code tab. Then install Anthropic’s theme-examples plugin and run /custom-theme to pick one of its twenty scenes, or describe the look you want and Claude writes a mod for it. New colors need Claude Code 2.1.324 or later in the Code tab; /status shows yours.
Why isn’t my Claude Code theme showing?
- First send a message, because a new session shows no theme until you do. If a scene still doesn’t appear, users on GitHub traced it to Windows’ Transparency effects being off or macOS’s Reduce transparency being on, which turn the glass over the scene solid. Desktop 5.11492.5 also has open bugs with still scenes on some Macs and refused JPEG and PNG backgrounds.
Do Claude Code themes work in the terminal?
- Not these. Anthropic’s docs say “The terminal draws no backdrop” and that Claude Code in the terminal keeps its own colors. The terminal has its own custom themes, color-only JSON files you make with /theme and New custom theme…, saved in ~/.claude/themes/.
Are Claude Code themes safe to install?
- Only from authors you trust. A theme is a mod, and Anthropic’s docs say a mod “runs with your permissions. It can read and write your files, start processes, and make network requests.” Run claude plugin validate on a theme before you install it to list what it hooks and calls. Anthropic’s theme-examples says it “sends nothing anywhere.”
How do I remove a Claude Code theme?
- For theme-examples, run /custom-theme off. For another mod, turn it off or uninstall it, start a new session, and if colors stay, open Settings in the Code tab, search for “code appearance” and select Remove colors.