NousResearch/hermes-agent

kimi-coding credential pool base_url seeding for sk-kimi- keys

Cluster 5561 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These members appear to share one theme: the kimi-coding credential pool seeding a base_url that may be wrong for sk-kimi- keys, with an issue reporting a 401 on the first request. Two pull requests propose changes, one using _resolve_kimi_base_url and one also mentioning a PKCE endpoint fallback.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: other 2

  • #5566 fix(credential_pool): use _resolve_kimi_base_url when seeding kimi-coding pool · other → #5669
  • #5669 fix(auth): kimi-coding pool base_url seeding + PKCE endpoint fallback · other
Closed issues · 1
  • Closed#5561kimi-coding credential pool seeds wrong base_url for sk-kimi- keys, causing 401 on first request
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
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.