# NousResearch/hermes-agent · Fix /config terminal settings display accuracy

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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

- #16723: \[Bug\]: /config terminal.timeout value does not match value in config.yaml nor TERMINAL_TIMEOUT env variable

## Prior & competing PRs

- **#13651: fix(cli): honor config terminal settings in /config**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`
- **#16807: fix(cli): show effective terminal timeout in /config**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#13651`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`