[FEATURE] Terminal font family setting in desktop app

Status Fixed / completed
Maintainer reply None cached
Activity 12 comments · opened Apr 15, 2026 · closed Aug 25, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The Code tab in Claude Desktop uses a fixed font with no way to change it. If you use Oh My Zsh with a theme that needs Nerd Font glyphs (Powerlevel10k, Starship, etc.), the terminal shows broken squares instead of the actual icons.

The font is installed and works in every other terminal on the system. The desktop app just doesn't pick it up.

Related issues cover font size (#48237) and dyslexic-friendly fonts (#40469), but none ask for font family selection.

Proposed Solution

A "Terminal font family" text field in Settings > Appearance. Just needs to accept a CSS font-family string so xterm.js uses the right font. No picker needed.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

Screenshot showing broken Nerd Font glyphs in the integrated terminal:

<img width="538" height="116" alt="Image" src="https://github.com/user-attachments/assets/629b0ad4-3da3-46da-820f-1b99ff98cc35" />

View original on GitHub ↗

12 Comments

greghesp · 6 months ago

I'd also agree here, but purely on the basis that the font is illegible for me. If we compare MacOS native terminal against the one in Claude Code, one you start adding errors, symbols etc, its too difficult to read

<img width="368" height="188" alt="Image" src="https://github.com/user-attachments/assets/aebbabfe-6d41-4e90-9d55-1bf8575dbf9e" />

juhguu · 6 months ago

Yes. Especially in light themes, the font rendering in the Claude Code Desktop terminal looks terrible.
Harsh and hard to read.
<img width="450" height="298" alt="Image" src="https://github.com/user-attachments/assets/71f5b174-d067-4461-b6eb-aa38b8714c47" />

nicolaschapados · 5 months ago

Upvoting this request 👍

jaredalonzo · 5 months ago

Upvoting this request as well! This would be great so I can use neovim in the Terminal panel within the claude code app

keith555 · 5 months ago

The font is terrible. It looks like a typewriter with a worn-out ribbon,

<img width="480" height="80" alt="Image" src="https://github.com/user-attachments/assets/eb300de5-21c1-4af1-9f04-c64540570f76" />

Celggar · 4 months ago

+1 on this request.

My setup:

  • macOS, Claude.app desktop (v2.1.158)
  • Powerlevel10k with MesloLGS NF Regular 12pt
  • Font is installed at ~/Library/Fonts/MesloLGS NF Regular.ttf and works perfectly in macOS Terminal.app (the default terminal)

Confirmed behavior: The font IS installed system-wide but Claude.app's integrated terminal ignores it and falls back to a default monospace font, rendering Powerlevel10k icons as broken squares.

Workaround I'm using: Launching claude . from macOS Terminal.app instead of using the built-in terminal tab — works perfectly there.

The proposed fix (a font-family field in Settings > Appearance) would be ideal. Even just reading from a config key in ~/.claude/settings.json like "terminalFontFamily": "MesloLGS NF" would solve this for power users.

LiorRonen · 3 months ago

<img width="402" height="286" alt="Image" src="https://github.com/user-attachments/assets/478cb5db-9fa7-4d96-96c1-44db827068b0" />

<img width="289" height="274" alt="Image" src="https://github.com/user-attachments/assets/86a47f11-8920-414a-ba09-d0dac2231001" />

I cannot use Windows Claude Desktop because of the fonts, they look terrible (see attached first image).
Would love to have the option to use the Courier New font (see second image from Claude via browser) and also an option to set the font size. Maybe even via CSS.

Thanks!

55Cancri · 3 months ago

Please allow us to customize the fonts in claude desktop terminal

tmarkovski · 3 months ago

Please add customization for terminal font, it is currently unusable in certain scenarios.

mjeragh · 2 months ago

Update for anyone still subscribed: the setting asked for here has shipped, but it doesn't reach the terminal.

Settings → Code appearance → Code font says it sets the font "for code and terminal." It applies to code blocks and diffs only — the terminal hardcodes fontFamily: '"SF Mono", ui-monospace, Menlo, Consolas, monospace' at its call site and never reads the configured value, so Nerd Font glyphs still render as tofu.

I traced it to the exact call site and filed it with a suggested one-line fix in #82205.

tmarkovski · 2 months ago
Update for anyone still subscribed: the setting asked for here has shipped, but it doesn't reach the terminal. Settings → Code appearance → Code font says it sets the font "for code and terminal." It applies to code blocks and diffs only — the terminal hardcodes fontFamily: '"SF Mono", ui-monospace, Menlo, Consolas, monospace' at its call site and never reads the configured value, so Nerd Font glyphs still render as tofu. I traced it to the exact call site and filed it with a suggested one-line fix in #82205.

Doing lord's work.

MizuMate · 1 month ago

Settings > Appearance > Chat font changes the typeface in Chat and Cowork, but the Code tab ignores it entirely and stays on a fixed font. The result is that within the same app, on the same screen, switching tabs changes the typeface with no way to align them. For anyone using Desktop as their main daily surface (not just for the terminal/Nerd Font use case), this reads as an inconsistency in the app itself, independent of any terminal font-glyph requirements.

A "Terminal font family" field would fix the glyph problem. It wouldn't fix this one unless the Code tab can also just inherit the Chat font setting by default. Would be great if the fix covered both:

  • A font family override for the Code tab (for Nerd Font / custom glyph needs)
  • The Code tab respecting the existing Chat font setting when no override is set (for everyone who just wants one consistent typeface across the app)

Happy to test on Windows if a build with either option lands.