NousResearch/hermes-agent

Fix non-ASCII data loss in turn recovery fallback

Cluster 117802. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #118313 on 21 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #118313. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #118313, then check it covers your case.

Read #118313 Pick up a Lab task

These issues and PRs address a bug where the ASCII-codec fallback during turn/unicode recovery irreversibly removes non-ASCII content from conversation history stored in session state. The fixes aim to preserve conversation history intact when handling UnicodeEncodeError conditions.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#118313 fix(agent): keep conversation history intact during ASCII-codec recovery (salvage of #117891)

merged to main

files: agent/message_sanitization.py, agent/turn_recovery.py, contributors/emails/[email protected], tests/agent/test_unicode_ascii_codec.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#117812 fix(turn-recovery): stop stripping non-ASCII from conversation content on UnicodeEncodeError · superseded by another PR → #117802, #118313, #117891, #117569
#117891 fix(agent): preserve conversation history during unicode recovery · merged via another change → d2cec3b, 1c5c712, 5460649, #118313, #117812, #117802

Closed issues · 1

Closed#117802[Bug]: Turn-recovery ASCII fallback irreversibly strips non-ASCII content from session history (state.db)

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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs: #118313
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 21 Sep 2026

For your agent

The same facts, typed.

cluster/117802.json
cluster/117802.md