Cairn

tool_call handling of directly-listed tools instead of refusing

NousResearch/hermes-agent · cluster 137639 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These members concern the case where tool_call names a tool that is already listed directly, which is reported as being refused and costing an iteration. Two pull requests propose different approaches: dispatching the call directly, or echoing a ready-to-reissue direct call.

Open issues1

  • Issue#137639tool_call naming a directly-listed tool is refused instead of dispatched (1 wasted iteration per hit)

Open PRs3

  • PR#137642fix(tools): dispatch directly-listed bridge calls
  • PR#137643fix(tools): echo a ready-to-reissue direct call when tool_call names a directly-listed tool
  • PR#137817fix(tools): dispatch a directly-listed tool from tool_call instead of refusing
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/137639.json
cluster/137639.md