Cairn
NousResearch/hermes-agent

Invalid tool-call JSON recovery keyed incorrectly

Cluster 84698 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 1 PR.

A bug was identified where invalid-JSON tool-call recovery uses the tool name as the key instead of the call ID or index, causing valid sibling calls to be incorrectly affected. The members cover the bug report and two fix approaches addressing the keying strategy.

Open issues1

  • Issue#84698[Bug] Invalid tool-call JSON recovery is keyed by tool name, not call id — a valid sibling call gets the error

Open PRs1

  • PR#84867fix(agent): key invalid-JSON tool recovery by call id, execute valid siblings

1 PR closed without merging

From the close comments: closed without comment 1

  • #84759 fix(agent): key invalid-JSON tool-call recovery by call index, not name · closed without comment
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/84698.json
cluster/84698.md