Docker sandbox path mismatch for spilled tool results

NousResearch/hermes-agent · cluster 121024 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items address a bug where spilled tool results are announced using the host filesystem path rather than the sandbox-visible path, causing tools like read_file and execute_code to fail when the Docker sandbox has not yet been initialized. The fixes involve correcting the announced path and ensuring the sandbox is initialized before spilling occurs.

Open issues1

  • Issue#121024[Bug]: spilled tool result announced by host path when the Docker sandbox doesn't exist yet — read_file/execute_code can't find it

Open PRs2

  • PR#121029fix(agent): initialize Docker sandbox before spilling tool results
  • PR#121592fix(tools): announce env=None spills by the sandbox-visible path (#121024)
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.67: 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
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.