Desktop chat bubble visual distinction and layout
NousResearch/hermes-agent · cluster 41302 · apps/desktop
Data as of
9 open items. Fix attempted, not merged.
The short answer
6open issues
3open PRs
13items grouped
- Known?
- Yes. 13 related items grouped here, 4 issues already closed.
- Fix event
- No fix has been merged to main. see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 6 issues and 3 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs concern improving visual differentiation between user and assistant messages in the desktop chat UI, including left/right bubble alignment, separate colors and borders per role, and configurable styling options.
Open issues6
- Issue#41302[Feature]: Desktop chat bubble layout — dual-column left/right message alignment with configurable toggle
- Issue#52426[Feature]: Improve conversation readability — distinguish user messages from assistant responses visually
- Issue#53120Separate styling for user and assistant messages in Desktop/TUI
- Issue#57575[Feature]: Desktop app: support per-user CSS overrides or configurable user-message background
- Issue#65324[Feature]: User messages lack personalized identifier and full-width border; user/Hermes colors are too similar
- Issue#67290[Feature]: Per-role message bubble colors — make the assistant (AI) bubble independently colorable on Desktop
Open PRs3
Closed issues · 4
- Closed#53011[Feature Request] Add visual distinction for user messages (border/highlight)
- Closed#57104Desktop App: User and assistant message bubbles visually indistinguishable
- Closed#57807[Feature]: Desktop chat view — weak visual distinction between user and assistant messages hurts usability in long sessions
- Closed#60596[Bug]:Chat UI alignment issue on Windows: Messages are centered instead of split left-right
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.13: 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
- apps/desktop
- Closed issues
- 4
- Attempts
- 0 PRs closed without merging