Nothing open on GitHub. Fix merged in #106313 on 9 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #106313. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #106313. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items relate to a bug where conversation history is dropped or not properly resumed, and fixes targeting the --resume flag behavior in one-shot mode. The issues span both CLI flag handling and provider-level history management.
Open issues0
Open PRs0
Fixes on record
-
#106313 fix(cli): `hermes -z --resume` continues the session instead of starting a fresh one (#105892; salvage #105957)
files:
hermes_cli/cli_model_switch_mixin.py,hermes_cli/main.py,hermes_cli/oneshot.py,tests/hermes_cli/test_oneshot_resume.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#105957 fix(cli): honor --resume in one-shot mode (hermes -z) · done elsewhere →
#106313
Closed issues · 1
- Closed#105892[Bug] Custom/OpenAI-compatible provider (Ollama): conversation history is dropped - each turn sends only [system, current user]
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: 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
- Merged PRs
- #106313
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 9 Sep 2026