Problem
The integrated thread terminal uses a fixed font stack that ends at the generic monospace fallback. On Linux, prompts that use Powerline or Nerd Font glyphs can render as boxes or unknown characters even when a Nerd Font is installed, because the stack does not name common Nerd Font families.
Expected behavior
The terminal should keep the existing default font preference, but fall back to installed Nerd Font families for prompt glyphs when the default fonts do not cover them.
Scope
This is not a request for a configurable terminal font setting. PR #1572 was closed because a broader appearance system is planned; this issue is only about a small fallback-only bug fix for missing terminal glyphs.
Proposed fix
Add common Nerd Font families before the final generic monospace fallback in the xterm font stack used by ThreadTerminalDrawer.
Validation
A local source patch was checked with bun fmt, bun lint, and bun typecheck using Bun 1.3.9 and Node 24.13.1.
Problem
The integrated thread terminal uses a fixed font stack that ends at the generic
monospacefallback. On Linux, prompts that use Powerline or Nerd Font glyphs can render as boxes or unknown characters even when a Nerd Font is installed, because the stack does not name common Nerd Font families.Expected behavior
The terminal should keep the existing default font preference, but fall back to installed Nerd Font families for prompt glyphs when the default fonts do not cover them.
Scope
This is not a request for a configurable terminal font setting. PR #1572 was closed because a broader appearance system is planned; this issue is only about a small fallback-only bug fix for missing terminal glyphs.
Proposed fix
Add common Nerd Font families before the final generic
monospacefallback in the xterm font stack used byThreadTerminalDrawer.Validation
A local source patch was checked with
bun fmt,bun lint, andbun typecheckusing Bun 1.3.9 and Node 24.13.1.