Doctor command probe key tracking and fallback region reporting

NousResearch/hermes-agent · cluster 136791 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

The three members concern the hermes doctor command's handling of API key probes: one bug report describes a ✗ for a region probed with a fallback key and a hint naming an unset variable, and two fix-titled items address tracking which env var supplied the key and skipping fallback key region probes. The titles alone don't show how the changes relate or what their outcome is.

Open issues1

  • Issue#136791[Bug]: hermes doctor reports ✗ for a region it probed with a fallback key, and the hint names an unset variable

Open PRs2

  • PR#136793fix(doctor): skip fallback key region probes
  • PR#136795fix(cli): track which env var supplied a doctor probe key
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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.