# NousResearch/hermes-agent · Codex large-context TTFB timeout cap issue

## Open now

- Nothing open on GitHub.

These items all concern a bug where large-context Codex requests have their scaled-up time-to-first-byte (TTFB) allowance overridden back to a 120-second cap. The group includes a bug report and related fix attempts addressing this timeout capping behavior.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #115291. Verify it addresses your case.
- **Recommended:** read PR #115291 (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-115291`. 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.50`: 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

- #91621: \[Bug\]: large-context Codex TTFB scaling is immediately capped back to 120s

## Prior & competing PRs

- **#115291: openai-codex: large-context TTFB scale-up no longer clawed back to 120s by the cap default (#91621, salvage #91635)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/chat_completion_helpers.py`, `contributors/emails/98612348+jwilson411@users.noreply.github.com`, `tests/agent/test_codex_ttfb_watchdog.py`
- **#91635: fix(agent): keep large Codex requests from reconnecting at 120s**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`
- **#104339: fix(agent): honor large-context Codex TTFB scale instead of recapping to 120s**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `b1968795b2`, `#91621`, `#115291`, `#91635`

## Fix status

- Merged to main in PR #115291 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-18`.
- Subsystem: `agent`