Cairn

Kimi-k3 model ID mismatch on coding endpoint

NousResearch/hermes-agent · cluster 105650 · agent

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.

These issues and fixes address a mismatch between the model IDs listed in the Kimi-coding catalog metadata and the IDs actually accepted by the coding endpoint, specifically that 'kimi-k3' variants must be translated to the bare 'k3' slug. All three members share this single narrow theme.

Open issues1

  • Issue#105650[Bug]: kimi-coding rejects kimi-k3 (401 'model id does not exist … use k3') — metadata lists stale ids on coding endpoint

Open PRs2

  • PR#105664fix(kimi-coding): translate kimi-k3 display ids to the bare k3 slug on the /coding endpoint
  • PR#117909fix(kimi): align kimi-coding curated catalog with the coding endpoint
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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/105650.json
cluster/105650.md