NousResearch/hermes-agent

Honcho host-block cadence config not respected

Cluster 35359 · agent. 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, 2 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: done elsewhere 1

  • #35370 fix(honcho): resolve cadence config from host block, not just root raw · done elsewhere → 2f80ae0, #131301
Closed issues · 2
  • Closed#35359Honcho host-scoped cadence config is ignored by status and runtime
  • Closed#60615Honcho plugin: contextCadence/dialecticCadence/injectionFrequency ignore host-block values
How this cluster was grouped
  • Link evidence (partly structural links): 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 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
agent
Closed issues
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.