Cap CDP supervisor reconnect retries after dead endpoint

NousResearch/hermes-agent · cluster 114172

Data as of

Nothing open on GitHub. Fix merged in #114897. Check it covers your case.

The short answer

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

These issues and PRs address an unbounded reconnect loop in the browser CDP supervisor that triggers excessive warnings when an endpoint dies. The proposed fix limits reconnect attempts to prevent the infinite retry cycle.

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.

  • #114897 fix(browser): CDP supervisor stops retrying a dead endpoint after 5 failed reconnects (#114172, salvage #114178)

    merged to main

    files: tests/tools/test_browser_supervisor_reconnect.py, tools/browser_supervisor.py, website/docs/developer-guide/browser-supervisor.md

4 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1 · other 2

  • #114178 fix(browser): bound CDP supervisor reconnects · merged via another change → aefa503, #114897, #114172, #114178
  • #114179 fix(browser): cap supervisor reconnects after a dead CDP endpoint · other → #114178, #114172, #44460
  • #114200 fix: cap CDPSupervisor post-attach reconnect retries to prevent unbounded loop · superseded by another PR → aefa503, #114897, #114172, #114178
  • #114207 fix(browser): bound CDP supervisor reconnect lifetime · other → #114897
Closed issues · 1
  • Closed#114172browser_supervisor: unbounded reconnect loop after the CDP endpoint dies (1,600+ warnings from a finished cron session)
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.33: 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

Merged PRs
#114897
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.