OpenCode Go: Kimi K3 capacity errors while usage allowance increases

Description

Kimi K3 showed capacity errors during my September 16 session, and I could not complete useful work. My Go dashboard subsequently showed $3.0635 of Kimi K3 usage: 40.8% weekly and 20.4% monthly.

Usage History records requests with nonzero output tokens between 11:03:40 and 11:10:51 AM UTC+7. Please investigate whether these were successful responses, incomplete responses, or retries, and whether failed requests consumed allowance.

Expected: Successful responses, or a clear availability error with accurate usage accounting.

Actual: Capacity errors prevented useful completion, while usage was recorded. The relationship between these errors and the recorded requests needs investigation.

OpenCode account: keenusuwannabut@gmail.com

I contacted help@anoma.ly from this address on September 16, 2026. Please use it to locate my account and investigate the recorded requests.

Plugins

None

OpenCode version

1.18.31

Steps to reproduce

1. Select Kimi K3 through OpenCode Go.
2. Submit a coding task.
3. Encounter capacity errors.
4. Check the Go dashboard and Usage History for recorded consumption.

Screenshot and/or share link

No response

Operating System

Windows 11, 64-bit

Terminal

PowerShell 7.6.6

Start with the reported OpenCode Go session, the Go dashboard, and Usage History for the September 16 timestamps, using the support contact and account details provided. Compare the capacity errors with recorded output tokens and determine whether requests succeeded, were incomplete, or were retried, and whether failed requests consumed allowance.