Normalize provider tool call IDs for replay safety

NousResearch/hermes-agent · cluster 130363

Data as of 2026-10-23 11:54 UTC

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

open issues

open PRs

items grouped

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

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

Read #131063 Pick up a Lab task

These issues and PRs address a bug where provider-minted parallel tool call IDs cause sessions to become permanently broken during replay. The work focuses on normalizing those IDs without mutating history.

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.

#131063 fix(agent): normalize provider-minted parallel tool-call ids at mint time

merged to main

files: agent/message_sanitization.py, agent/turn_tool_round.py, agent/turn_tool_validation.py, tests/agent/test_message_sanitization_policy.py, tests/agent/test_provider_id_mint_normalization.py

3 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1 · other 1

#130366 fix(agent): normalize provider-minted parallel tool ids · merged via another change → #131063
#130462 agent: normalize provider-minted tool call ids on multi-call messages · other → #130363, #131063, #127260, #128787, #126351, #126102, #129301, #128974, #129281, #129482, #129740, #129476, #129235, #129123, #129065, #127869
#130550 fix(agent): normalize parallel provider tool call ids · done elsewhere → #131063

Closed issues · 1

Closed#130363Provider-minted parallel tool-call ids permanently wedge a session on replay (502 'JSON error injected into SSE stream')

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: #131063
Closed issues: 1
Attempts: 3 PRs closed without merging
Fix link checked: 2 Oct 2026

For your agent

The same facts, typed.

cluster/130363.json
cluster/130363.md