anomalyco / anomalyco/opencode

NVIDIA provider missing moonshotai/kimi-k2.6 despite model being available via NVIDIA API

Open
#40,911 0 comments 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Aug 6, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description
Checklist
  • I searched for existing issues.
OpenCode version
1.18.14
Provider

NVIDIA API

Description

moonshotai/kimi-k2.6 is available from NVIDIA's /v1/models endpoint, but OpenCode does not expose it under the NVIDIA provider.

The same model does appear under the Cloudflare Workers AI provider.

Steps to reproduce
  1. Authenticate with NVIDIA:
opencode auth login nvidia
  1. Refresh models:
opencode models --refresh
  1. Search for Kimi models:
opencode models | grep kimi
Actual behavior

Output contains:

cloudflare-ai-gateway/workers-ai/@cf/moonshotai/kimi-k2.6
cloudflare-ai-gateway/workers-ai/@cf/moonshotai/kimi-k2.5
cloudflare-ai-gateway/moonshotai/kimi-k3

but does not contain:

nvidia/moonshotai/kimi-k2.6
Expected behavior

If NVIDIA exposes moonshotai/kimi-k2.6 through its Models API, OpenCode should expose it under the NVIDIA provider as well.

Additional information
  • OpenCode version: 1.18.14
  • opencode auth list shows NVIDIA authentication is configured correctly.
  • opencode models --refresh completes successfully.
  • Other NVIDIA models (Qwen, DeepSeek, GPT-OSS, Llama, etc.) are listed normally.

It appears the NVIDIA provider's model registry is missing moonshotai/kimi-k2.6, even though the NVIDIA API exposes it. NVIDIA's model listing includes this model. :contentReference[oaicite:0]{index=0}

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.