# NousResearch/hermes-agent · Codex first-progress deadline per attempt logic

## Open now

- Nothing open on GitHub.

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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #121364. Verify it addresses your case.
- **Recommended:** read PR #121364 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-121364`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

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

## Prior & competing PRs

- **#121364: Codex lifecycle-only streams hit the first-progress deadline per attempt (#120174, salvage #120209)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#120209: fix(agent): bound Codex first progress per physical attempt**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `3d704f53e1`, `328d0459e1`, `#121364`, `#120197`

## Fix status

- Merged to main in PR #121364 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-24`.