Windows CLI Unicode symbol rendering issues
NousResearch/hermes-agent · cluster 24277 · hermes cli
Data as of
5 open items. Fix attempted, not merged.
The short answer
3open issues
2open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 3 issues and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and fixes concern Unicode or special symbols displaying as tofu or question marks in Windows terminals, with proposed fallbacks to ASCII display on Windows MSYS environments.
Open issues3
- Issue#24277[Windows] Special symbols before yellow-colored text displayed as question marks
- Issue#24278Symbols/icons before yellow headers in conversation appear as question marks
- Issue#67151[Enhancement] Hermes CLI / Desktop uses Unicode symbols not available in Windows 10 default fonts — displays as tofu (□)
Open PRs2
1 PR closed without merging
From the close comments: other 1
- #83759 fix(cli): fall back to ascii display on windows msys · other
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.31: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- hermes cli
- Closed issues
- 0
- Attempts
- 1 PR closed without merging