Skip to content

[Bug] "Provider returned error" consistently occurs with Kimi K2.5 via OpenCode Go on Windows #16685

Closed as duplicate

Description

@ChrisWenChen

Description

Environment Information
Client: OpenCode (Windows Desktop Client, latest version))

Model Provider: OpenCode Go

Model: Kimi K2.5

Timestamp: March 8, 2026, 10:34 PM (CST)

Describe the bug
When sending a prompt to the Kimi K2.5 model through the OpenCode Go provider on the Windows desktop client, the application immediately returns a red error box stating "Provider returned error". This happens consistently and prevents any response from being generated.

Session Example (The Prompt that triggered the error)
User Input:

"目前的三个模板,对不对?没有yaml信息?我觉得在工作流加上,如无特殊说明,尽量用中文写作。标题为中文,但是要有alias,通常是英文或者别的语言的翻译以及一些真的缩写、别名等。不需要日期和tag。"

Expected Result:
The model should analyze the prompt and provide a response or suggestion regarding the template structure.

Actual Result:
The UI shows: Provider returned error (Build: Kimi K2.5).

Plugins

No response

OpenCode version

v1.2.22

Steps to reproduce

Open the OpenCode Windows client.

  • Ensure the provider is set to OpenCode Go and the model selected is Kimi K2.5.

  • Enter the prompt mentioned in the "Session Example" above.

  • Click 'Send' or press Enter.

  • Observe the red error message appearing below the input box.

Screenshot and/or share link

Image

Operating System

Windows

Terminal

Windows Terminal

Activity

  1. seasea128 commented on Mar 9, 2026

    @seasea128

    This also happens on Linux with opencode CLI with OpenCode Go's Kimi K2.5. All other models from OpenCode Go works file as far as I've tested.

  2. osorionicolas commented on Mar 19, 2026

    @osorionicolas

    Same in MacOS

  3. eliawk commented on Mar 23, 2026

    @eliawk

    same here!

  4. meffbbbro commented on Mar 24, 2026

    @meffbbbro

    +1

  5. jaaasonSun commented on Mar 29, 2026

    @jaaasonSun

    I am seeing the same error on macOS CLI

  6. jonny7737 commented on Mar 29, 2026

    @jonny7737

    Same in zeroclaw in docker.
    Also happens when using minimax-m2.7 though the error is less frequent

    Times are in CDT

    2026-03-29 09:11:09 ❌ LLM error after 13880ms: All providers/models failed. Attempts:
    2026-03-29 09:11:09 provider=opencode-go model=kimi-k2.5 attempt 1/3: retryable; error=OpenCode Go API error (500 Internal Server Error): {"type":"error","error":{"type":"error","message":"Cannot read properties of undefined (reading 'prompt_tokens')"}}
    2026-03-29 09:11:09 provider=opencode-go model=kimi-k2.5 attempt 2/3: retryable; error=OpenCode Go API error (500 Internal Server Error): {"type":"error","error":{"type":"error","message":"Cannot read properties of undefined (reading 'prompt_tokens')"}}
    2026-03-29 09:11:09 provider=opencode-go model=kimi-k2.5 attempt 3/3: retryable; error=OpenCode Go API error (500 Internal Server Error): {"type":"error","error":{"type":"error","message":"Cannot read properties of undefined (reading 'prompt_tokens')"}}
    

    Kimi has prompt token issue but minimax-m2.7 has input token issue.

  7. Tao-Yida commented on Mar 30, 2026

    @Tao-Yida

    Experiencing same issue for Mimo v2 pro free by Opencode Free, and additional "expected 'id' to be a string" error for Kimi K2.5 via Nvidia API since OpenCode1.2.24.

  8. DKEQ commented on Mar 30, 2026

    @DKEQ
    Image

    This has been plaguing me out of random, its slowing my work and is getting annoying

  9. lodela commented on Apr 11, 2026

    @lodela

    same with "Nemotron 3 Super Free" can anyone show some more about this error? HOW CAN i FIXIT?

  10. tonycaputome commented on Apr 20, 2026

    @tonycaputome

    Same here but with Kimi-2.6 (OpenCode Go)

  11. yinxiaju commented on Apr 21, 2026

    @yinxiaju

    today use Kimi-2.6 (OpenCode Go) or Kimi-2.5 (OpenCode Go) return same wrong,
    but use nvdia Kimi-2.5 is work ok

  12. 1 remaining item

  13. Dayclone commented on Apr 23, 2026

    @Dayclone

    I get this issue as well for the latest Kimi K2.6

  14. KaltWulx commented on Apr 24, 2026

    @KaltWulx

    The MCPs are the problem.

    #23887 (comment)

  15. Tranthanh98 commented on Apr 26, 2026

    @Tranthanh98

    same today

  16. nikkbelousov commented on Apr 26, 2026

    @nikkbelousov

    again!

  17. saadzimat430 commented on Apr 26, 2026

    @saadzimat430

    same

  18. rekram1-node commented on Apr 27, 2026

    @rekram1-node
    Contributor

    Going to continue convo in: #23887

    Chances are there is an mcp or tool causing an error the error is a little too generic

  19. bao-to-covergo commented on Apr 28, 2026

    @bao-to-covergo

    same issue

  20. desarrollador1IR commented on Apr 29, 2026

    @desarrollador1IR

    SAMEEEEEEEEEEEE on ubuntu

  21. rekram1-node commented on Apr 29, 2026

    @rekram1-node
    Contributor

    just comment on the other issue yall

  22. nylla8444 commented on May 2, 2026

    @nylla8444

    experienced this again
    "Error from provider: Provider returned error"

  23. jesterror987 commented on May 2, 2026

    @jesterror987

    +1

  24. fjrevoredo commented on May 4, 2026

    @fjrevoredo

    +1

  25. BarnoTD commented on Jun 29, 2026

    @BarnoTD

    Same today for MiMo V2.5 Free on MacOS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingwebRelates to opencode on web / desktopwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions