Cairn
NousResearch/hermes-agent

Codex commentary not forwarded in streaming endpoints

Cluster 67580 · agent. Data as of

Nothing open on GitHub. Fix merged in #115903 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 #115903. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #115903. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug was identified where Codex commentary-phase text was not being forwarded through the API server and gateway to streaming SSE clients. Multiple fixes target routing that commentary to the correct channel and propagating it through the streaming pipeline.

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.

  • #115903 fix(api-server): codex commentary reaches streaming clients on session SSE, /v1/runs and /v1/responses (#67580, salvage #67593 #67613)

    merged to main

    files: contributors/emails/[redacted:email], gateway/platforms/api_server.py, gateway/platforms/api_server_openai_routes.py, gateway/platforms/api_server_runs.py, tests/gateway/test_api_server_runs.py, tests/gateway/test_session_api.py, website/docs/user-guide/features/api-server.md

2 PRs closed without merging

From the close comments: merged via another change 2

  • #67593 fix(gateway): forward Codex commentary to API Server streaming clients (#67580) · merged via another change → 3df8ad0, #115903, #67580, #67593, #67613
  • #67613 fix(api-server): forward Codex commentary in streaming SSE endpoint · merged via another change → 3df8ad0, #115903, #67580, #67593, #67613
Closed issues · 1
  • Closed#67580[Bug]: Codex commentary is not forwarded by API Server streaming endpoints
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

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

For your agent

The same facts, typed.

cluster/67580.json
cluster/67580.md