NousResearch/hermes-agent

surrogateescape handling in local file write paths

Cluster 79178. Data as of

Nothing open on GitHub. Fix merged in #81964. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #81964. 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.

These items concern a bug where surrogate-escaped bytes cause failures during local environment file writes. The work involves making file writes surrogateescape-safe while rejecting genuinely unencodable surrogates.

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.

  • #81964 fix(agent,gateway): lone-surrogate chokepoints \u2014 sanitize once at model-text exit and outbound assembly

    merged to main

    files: agent/conversation_loop.py, agent/turn_finalizer.py, contributors/emails/[redacted:email], gateway/run.py, hermes_cli/oneshot.py, tests/agent/test_surrogate_chokepoints.py, tests/hermes_cli/test_oneshot_surrogate.py, tests/tools/test_file_write_surrogate_roundtrip.py, tests/tools/test_process_registry_write_stdin_surrogates.py, tools/environments/base.py, tools/file_operations.py, tools/process_registry.py

3 PRs closed without merging

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

  • #79218 fix(tools): preserve surrogateescape bytes in local writes · superseded by another PR → #79234
  • #79234 fix: surrogateescape-safe file writes, reject unencodable surrogates (#79178) · other
  • #79240 fix: surrogateescape-safe file writes, reject unencodable surrogates (#79178) · merged via another change → #81964
Closed issues · 1
  • Closed#79178[Bug]: surrogateescape content fails in the real LocalEnvironment write path
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.40: 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
#81964
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
8 Aug 2026

For your agent

The same facts, typed.