NousResearch/hermes-agent

Camofox stale tab recovery for HTTP 410 Gone

Cluster 80276 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These members address a bug where Camofox stale tabs are not recovered on HTTP 410 Gone responses, causing browser tools to become unresponsive. A fix is proposed or applied to handle this specific HTTP status during stale-tab recovery.

Open issues1

  • Issue#80276[Bug]: Camofox stale-tab recovery misses HTTP 410 Gone — browser_* tools wedge until Hermes restart

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1

  • #80298 fix(browser): recover Camofox stale tabs on HTTP 410 Gone · superseded by another PR → b5e999a, #93249
  • #93249 fix(browser): recover Camofox stale tabs on HTTP 410 Gone · done elsewhere
  • #138432 fix(camofox): recover from stale-tab 410 Gone after a server restart · superseded by another PR → #85538, #80276
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.50: 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
3 PRs closed without merging

For your agent

The same facts, typed.