Fix reply_to_mode config handling across platforms

NousResearch/hermes-agent · cluster 121430 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items address bugs in how reply_to_mode values are stored and normalized in platform configuration, including handling of legacy boolean values and ensuring string modes are preserved correctly in the gateway.

Open issues1

  • Issue#121430hermes config set platforms.<platform>.reply_to_mode off stores false, gateway falls back to first

Open PRs2

  • PR#121445fix(config): preserve platform reply mode strings
  • PR#121482fix(gateway): normalize a legacy bool reply_to_mode across every platform
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
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.