anomalyco / anomalyco/opencode

Models other than hy3-free / deepseek flash free fail with Forbidden: {model:big-pickle}

Open
#43,054 4 comments 3 reactions 1 assignee View on GitHub

@MrMushrooooom is already working on this.

Since Aug 17, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

When using opencode with any model other than hy3-free and deepseek flash free, requests fail with a Forbidden error whose body references the model big-pickle:

Forbidden: {"model":"big-pickle"}

Only hy3-free and deepseek flash free are usable. Every other model selection results in this error.

Steps to reproduce

  1. Set the active model to anything other than hy3-free or deepseek flash free (e.g. a model that internally resolves to / is routed as big-pickle).
  2. Send any prompt / start a session.
  3. Observe the Forbidden: {"model":"big-pickle"} response.

Expected behavior

  • The selected model is accepted and the request completes, OR
  • a clear, descriptive error explains which models are permitted.

Actual behavior

  • The request is rejected with Forbidden: {"model":"big-pickle"}.
  • Only hy3-free and deepseek flash free work.

Notes

  • The rejected model id big-pickle appears to be a backend model name that is not authorized for the account/endpoint.
  • This looks like a model-access / entitlement issue: the backend only allows hy3-free and deepseek flash free, while other models (including ones that map to big-pickle) are blocked with a bare Forbidden and no detail.
  • A clearer error message (which models are allowed, or why this one is forbidden) would make the failure actionable instead of cryptic.

Environment

  • opencode
  • Working models: hy3-free, deepseek flash free
  • Failing models: everything else (backend returns {"model":"big-pickle"})

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.