# NousResearch/hermes-agent · Configurable per-task no-progress timeout for Codex

## Open now

- Nothing open on GitHub.

These members relate to adding configuration support for a per-task no-progress timeout in the Codex auxiliary compression feature. They cover the feature request, implementation, and a related fix or salvage of prior work.

## 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 #115804. Verify it addresses your case.
- **Recommended:** read PR #115804 (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-115804`. 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

- #108104: \[Feature\]: Make Codex auxiliary no-progress timeout configurable per task

## Prior & competing PRs

- **#115804: feat(compression): auxiliary.<task>.no_progress_timeout widens the Codex summary stream progress window per task (#108104, salvage #108119)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/auxiliary_client.py`, `cli-config.yaml.example`, `hermes_cli/config_defaults.py`, `tests/agent/test_auxiliary_client.py`, `website/docs/user-guide/configuration.md`
- **#108119: feat(compression): make Codex auxiliary no-progress timeout configurable per task**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `a6057ccbeaf1`, `#115804`, `#108104`, `#108119`

## Fix status

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