NousResearch/hermes-agent

Fix web_extract URL-to-result positional matching bug

Cluster 97378. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #112245 on 16 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #112245, then check it covers your case.

Read #112245 Pick up a Lab task

A bug caused web_extract to associate provider results with requested URLs by position rather than by URL, meaning reordering or partial failures could poison the cache with mismatched content. These changes fix the matching logic to use URL identity instead of positional order.

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.

#112245 fix(web): web_extract caches each page under its own requested URL, never by batch position (#111803, #97378, salvage #111806)

merged to main

files: plugins/web/tavily/provider.py, tests/tools/test_web_tools_tavily.py, tools/web_tools_extract.py, website/docs/user-guide/features/web-search.md

2 PRs closed without merging

From the close comments: merged via another change 2

#96859 fix(web): match extract results to requested URLs instead of by position · merged via another change → 7935294, #112245
#97430 fix(web_extract): match provider results to URLs by URL instead of position · merged via another change → 7935294, #112245

Closed issues · 1

Closed#97378[Bug]: web_extract associates provider results with requested URLs by position — reorder/failure poisons the extract cache

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

Merged PRs: #112245
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/97378.json
cluster/97378.md