Cairn

Null YAML values stringified to 'None' in auxiliary config

NousResearch/hermes-agent · cluster 100835 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 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 3 PRs.

A bug where null/unset YAML values in auxiliary model configuration were being converted to the literal string 'None' instead of being treated as unset. Multiple fixes and a bug report address this same issue across the agent and auxiliary config handling.

Open issues1

  • Issue#100835[Bug]: auxiliary model: null is stringified to literal "None" model ID

Open PRs3

  • PR#100851fix(agent): prevent null auxiliary model from becoming "None" string ID
  • PR#100861fix(auxiliary): treat YAML null task-config values as unset, never as 'None' literal
  • PR#100913fix(agent): guard auxiliary config against YAML null values (#100835)
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.50: 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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/100835.json
cluster/100835.md