NousResearch/hermes-agent

Copilot token probing without explicit provider configuration

Cluster 35946 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
5items grouped
Known?
Yes. 5 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 1 PR.

The members appear to center on Copilot token validation or credential probing happening when Copilot is not explicitly configured, such as when a GITHUB_TOKEN with a ghp_* prefix is set. Several titles describe changes to gate, skip, or require opt-in for this behavior, but the titles alone do not establish the outcome.

Open issues1

  • Issue#35946Spurious Copilot token validation WARNING when GITHUB_TOKEN=ghp_* is set but copilot is not configured

Open PRs1

  • PR#35958fix(auxiliary): skip unconfigured copilot fallback

3 PRs closed without merging

From the close comments: stale or abandoned 1 · other 2

  • #35998 fix(auxiliary): gate copilot token probing · other
  • #90324 fix(copilot): require explicit opt-in for GitHub token probes · other
  • #124234 fix(auth): gate copilot credential refresh on explicit provider config (#35946) · stale or abandoned
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.40: 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
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.