Cairn

Terminal fence markers leaking into file content

NousResearch/hermes-agent · cluster 3587 · environments

Data as of

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

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #19426. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #19426. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where heredoc or oneshot terminal execution causes internal fence/wrapper markers (HERMES_FENCE) to bleed into file content, silently corrupting files. Multiple fix attempts address this from both the terminal and file-read sides.

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.

  • #19426 fix(file): strip leaked terminal fences from reads

    merged to main

    files: tests/tools/test_file_operations.py, tools/file_operations.py

2 PRs closed without merging

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

  • #3613 fix(terminal): prevent fence wrapper from bleeding into heredoc content · other
  • #19266 fix(file): strip leaked terminal fences from reads · merged via another change → #19426
Closed issues · 2
  • Closed#3587[Bug]: terminal tool corrupts files when using heredoc syntax - shell wrapper artifacts bleed into file content
  • Closed#5400[Bug]: HERMES_FENCE markers leak into file content via ShellFileOperations — corrupts source files silently
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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

Subsystem
environments
Merged PRs
#19426
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
3 May 2026

For your agent

The same facts, typed.

cluster/3587.json
cluster/3587.md