Cairn
NousResearch/hermes-agent

web_extract and browser routing issues

Cluster 43099 · 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.

These members concern problems with how web extraction is routed between the DDGS package and a Chromium browser, including a fix to enable DDGS-based extraction, a fix to redirect explicit browser tasks away from web_extract, and a user report of Chromium access breaking and falling back to a failing DDGS web_extract.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #43352 fix(browser): steer explicit browser tasks away from web_extract · other
  • #47001 fix(web/ddgs): enable web_extract via the ddgs Python package · superseded by another PR → #84104
Closed issues · 1
  • Closed#43099My Hermes lost its hability to use chromium and defaults to DDGGS web_extract that fails.
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.

cluster/43099.json
cluster/43099.md