Hermes Classic CLI Ignores Memory-Notification Settings and Per-Platform Overrides (#64736)
Bug Tracker — July 15, 2026. A reported configuration-parity defect makes classic terminal sessions ignore the memory-notification setting and any per-platform CLI override, while messaging gateway and TUI behavior follows the setting.
Issue Summary
Issue #64736 reports that display.memory_notifications: off is honored by the messaging gateway and TUI but not by classic hermes or hermes chat. Terminal sessions reportedly use AIAgent’s hardcoded on default and print self-improvement review summaries regardless of the configured global or per-platform CLI value. A linked PR #64737 is intended to address the discrepancy.
Observed Failure Path
| Step | Reported Behavior | User-Level Consequence |
|---|---|---|
| Operator disables notifications | display.memory_notifications: off is configured, optionally with a CLI-specific override. | Operator expects the selected interface to suppress memory-review summary output. |
| Gateway and TUI execution | Reportedly honor the configured setting. | Behavior matches the declared configuration in those interfaces. |
| Classic CLI execution | hermes and hermes chat reportedly do not read the setting and retain an on default. | Terminal sessions emit summaries that the operator explicitly attempted to disable. |
| Platform override | Per-platform CLI override is also reported to be ignored. | Interface-specific configuration cannot reliably control the terminal experience. |
Operational Impact
Classification: P3. Status: Open. This page summarizes a publicly reported incident; its scope, remediation status, and reproducibility can change. Validate behavior on the relevant Hermes version, adapter, and deployment path before treating a workaround or closure as complete.
Mitigation and Verification
- Reproduce on the relevant Hermes build by setting both the global value and an explicit CLI override, then compare gateway, TUI,
hermes, andhermes chatoutput. - Record the resolved configuration source and the actual output; do not infer terminal parity from a successful gateway test.
- Track issue #64736 and PR #64737, then retest default behavior, global-off behavior, and per-platform override behavior after the fix lands.
- For production workflows where output control matters, document the current terminal limitation and use a supported interface whose setting is verified until remediation is available.
Source Evidence
Primary issue: NousResearch/hermes-agent issue #64736 (linked PR #64737)
For a managed-agent comparison, the relevant question is whether configuration settings and channel failures remain consistent, observable, and recoverable across interfaces—not only whether the happy path succeeds.