NousResearch/hermes-agent
Fix missing first-chunk timing in Responses streams
Cluster 105311 · agent. Data as of
1 open item. Fix merged in #115819 on 19 Sep 2026. Check it covers your case.
The short answer
0open issues
1open PR
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #115819. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115819. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A bug where post_api_request first_chunk_at timing was not being recorded for Codex Responses streaming, and related fixes to populate that field correctly.
Open issues0
Open PRs1
- PR#105326fix(agent): populate first_chunk_at for Codex Responses streams
Fixes on record
-
#115819 fix(codex): post_api_request.first_chunk_at is populated for Responses streams instead of None (#105311, salvage #105325)
files:
agent/codex_runtime.py,tests/agent/test_codex_first_event_timing.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#105325 fix(codex): record first Responses stream event timing · merged via another change →
68ef35d,#115819,#105311,#105325
Closed issues · 1
- Closed#105311Bug: Responses streaming omits post_api_request first-chunk timing
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.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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #115819
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026