Cairn
NousResearch/hermes-agent

Tool call ID duplication after context compression on strict providers

Cluster 58327. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this resolved, deciding PR #58350. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members center on one theme: context compression or compaction can leave the tool message chain invalid, with an error about 'tool' messages needing a preceding 'tool_calls' message, or with duplicate tool_call_ids on strict providers. One is a bug report and the others are pull requests proposing deduplication of tool_call_ids, with two having identical titles.

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.

  • #58350 fix(agent): deduplicate tool_call_id across pre-API sanitizers (#58327)

    merged to mainSuggested link · files and diff not shown

3 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1 · other 1

  • #58362 fix(agent): dedup duplicate tool_call_id after compaction (#58327) · duplicate → #58350, #58327
  • #60270 fix(compression): dedup duplicate tool_call_ids to prevent HTTP 400 on strict providers · other
  • #60398 fix(compression): dedup duplicate tool_call_ids to prevent HTTP 400 on strict providers · done elsewhere → dba585c, #58350, #58327
Closed issues · 1
  • Closed#58327[Bug]: Context compression breaks tool message chain, causing "role 'tool' must be a response to a preceding message with 'tool_calls'" on strict providers
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

Merged PRs
#58350
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/58327.json
cluster/58327.md