hermes - ✅(Solved) Fix [Feature]: Preserve normal casing in Web Dashboard [1 pull requests, 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
NousResearch/hermes-agent#16416Fetched 2026-04-28 06:53:29
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×3cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #16522: fix(web): preserve dashboard content casing

Description (problem / solution / changelog)

Summary

  • remove the inherited uppercase transform from the dashboard shell so normal content keeps its original casing
  • keep intentional uppercase styling on sidebar navigation and system action labels
  • update the embedded chat comment now that shell casing is preserved globally

Fixes #16416

Verification

  • npm ci
  • npx tsc -b
  • npx vite build

Note: npm run build is blocked on Windows by the existing Unix-style prebuild asset script (rm/cp). npm run lint is currently blocked by unrelated pre-existing dashboard lint errors.

Changed files

  • web/src/App.tsx (modified, +3/-3)
  • web/src/pages/ChatPage.tsx (modified, +2/-2)
RAW_BUFFERClick to expand / collapse

Problem or Use Case

All content (session logs, file names, etc.) is displayed in uppercase. This makes readability and recognition more difficult.

Proposed Solution

A configuration option (theme?) to preserve normal casing would be helpful to increase readability.

Alternatives Considered

No response

Feature Type

Configuration option

Scope

None

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

Adding a configuration option to preserve the original casing of content could improve readability.

Guidance

  • Investigate existing theme or display settings to see if there's an overlooked option to control case display.
  • Consider adding a new configuration parameter specifically for case sensitivity, allowing users to choose between preserving original case or converting to uppercase.
  • Review the current implementation of content display to understand where the uppercase conversion is happening and assess the feasibility of adding case preservation.
  • Evaluate the potential impact of case preservation on other features or functionality.

Example

No specific code example is provided due to lack of implementation details in the issue.

Notes

The solution depends on the specific architecture and current implementation of the system, which is not detailed in the issue. Therefore, the guidance is focused on investigative steps rather than direct code changes.

Recommendation

Apply workaround: Implement a configuration option to preserve normal casing, as it directly addresses the readability issue mentioned and provides flexibility for users.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

hermes - ✅(Solved) Fix [Feature]: Preserve normal casing in Web Dashboard [1 pull requests, 1 participants]