NousResearch/hermes-agent

Fix orphaned execute_code processes after session reset

Cluster 8523 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

A bug report and two fixes addressing the issue where /reset fails to stop in-flight code execution, leaving orphaned subprocesses and stale responses after the session resets.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #8545 fix(gateway): discard orphaned execute_code responses after reset · done elsewhere → 4b6ff0e, #8581
  • #8581 fix(execute_code): register subprocess with process_registry for immediate kill on /reset · done elsewhere → b7bdf32
Closed issues · 1
  • Closed#8523[Bug] /reset does not stop in-flight execute_code — orphaned response written after session reset
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.