NousResearch/hermes-agent

Codex SSE relay discarding billed responses after completion

Cluster 103864. Data as of

Nothing open on GitHub. Fix merged in #115817 on 19 Sep 2026. Check it covers your case.

The short answer

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

These issues and PRs address a bug where a relay holding an SSE connection open past the terminal event causes billed responses to be silently discarded. The work involves bounding the post-terminal drain and ensuring completed responses are returned rather than lost.

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.

  • #115817 fix(codex): a relay that holds the stream open after response.completed no longer discards the billed response (#103864, salvage #103881)

    merged to main

    files: agent/codex_runtime.py, hermes_cli/config_defaults.py, tests/agent/test_run_agent_codex_responses.py, website/docs/user-guide/configuration.md

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

  • #103881 fix(codex): return completed responses from held-open streams · merged via another change → b3f6834, #115817, #103864, #103881
  • #103901 fix(codex): bound the post-terminal SSE drain so a wedged relay can't discard a billed response · duplicate → #103881, #103864
Closed issues · 1
  • Closed#103864codex: post-terminal drain is unbounded — a relay that never closes the SSE connection still discards billed responses (follow-up to #74348)
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

Merged PRs
#115817
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.