# NousResearch/hermes-agent · Honcho host-block cadence config not respected

## Open now

- Nothing open on GitHub.

These issues and a related fix concern Honcho's cadence-related configuration options (contextCadence, dialecticCadence, injectionFrequency) being read from the root level rather than the host block, causing host-scoped values to be ignored by the plugin, status, and runtime.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 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_PARTIAL`): 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.45`: 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

- #35359: Honcho host-scoped cadence config is ignored by status and runtime
- #60615: Honcho plugin: contextCadence/dialecticCadence/injectionFrequency ignore host-block values

## Prior & competing PRs

- **#35370: fix(honcho): resolve cadence config from host block, not just root raw**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `2f80ae0a6a`, `#131301`

## Fix status

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