Oversized item IDs causing 400 errors in Responses API
NousResearch/hermes-agent · cluster 10788 · agent
Data as of
Nothing open on GitHub. Fix merged in #62225. Check it covers your case.
The short answer
- Known?
- Yes. 8 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #62225. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PRs #62225, #73538. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple fixes and reports address a problem where replayed message, reasoning, or call IDs exceeding length limits trigger HTTP 400 'string_above_max_length' errors in the Responses API. The cluster covers stripping, clamping, or dropping these oversized IDs across various replay scenarios.
Open issues0
Open PRs0
Fixes on record
-
#62225 fix(codex): drop oversized message ids on Responses input replay
files:
agent/codex_responses_adapter.py,tests/agent/test_codex_responses_adapter.py -
#73538 fix(codex): clamp oversized Responses call_id so MCP tools don't brick sessions (#73492)
files:
agent/codex_responses_adapter.py,tests/agent/test_codex_responses_adapter.py
4 PRs closed without merging
From the close comments: superseded by another PR 2 · closed without comment 1 · done elsewhere 1
- #10796 fix(codex): drop reasoning item ids > 64 chars · closed without comment
-
#27143 fix(codex): strip oversized message item ids on replay to prevent HTTP 400 · superseded by another PR →
#17318 -
#33306 fix: strip oversized item ids from Responses API replay (#10788) · done elsewhere →
0b2907f,#62225 -
#35488 fix(codex_responses_adapter): drop cross-issuer message ids on replay · superseded by another PR →
#62225,#27038
Closed issues · 2
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.26: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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