NousResearch/hermes-agent

Config-map provider lost when writing named profile

Cluster 106643 · dashboard. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

A bug causes the profile builder to drop the providers.<name> entry when assigning a config-map provider to a named profile, leading to an unknown provider error at agent init. The remaining members are fixes addressing this omission.

Open issues1

  • Issue#106643[Bug] Profile builder drops providers.<name> entry when assigning a config-map provider (scnet) → agent init: Unknown provider '<name>'

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: superseded by another PR 2 · other 1

  • #106651 fix(profile-builder): carry config-map provider entry into target profile · superseded by another PR → d62716c, #106655
  • #106655 fix(profiles): copy config-map provider into named profile on model write · superseded by another PR → #106643, #106651
  • #126454 fix(profile-builder): carry config-map provider entry into target profile · other
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
dashboard
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.