# NousResearch/hermes-agent · Clarify timeout config key inconsistency fixes

## Open now

- Nothing open on GitHub.

Multiple code paths used different config keys and hardcoded defaults for the clarify timeout, leaving it unconfigurable in some interfaces. These issues and fixes address unifying the timeout under one canonical config key across CLI, TUI, and gateway.

## TL;DR

- 11 member(s): 0 open issue(s), 3 closed issue(s), 0 open PR(s), 2 merged PR(s), 6 PR(s) closed without merging.
- A fix was merged to main in PR #69774. Verify it addresses your case.
- **Recommended:** read PR #69774 (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: `partially_resolved` · deciding PR(s): `pr-69774`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.18`: 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

- #25859: Two separate clarify timeout config keys cause silent CLI auto-decide after 120s
- #42969: \[Bug\]: clarify timeout config key mismatch
- #51960: Clarify timeout not configurable on TUI/Desktop — three code paths, three defaults, two config keys, one unconfigurable

## Prior & competing PRs

- **#25962: fix(cli): read agent.clarify_timeout in CLI clarify callback**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#25865`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#34499: fix(cli): backfill clarify.timeout from agent.clarify_timeout**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#25865`, `#25859`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#69774: fix(clarify): one canonical timeout across CLI, TUI/desktop, and gateway**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - files: `cli.py`, `hermes_cli/callbacks.py`, `tests/test_tui_gateway_server.py`, `tests/tools/test_clarify_gateway.py`, `tools/clarify_gateway.py`, `tui_gateway/server.py`
- **#114875: fix(clarify): CLI clarify prompt honours agent.clarify_timeout instead of a hidden 120 s cap (#113873, salvage #72714)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - files: `agent/tool_executor.py`, `cli.py`, `contributors/emails/[redacted:email]`, `hermes_cli/config_defaults.py`, `tests/tools/test_clarify_gateway.py`, `website/docs/user-guide/configuration.md`, `website/docs/user-guide/messaging/discord.md`, `website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/messaging/discord.md`, `website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/messaging/telegram.md`
- **#42974: fix(cli): read agent.clarify_timeout for CLI clarify timeout (#42969)**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#69774`, `#42969`
- **#51202: fix(cli): fall back to agent.clarify_timeout when clarify.timeout is unset**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#69774`, `#42969`
- **#51993: fix: honor tui clarify timeout**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#69774`, `#51960`
- **#87463: fix(clarify): honor canonical timeout in CLI**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `1b50849d273b`, `#114875`, `#114875`, `#113873`, `#72714`, `#113873`

## Fix status

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