Cairn

Stale browser_harness daemons left running after browser_exec

NousResearch/hermes-agent · cluster 121095 · 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.

One issue reports that browser_exec can leave stale browser_harness daemon processes running after completion. Two pull requests propose changes to the browser tooling to stop or reap these daemons, one using an owner lease and one covering every exit path including a killed owner.

Open issues1

  • Issue#121095browser_exec leaves stale browser_harness daemon processes running after completion

Open PRs2

  • PR#129655fix(browser): stop browser_exec harness daemons on every exit path, including a killed owner
  • PR#140088fix(browser): reap browser-harness daemons by owner lease
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.

cluster/121095.json
cluster/121095.md