claude-code - 💡(How to fix) Fix Status bar UI icons render as tofu in kitty terminal despite font support [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46841Fetched 2026-04-12 13:31:39
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4

Private Use Area Unicode glyphs (e.g. the ▸▸ play icons in the status bar) render as tofu/missing glyphs in the status bar when running Claude Code inside kitty terminal.

However, the same glyphs render correctly in the main text body (markdown output area) of Claude Code. This proves the terminal and font are capable of rendering these characters — the issue is specific to the status bar rendering.

Root Cause

Private Use Area Unicode glyphs (e.g. the ▸▸ play icons in the status bar) render as tofu/missing glyphs in the status bar when running Claude Code inside kitty terminal.

However, the same glyphs render correctly in the main text body (markdown output area) of Claude Code. This proves the terminal and font are capable of rendering these characters — the issue is specific to the status bar rendering.

RAW_BUFFERClick to expand / collapse

Description

Private Use Area Unicode glyphs (e.g. the ▸▸ play icons in the status bar) render as tofu/missing glyphs in the status bar when running Claude Code inside kitty terminal.

However, the same glyphs render correctly in the main text body (markdown output area) of Claude Code. This proves the terminal and font are capable of rendering these characters — the issue is specific to the status bar rendering.

Environment

  • Claude Code v2.1.101
  • Terminal: kitty 0.42.2 (running on WSL2/WSLg, linux_display_server x11)
  • Font: RictyDiscord Nerd Font (includes full Nerd Fonts / Powerline glyphs)
  • OS: Ubuntu 24.04 on WSL2

Screenshots

Windows Terminal — status bar renders correctly

Windows Terminal - OK

kitty — status bar icons are tofu

kitty - tofu

kitty — same glyphs render fine in the main text body

kitty - body OK

What I've tried

  • Setting font_family in kitty.conf to RictyDiscord Nerd Font
  • Adding symbol_map for Private Use Area ranges (U+E0A0-U+E0D4, U+E700-U+E7C5, U+F000-U+F2E0, etc.)
  • Neither had any effect on the status bar rendering

Expected behavior

Status bar UI icons should render using the terminal's configured font, the same way the main text body does.

extent analysis

TL;DR

The issue can be resolved by configuring kitty to properly handle Private Use Area Unicode glyphs in the status bar, potentially by adjusting font settings or symbol mapping.

Guidance

  • Verify that the font_family setting in kitty.conf is correctly set to RictyDiscord Nerd Font and that the font is properly installed and accessible to kitty.
  • Check if there are any specific settings or configurations in kitty that need to be adjusted to handle Private Use Area Unicode glyphs in the status bar, such as modifying the symbol_map or adding custom font settings.
  • Consider testing with a different font that includes the necessary glyphs to see if the issue is font-specific.
  • Review the kitty documentation and configuration options to ensure that all relevant settings are properly configured for Unicode glyph rendering.

Example

No specific code example is provided as the issue seems to be related to configuration and font settings rather than code.

Notes

The issue appears to be specific to the status bar rendering in kitty, and the fact that the same glyphs render correctly in the main text body suggests that the terminal and font are capable of rendering these characters. The solution will likely involve adjusting kitty's configuration to properly handle Private Use Area Unicode glyphs in the status bar.

Recommendation

Apply workaround: Adjust kitty's configuration settings, such as font_family and symbol_map, to properly handle Private Use Area Unicode glyphs in the status bar, as the issue seems to be related to configuration rather than a version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Status bar UI icons should render using the terminal's configured font, the same way the main text body does.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING