NousResearch/hermes-agent

Codex first-progress deadline per attempt logic

Cluster 120174. Data as of 2026-10-27 11:58 UTC

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

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

Read #121364 Pick up a Lab task

These items concern how the first-progress deadline is applied to Codex lifecycle-only streams, including a bug where such streams could bypass TTFB and progress-gated idle watchdog checks and wait up to 600–900 seconds before retrying. The work involves bounding or enforcing the first-progress deadline correctly per physical attempt.

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.

#121364 Codex lifecycle-only streams hit the first-progress deadline per attempt (#120174, salvage #120209)

merged to main

files: agent/chat_completion_helpers.py, agent/chat_completion_nonstream.py, agent/chat_completion_wait_notice.py, agent/codex_runtime.py, tests/agent/test_codex_ttfb_watchdog.py, tests/agent/test_nonstream_wait_notice.py, tests/agent/test_wait_notice_cadence.py

1 PR closed without merging

From the close comments: merged via another change 1

#120209 fix(agent): bound Codex first progress per physical attempt · merged via another change → 3d704f5, 328d045, #121364, #120197

Closed issues · 1

Closed#120174Codex lifecycle-only streams bypass TTFB and progress-gated idle watchdog, waiting 600/900s before retry

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

Merged PRs: #121364
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 24 Sep 2026

For your agent

The same facts, typed.

cluster/120174.json
cluster/120174.md