Cairn
NousResearch/hermes-agent

YAML serializes cleared api_key as 0 integer bug

Cluster 56535 · hermes cli. 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, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs 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.

A bug where clearing model endpoint credentials causes the api_key field to be written as the integer 0 in YAML instead of being omitted or kept as a string, leading to authentication failures. The associated fixes address None-to-0 serialization and enforce string typing for api_key on save.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #56661 fix(config): keep model api_key string typed on save · done elsewhere → #56535
  • #57089 fix(config): prevent YAML None→0 serialization in credential clearing · other → #56535
Closed issues · 1
  • Closed#56535[Bug] model.api_key: 0 (YAML integer) saved when clear_model_endpoint_credentials() removes api_key, causing auth failures on custom providers
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
hermes cli
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/56535.json
cluster/56535.md