NousResearch/hermes-agent

Codex incomplete-response interim message duplication and capping

Cluster 52711 · agent. Data as of 2026-10-28 11:56 UTC

Nothing open on GitHub. Fix merged in #65063 on 15 Jul 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #65063 Pick up a Lab task

One bug report describes an OpenAI-compatible /v1/responses endpoint returning status=incomplete and producing many near-identical messages in a single turn, with existing dedup/cap logic seen as insufficient. Two pull requests propose deduplicating codex incomplete interim messages by visible content, with one also adding a cumulative cap.

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.

#65063 fix(agent): dedup codex incomplete interims on visible content

merged to main

files: agent/conversation_loop.py, tests/run_agent/test_run_agent_codex_responses.py

1 PR closed without merging

From the close comments: merged via another change 1

#52716 fix(agent): dedup codex incomplete interims on visible content + cumulative cap · merged via another change → #65063, #52711

Closed issues · 1

Closed#52711[Bug]: status=incomplete (incomplete_details=None) on an OpenAI-compatible /v1/responses endpoint fans one turn into ~60 near-identical messages — codex_responses incomplete-continuation dedup/cap insufficient

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
Merged PRs: #65063
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 15 Jul 2026

For your agent

The same facts, typed.

cluster/52711.json
cluster/52711.md