Cairn
NousResearch/hermes-agent

Fix /config terminal settings display accuracy

Cluster 16723 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a bug where the /config command does not correctly reflect terminal timeout and other terminal settings from config.yaml or environment variables. The fixes ensure the displayed values match the effective configuration.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #13651 fix(cli): honor config terminal settings in /config · done elsewhere
  • #16807 fix(cli): show effective terminal timeout in /config · done elsewhere → #13651
Closed issues · 1
  • Closed#16723[Bug]: /config terminal.timeout value does not match value in config.yaml nor TERMINAL_TIMEOUT env variable
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.67: 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
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/16723.json
cluster/16723.md