hermes - 💡(How to fix) Fix Workspace UI: Context alert modal points to non-existent "Settings → Config" [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#15677Fetched 2026-04-26 05:25:53
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Code Example

Connection
Model & Provider
Agent Behavior
Smart Routing
Voice
Display
Appearance
Chat
Notifications
MCP Servers
Language

---

compression:
  enabled: true
  threshold: 0.5
  target_ratio: 0.2
  protect_last_n: 20
RAW_BUFFERClick to expand / collapse

Bug Report

Severity: Medium — User confusion, no functional breakage but misleading guidance

Component: Hermes Workspace (Web UI)


What the user sees

In the Workspace chat interface, when context usage reaches ~35%, a warning modal appears with this recommendation:

🗜️ Enable auto-compaction in Settings → Config to automatically manage context

The "Settings → Config" link is clickable ( /settings ) and leads to the Settings page.


Actual behavior (current code)

The Settings page (src/routes/settings/index.tsx) sidebar shows these sections:

Connection
Model & Provider
Agent Behavior
Smart Routing
Voice
Display
Appearance
Chat
Notifications
MCP Servers
Language

There is no "Config" section — the sidebar item is SETTINGS_NAV_ITEMS and does not include "Config".

Expected behavior

The modal should direct users to the correct location, OR auto-compaction should be controllable from the Settings UI, OR the message should be updated to reflect that auto-compaction is controlled via ~/.hermes/config.yaml.

Current state of auto-compaction

Auto-compaction exists and works — it's configured via compression: section in ~/.hermes/config.yaml:

compression:
  enabled: true
  threshold: 0.5
  target_ratio: 0.2
  protect_last_n: 20

There is no Workspace UI toggle for this feature. The modal message is a holdover from an earlier design where compaction settings lived in a "Config" section.


Recommended fix (choose one)

Option A (minimal): Update the modal message to say:

"Auto-compaction is configured via ~/.hermes/config.yaml under the compression: section. Edit the config file directly to adjust threshold, target ratio, or disable it."

Option B (UI feature): Add a "Compression" or "Advanced" section to Settings that exposes the compression: config keys (enabled, threshold, target_ratio, protect_last_n, summary_model) as form controls that write to config.yaml via the /api/hermes-config endpoint.

Option C (merge): Change the link destination to point directly to the "Agent Behavior" section (since compression is an agent-level config) and add a note that it's configured in the config file.


Reproduction steps

  1. Open Hermes Workspace (port 3000)
  2. Have a long conversation that uses >35% of context window
  3. Observe the context alert modal
  4. Note the "Settings → Config" recommendation
  5. Navigate to Settings — observe no "Config" tab exists
  6. Auto-compaction itself does work (based on config.yaml), but users cannot manage it via UI

Environment

  • Hermes Agent version: v0.8.0 (from /home/ubuntu/.hermes/hermes-agent directory)
  • Workspace version: current outsourc-e/hermes-workspace (latest)
  • Browser: Any
  • Platform: Linux (WSL2)

Attaching: Screenshot of the modal + Settings sidebar would normally be included.

Reported by: Frank Cona (user) Date: 2026-04-25

extent analysis

TL;DR

Update the modal message to accurately reflect how auto-compaction is configured, either by directing users to edit the ~/.hermes/config.yaml file or by adding a UI control for compression settings.

Guidance

  • Verify the issue: Confirm that the modal message is misleading by checking the Settings page for a "Config" section and verifying that auto-compaction settings are not exposed in the UI.
  • Choose a fix approach: Decide between updating the modal message to point to the config file, adding a UI control for compression settings, or changing the link destination to the "Agent Behavior" section with a note about config file configuration.
  • Implement the chosen fix: For Option A, update the modal message as recommended; for Option B, add a "Compression" section to Settings with form controls that write to config.yaml; for Option C, update the link and add a note about config file configuration.
  • Test the fix: After implementing the chosen solution, reproduce the steps to trigger the modal and verify that the message is accurate and helpful, and that any new UI controls function as expected.

Example

No code example is provided as the issue does not require a specific code change but rather a decision on how to address the misleading modal message.

Notes

The choice between the recommended fixes (Option A, B, or C) depends on the desired user experience and the priority of adding UI controls for auto-compaction settings. Option A is the most straightforward and minimal change, while Option B provides a more integrated user experience.

Recommendation

Apply workaround Option A: Update the modal message to say "Auto-compaction is configured via ~/.hermes/config.yaml under the compression: section. Edit the config file directly to adjust threshold, target ratio, or disable it." This is the most straightforward fix that immediately addresses the misleading guidance without requiring additional UI development.

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

The modal should direct users to the correct location, OR auto-compaction should be controllable from the Settings UI, OR the message should be updated to reflect that auto-compaction is controlled via ~/.hermes/config.yaml.

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 - 💡(How to fix) Fix Workspace UI: Context alert modal points to non-existent "Settings → Config" [1 participants]