Cairn
NousResearch/hermes-agent

Doctor validator false-positives for valid provider aliases

Cluster 15358 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues 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
0 issues and 1 PR.

Multiple issues and fixes address the doctor command incorrectly rejecting providers it recognizes as valid, including aliased providers like 'copilot' and 'bedrock'. Related work also adds native AWS Bedrock provider support and fixes provider registration so resolution succeeds.

Open issues0

No open issues.

Open PRs1

  • PR#16086fix(doctor): accept providers whose catalog id is None

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #15361 fix(providers): register bedrock in HERMES_OVERLAYS so resolve_provider_full succeeds · done elsewhere
  • #16083 fix(doctor): accept aliased providers (e.g. 'copilot') without false-positive unknown-provider error · superseded by another PR → #16086
Closed issues · 3
  • Closed#15358hermes doctor: false-positive "model.provider 'bedrock' is not a recognised provider"
  • Closed#16076bug(doctor): reports 'copilot' as unknown provider while listing it as valid
  • Closed#16085doctor false-positive: validator rejects providers it lists as valid (opencode-zen, ai-gateway, copilot, kilocode, kimi-coding, kimi-coding-cn, bedrock)
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.25: 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
3
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/15358.json
cluster/15358.md