Cairn
NousResearch/hermes-agent

Fix CLI clarify timeout fallback behavior

Cluster 72688 · hermes cli. Data as of

Nothing open on GitHub. Fix merged in #114875 on 18 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #114875. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address a bug where the CLI incorrectly falls back to a legacy 120-second timeout instead of using the configured clarify timeout value. The work involves propagating and honoring the canonical timeout setting after config merging.

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.

  • #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

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

  • #72714 fix(cli): honor canonical clarify timeout after config merge · merged via another change → 1b50849, #114875, #113873, #72714
  • #73577 fix(cli): propagate agent.clarify_timeout correctly, remove legacy 120s fallback · duplicate → #72714
Closed issues · 1
  • Closed#72688CLI clarify timeout still falls back to legacy 120s after #69774
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: 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
hermes cli
Merged PRs
#114875
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/72688.json
cluster/72688.md