What happened
The anomalyco/models.dev pull request titled “feat(opencode): bring back MiniMax M3.1 Flash Free” was merged into the repository’s dev branch on November 10, 2026. Its description says MiniMax M3.1 Flash Free is being brought back to OpenCode’s Free tier for a limited time. The pull request records a single commit and identifies the change as a MiniMax M3.1 Flash Free promotion.
The implementation is a model-registry change rather than a new MiniMax model release. A review note on the pull request says that removing status = "deprecated" republishes the Free route as available in v1 and v2. In practical terms, the repository is changing the status of an existing OpenCode route so it can be offered again, rather than adding a newly trained model or announcing a new API capability.
The pull request was opened and merged by opencode-agent[bot]. It shows two checks passing, an inactive release deployment, and no recorded human reviews. Its description says documentation and the public registry row should be live before the merge. It also identifies the request as having come through Slack. Those process details show a registry update was completed, but they do not provide user-facing terms for the restored route.
A bot review explicitly raised a documentation problem before the merge. It noted that the pull request had no direct first-party links supporting the availability claim or the “limited time” language, and requested links to OpenCode model documentation and a public registry entry. The review was marked low severity and the pull request was merged. As a result, the visible repository record supports that the deprecated marker was removed, while the operational details of the Free-tier offer remain thin.
The pull request gives no end date for the temporary return. It also lists no usage allowance, rate limit, context limit, geographic availability, account requirement, or model-performance figure. “Free” describes the route in the pull request, not a documented capacity commitment. Builders can treat the change as a possible additional option in OpenCode, but cannot infer how much work it will support or whether it will remain selectable for a particular team.
What the archive adds
New Runtime’s earlier coverage of OpenCode’s DeepSeek V4.1 Flash quota on October 24, 2026 and its separate free route on October 28, 2026 tracked model-access changes on the same platform. This is a new access event involving MiniMax and a temporary restoration, not a new fact about those DeepSeek routes.
Trend signal
This is a small example of access terms becoming part of practical model selection: a registry change can restore a route to a Free tier without a new model release. It does not establish that temporary free routes are a durable product strategy, nor does it show their uptake or economics. This does not yet fit a pattern New Runtime tracks.
Why now
The pull request was merged on November 10, 2026 and describes the return as limited-time. It does not explain why the route was restored then, why it had previously been deprecated, or when the offer will end. The timing therefore supports urgency to check availability, but not a conclusion about the promotion’s intended duration.
Why it matters
For an individual developer or a small team, a restored free route can reduce the cost of evaluating a model inside an existing coding workflow. It may be useful for an experiment, a side-by-side task comparison, or a fallback during short-term work. Yet capacity planning requires more than a Free label. A team needs to know whether requests are capped, throttled, restricted by account type, or likely to disappear after a short promotion.
The more durable lesson is operational. Model availability can change through registry metadata, independent of a model release or a visible product launch. Teams that build around hosted agent tools should keep a small evaluation path for substitute models and avoid treating a promotional route as baseline production capacity. Here, the repository confirms the removal of a deprecated status; it does not confirm a stable service commitment.
Limits and uncertainty
The merged pull request is direct evidence of a configuration update, but it does not link to the OpenCode documentation or public registry row needed to independently inspect the offer. The stated limited-time period has no end date. No quota, rate limit, context window, account condition, regional scope, or service-level expectation is disclosed.
The repository record also does not measure actual availability after the merge. It cannot show whether the route appears for every OpenCode user, how it performs under load, or whether requests are accepted consistently. The absence of recorded human reviews does not itself indicate a defect, but it leaves the public change record with little explanation beyond the configuration action.
Reader takeaway
MiniMax M3.1 Flash Free has been restored in OpenCode’s registry by removing its deprecated status, and the pull request calls the return temporary. Check whether it is visible in your own OpenCode setup and test it on representative work, but do not budget a continuing workload around it until limits and duration are documented.
Open question
How long will MiniMax M3.1 Flash Free remain available through OpenCode, and what quotas or eligibility conditions apply?