Skip to content

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

Closed as not planned

Description

@Belf1995

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.

  1. 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

Activity

  1. github-actions commented on Sep 7, 2026

    @github-actions
    Contributor

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

    Additionally, several required fields in the bug report template were left as "No response": OpenCode version, Operating System, Terminal, and Steps to reproduce. Please edit the issue to fill in these fields — they help maintainers reproduce and diagnose the problem faster.

  2. hdworker commented on Sep 8, 2026

    @hdworker
    Image
  3. Belf1995 commented on Sep 8, 2026

    @Belf1995
    Author
    Image

    It’s like this for me…
    Image

  4. Tarquinen commented on Oct 20, 2026

    @Tarquinen
    Member

    Thanks for the report! This was a temporary problem with the model's upstream provider around the time it was reported, and there haven't been new reports here since. If you still see it on the latest OpenCode, please open a new issue with your version, model and the exact error. Closing this issue.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions