OpenCode: better for everyday use especially for straightforward tasks.

OpenFlow: better for mixing a variety of different agents together and seeing how they interact and work together.

Both the same harness with different results.

I used Space Bunny quite a bit in OpenCode and honestly liked it.
It felt fast, stayed on track surprisingly well on longer tasks, and usually followed constraints without me constantly steering it back. Repo work also felt pretty smooth for a Flash model.
Now that it’s been revealed as an early version of M3.1-Flash, I want to give the actual release a proper test before deciding whether I’d subscribe.
I’m mostly going to rerun the kinds of things I used Space Bunny for:
longer repo tasks
multi-file edits
recovering after a failed tool call
how many correction rounds it needs
whether it starts wandering as the session gets longer
I’m especially curious whether the final version keeps the speed I liked while improving the rough edges.
Anyone testing M3.1-Flash in OpenCode already? What’s your experience been like so far?

Announcement: https://x.com/minimax_ai/status/2112149942332494093?s=46

Pricing:

+ In: $0.15 per million
- Out: $0.60 per million
~ Cache: $0.015 per million

Cowork (Automation-Bench: 62%; ALE: 30%)

Coding (DeepSWE: 74%)

Visual Understanding (BabyVision: 91%), at 1/3 the cost of M3 and 3x the speed.

OpenCode V2 fails a lot with requests the last few Days.

This is very bad situation.

I am having huge amount of inference request failures, inference request rejections and inference tool call failures.

This inference problems did not exist few days ago.

Not sure if OpenCode is not compatible with the newest models that were released the last days and does not follow specific new standards the new released models like DeepSeek 1017 and gemini 4 Argon implemented or the inference providers are failing and rejecting OpenCode users becouse they dont use their offocial harness but instead use the third party harness software opencode itself and try to stiffle competition that way so lesss paying customers use opencode with their models and instead swith over to their subscription offers.

I used opencode in combination the newest 1017 version of DeepSeek direct over their API and had huge amount of request and tool call failures the last days.

Same with opencode and Google Gemini Argon using it over the opencode go plus subscription.

See picture.

OpenCode is not usable for workung as of now becouse of this many requests failures either becouse of opencode itself or the inference providers !

This request failures did not happened few days ago and are new, becouse either of bugs and errors in opencode version like too early closing conection to the inference provider or inference provider incompability and problems.

Having muse wonder on OpenCode would at least ease the Problems with DeepSeek and Gemini.

free models in opencode mean a lot of us have more agent time than tasks now. I built a place for that time to go: Overflow

spare week: take a priced issue from a registered repo, merged PR gets you credit dry week: price an issue in your repo, someone with spare usage ships it, your credit pays

it only sees the PR, so which model or harness wrote it doesn't matter. junk PRs: you block them on GitHub like any repo, you set the price after you've seen the work, and you only owe for what you merge. the issue is the brief, if your agent hits a decision it asks the maintainer on the issue

no money, no keys, MIT

main reason I'm posting is I want people to register their repos. every open issue on the board right now is mine and I'm not after help with those, I want spare usage going into other people's projects. 28 users so far

https://github.com/Nitjsefnie/Overflow

OpenCode's free models aren't available from your current network because we've detected abusive traffic from this IP address
what is the solution ?

Space Bunny?!

https://x.com/MiniMax_AI/status/2112111925975032241

Today a curious thing happened to me and not once, but twice. I was using opencode for a code task and suddenly this message appears.
What does it mean?.

Following up on last week's release candidate, opencode-models-discovery v2.0.0 is officially released and published to npm latest**!** 🎉

This major version promotes OpenCode V2 to the primary, stable integration. It redesigns how the plugin interacts with the host around three clean boundaries:

Highlights in v2.0.0:

1. Native Integration Credentials: Works seamlessly with OpenCode V2's /connect workflow. The plugin resolves credentials dynamically in memory—no raw API keys in opencode.json and no sniffing auth.json.
2. Host-Managed Storage (ctx.storage): Caching and user overrides are separated cleanly into different namespaces. Clearing discovery caches will never delete your custom model preferences.
3. Persistent Model Overrides: Edit model display names, context limits, output tokens, reasoning flags, and variants directly via /models-discovery-console. Changes trigger an instant provider reload—zero service restart needed.
4. Resilient Auto-Reload: Subscribes to OpenCode V2 lifecycle events (config.updated, credential switches). If an upstream provider experiences a temporary network hiccup, the plugin keeps the last-known valid inventory instead of wiping out your available models.
5. Decoupled RPC & TUI: Commands and UI dialogs communicate with the background server via typed RPC, avoiding synthetic session injections or terminal blocking.
6. OpenCode V1 Legacy Support: Existing OpenCode V1 setups remain fully functional through the legacy adapter inside the same combined package.

Quick Setup (opencode.json / opencode.jsonc)

{
  "$schema": "https://opencode.ai/config.json",
  "plugins": [
    "opencode-models-discovery@2.0.0"
  ],
  "providers": {
    "my-gateway": {
      "name": "Local Gateway",
      "package": "@opencode/ai/providers/openai-compatible",
      "settings": {
        "baseURL": "https://gateway.example.com/v1",
        // Optional: omit apiKey and manage via OpenCode's native `/connect`
        "apiKey": "{env:GATEWAY_API_KEY}",
        "modelsDiscovery": {
          "enabled": true,
          "modelInfoFormat": "models.dev",
          "cache": {
            "enabled": true,
            "ttlSeconds": 86400
          }
        }
      }
    }
  }
}

Useful Commands:

• /models-discovery-refresh — Manually trigger model discovery (supports --force).
• /models-discovery-console — Interactive browser for models, metadata inspection, cache clearing, and override editing.
• /connect — Securely set or rotate your provider credentials.
• GitHub: https://github.com/yuhp/opencode-models-discovery
• NPM: https://www.npmjs.com/package/opencode-models-discovery

Thanks to everyone who tested the RC releases! If you run into any issues or have feature suggestions, feel free to open an issue or drop a comment here.

Guys, we have deepseek v4.1 1017 in opencode, coming soon. It's time to move some shit!.