Cairn
NousResearch/hermes-agent

read_file masking real errors as File Not Found

Cluster 44750 · agent. Data as of

3 open items. Fix merged in #103678 on 5 Sep 2026. Check it covers your case.

The short answer

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

A bug where read_file and related tools incorrectly report 'File not found' when the actual cause is an interrupted read or environment/exec failure. Multiple fixes aim to preserve and surface the true underlying error.

Open issues1

  • Issue#63069read_file falsely reports "File not found" when interrupted mid-read (wc -c subprocess killed on SSE disconnect)

Open PRs2

  • PR#44753fix(tools): report environment failures instead of 'File not found' in read_file/search
  • PR#63090fix(file): preserve interrupted read errors

Fixes on record

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

  • #103678 fix(tools): a sandbox that cannot exec is reported as 'environment unavailable', not a false 'File not found' (#44750, salvage #44753)

    merged to main

    files: contributors/emails/[redacted:email], tests/tools/test_file_ops_env_not_ready.py, tools/file_operations.py

2 PRs closed without merging

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

  • #44874 fix(tools): disambiguate env failure from missing file in read_file (#44750) · other
  • #63084 fix(tools): don't report interrupted read_file as File not found (#63069) · superseded by another PR → b1ea9bc, #44750, #63069
Closed issues · 1
  • Closed#44750[Bug]: read_file/search_files report 'File not found' for existing files when the docker env isn't ready (exec failure conflated with missing file)
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.26: 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
#103678
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
5 Sep 2026

For your agent

The same facts, typed.

cluster/44750.json
cluster/44750.md