Sudden "Forbidden: {"model":"mimo-v2.5"}" Error Despite Active OpenCode Go Subscription

Description

Bug Report: Sudden "Forbidden: {"model":"mimo-v2.5"}" Error Despite Active OpenCode Go Subscription

1. Problem Description

While actively working with the mimo-v2.5 model through OpenCode Desktop and the console version of OpenCode, despite having an active OpenCode Go subscription with unused credits, any message sent in the chat suddenly started failing with the error: "Forbidden: {"model":"mimo-v2.5"}"
The error occurs regardless of the interaction method with OpenCode — whether through the OpenCode Desktop graphical interface or through the terminal (Command Prompt, PowerShell, or WSL) when using the opencode or opencode chat commands.

2. Reproduction

The issue is consistently reproducible under the following conditions:

Through OpenCode Desktop:
Active OpenCode Go subscription with unused credits.
Selection of the mimo-v2.5 (or mimo-v2.5-pro) model in OpenCode Desktop settings.
Sending any message in the OpenCode Desktop chat interface.

Through Console (Terminal):
Active OpenCode Go subscription with unused credits.
Launching OpenCode in the terminal using the opencode or opencode chat command.
Selecting or specifying the mimo-v2.5 model (e.g., via the --model mimo-v2.5 flag or in the opencode.json configuration file).
Sending any message in the console interface.
Expected behavior: The message is successfully processed by the mimo-v2.5 model, returning a meaningful response, as the subscription is active and credits are not exceeded.

Actual behavior:
In OpenCode Desktop, after sending a message, the interface displays the error Forbidden: {"model":"mimo-v2.5"}.
In the console, after sending a message, the terminal outputs the error: "Forbidden: {"model":"mimo-v2.5"}"
or a similar access denied message.
Other models (e.g., minimax-m2.7, deepseek-chat) continue to work correctly in both OpenCode Desktop and the console version.

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

Start by reproducing the failure with the opencode or opencode chat commands, selecting mimo-v2.5 through --model or opencode.json, and compare it with the working models. Trace how model access is handled for the console and OpenCode Desktop; done means an active subscription can send messages with mimo-v2.5 without regressing other models.