# NousResearch/hermes-agent · Config example file mismatches code defaults and omits keys

## Open now

- Nothing open on GitHub.

A bug report, a targeted fix, and a broader docs update all address discrepancies between cli-config.yaml.example and the actual runtime defaults, including wrong values for two keys and six undocumented keys.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #112235. Verify it addresses your case.
- **Recommended:** read PR #112235 (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: `resolved` · deciding PR(s): `pr-112235`. 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

- #111730: \[Bug\]: cli-config.yaml.example contradicts the code defaults for \`display.show_reasoning\` and \`agent.verify_on_stop\`, and omits six keys the runtime reads

## Prior & competing PRs

- **#112235: docs: config example, CONTRIBUTING conventions, cron watchdog and unattended browser logins now match the code (#111730, #112005, #112020, #111633, #111995, salvage #101327, #112037, #112024, #111636, #112001)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `CONTRIBUTING.md`, `cli-config.yaml.example`, `cron/AGENTS.md`, `website/docs/user-guide/features/browser.md`, `website/docs/user-guide/features/cron.md`
- **#101327: docs(config): align cli-config.yaml.example with the code defaults and document six missing keys**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#112235`

## Fix status

- Merged to main in PR #112235 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-16`.