Cairn

Bound recursion depth in browser output redaction walkers

NousResearch/hermes-agent · cluster 137067 · agent

Data as of

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

The short answer

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

These members share one theme: a bug report says deeply nested page values can trigger RecursionError in the browser tool's output redaction functions (_redact_browser_output / _redact_cdp_output), and three pull requests propose bounding or capping redaction depth. The titles do not show whether any change was merged or whether the problem is still open or has been closed.

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.

  • #140562 Browser tools no longer crash on deeply nested page data (#137067, salvage #137138)

    merged to main

    files: agent/redact.py, contributors/emails/[redacted:email], tests/tools/test_browser_redact_depth.py, tools/browser_cdp_tool.py, tools/browser_tool_snapshot.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · other 1

  • #137070 fix(browser): bound output redaction depth · done elsewhere → 18c525b, 870633c, #140562
  • #137075 fix(browser): bound the redaction walkers so deep page values cannot crash them · other → #137070, #137067
  • #137138 fix(browser): cap redaction walks so nested page data cannot crash · done elsewhere → 18c525b, 440c9b6, #140562
Closed issues · 1
  • Closed#137067[Bug]: Deeply nested page value crashes the browser tool output redaction walkers with RecursionError (no depth budget on `_redact_browser_output` / `_redact_cdp_output`)
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.40: 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
Merged PRs
#140562
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
17 Oct 2026

For your agent

The same facts, typed.

cluster/137067.json
cluster/137067.md