Cairn

Clarify timeout config key inconsistency fixes

NousResearch/hermes-agent · cluster 25859 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #69774. Check it covers your case.

The short answer

0open issues
0open PRs
11items grouped
Known?
Yes. 11 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #69774. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #69774. That is separate from the fix event.
Still open
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.

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.

  • #69774 fix(clarify): one canonical timeout across CLI, TUI/desktop, and gateway

    merged to main

    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

    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

6 PRs closed without merging

From the close comments: superseded by another PR 6

  • #25962 fix(cli): read agent.clarify_timeout in CLI clarify callback · superseded by another PR → #25865
  • #34499 fix(cli): backfill clarify.timeout from agent.clarify_timeout · superseded by another PR → #25865, #25859
  • #42974 fix(cli): read agent.clarify_timeout for CLI clarify timeout (#42969) · superseded by another PR → #69774, #42969
  • #51202 fix(cli): fall back to agent.clarify_timeout when clarify.timeout is unset · superseded by another PR → #69774, #42969
  • #51993 fix: honor tui clarify timeout · superseded by another PR → #69774, #51960
Show 1 more
  • #87463 fix(clarify): honor canonical timeout in CLI · superseded by another PR → 1b50849, #114875, #113873, #72714
Closed issues · 3
  • Closed#25859Two separate clarify timeout config keys cause silent CLI auto-decide after 120s
  • Closed#42969[Bug]: clarify timeout config key mismatch
  • Closed#51960Clarify timeout not configurable on TUI/Desktop — three code paths, three defaults, two config keys, one unconfigurable
How this cluster was grouped
  • Link evidence (partly structural links): 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 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

Subsystem
apps/desktop
Merged PRs
#69774, #114875
Closed issues
3
Attempts
6 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/25859.json
cluster/25859.md