Cairn

Config profile inheritance and provider key fixes

NousResearch/hermes-agent · cluster 20270 · agent

Data as of

8 open items. Fix attempted, not merged.

The short answer

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

Multiple issues and fixes around profile configs inheriting provider settings from the root/default config rather than replacing them, plus related auth and API key fallback fixes for specific providers.

Open issues3

  • Issue#40645Kanban: worker profile custom_providers not inherited from default config
  • Issue#43713Bug: profile config providers dict replaces/clears default providers instead of inheriting
  • Issue#55539[Kanban] Worker spawn produces Authorization: Bearer *** on first LLM call for minimax-cn profile

Open PRs5

  • PR#20964feat(config): implement profile config inheritance from default
  • PR#40670fix(kanban): inherit custom_providers from default config for workers
  • PR#43765fix(config): inherit default root config when loading profile configs
  • PR#55552fix(diagnostics): show masked API key and correct URL in request dumps for anthropic_messages mode
  • PR#55587fix(auth): add config.yaml model.api_key fallback for API-key providers

4 PRs closed without merging

From the close comments: superseded by another PR 1 · won't fix / by design 1 · other 2

  • #14642 config: inherit provider sections from root into named profiles · other → #14643, #41741, #43816, #43765
  • #41741 feat(config): profile config inheritance from default (#20270) · other → #20964
  • #43816 fix(config): profile configs inherit root providers instead of replacing (#43713) · superseded by another PR → #43765, #43713
  • #45254 fix(auth): iterate token endpoints in Anthropic OAuth login flow · won't fix / by design
Closed issues · 2
  • Closed#20270[Feature]: Profile config inheritance from default
  • Closed#22718[Feature]: Profile Inheritance — Base/Profile Layering Architecture
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.11: 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
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/20270.json
cluster/20270.md