Cairn

File write reliability and CWD preservation bugs

NousResearch/hermes-agent · cluster 26211 · agent

Data as of

Nothing open on GitHub. Fix merged in #53920. 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 #53920. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #53920. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes address silent file creation failures during long conversations and loss of the current working directory when terminal environments are recreated. Both themes involve file operation reliability on the local filesystem.

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.

  • #53920 fix(file-ops): preserve CWD across terminal env re-creation (#26211)

    merged to main

    files: tests/tools/test_file_tools.py, tests/tools/test_file_tools_cwd_resolution.py, tools/file_tools.py

2 PRs closed without merging

From the close comments: merged via another change 1 · partial fix 1

  • #26251 fix(file-ops): preserve CWD across terminal environment re-creation (#26211) · merged via another change → adeba1d, #53920
  • #26336 fix(file): verify file exists after write to prevent silent failures in long conversations · partial fix → #39066
Closed issues · 2
  • Closed#26211[Bug]: File creation fails silently in long-running conversations
  • Closed#34395[Bug]: can't create txt, html output in target folder (or anyway Mac could search)
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
agent
Merged PRs
#53920
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
28 Jun 2026

For your agent

The same facts, typed.

cluster/26211.json
cluster/26211.md