Kimi-k2.6 "Provider returned error" on Go Plan #25489

Activity

1. Kareem-AEz

   added

   bugSomething isn't workingSomething isn't working

   on May 2, 2026
2. github-actions commented on May 2, 2026

   

   github-actionsBot

   on May 2, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [Bug]: OpenCode Go + Kimi K2.6/K2.5 returns 'Provider returned error' on CLI 1.14.20 #23887: OpenCode Go + Kimi K2.6/K2.5 returns 'Provider returned error' on CLI 1.14.20 (same error, same model, same plan)
   • [Go Plan] Kimi K2.5/K2.6 models return "account suspended" from upstream Moonshot AI #25458: [Go Plan] Kimi K2.5/K2.6 models return "account suspended" from upstream Moonshot AI (same model/plan, likely same root cause)
   • Opencode Go Kimi and Minimax doesn't work #17626: Opencode Go Kimi and Minimax doesn't work (earlier report of Kimi not working on Go plan)

   If your issue is the same as one of these, please add a comment there instead so we can track it in one place.
3. thdxr

   assigned

   MrMushrooooom

   on May 3, 2026
4. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   on May 3, 2026
5. fwang

   assigned

   rekram1-node

   and unassigned

   MrMushrooooom

   on May 3, 2026
6. rekram1-node commented on May 3, 2026

   

   rekram1-node

   on May 3, 2026

   Collaborator

   More actions

   are u still facing this?
7. Kareem-AEz commented on May 4, 2026

   

   Kareem-AEz

   on May 4, 2026

   Author

   More actions

   are u still facing this?

   @rekram1-node Thanks for following up. I found the culprit, it was the PostHog MCP server. As soon as I disabled it, Kimi started working again. My other MCP servers (GitHub, shadcn, motion, better-auth, etc.) are all connected and working fine, so it seems specific to PostHog. Not sure if it's a tool count limit or a schema conflict, but disabling it fixed it for me.
8. Kareem-AEz

   closed this as completedon May 16, 2026