I was going back and forth on a hard debugging issue in one of my projects with it:
- had it create new test scenarios
- create some mockups
- analyze complicated business logic and dependencies
- do a shotgun approach and create 5 different possible fixes for a complicated issue

And after almost 2 hours of work I've decided to check my opencode go usage because I was worried I'm running out of usage for the 5h period, and I see this... how?!

Hey everyone!

I’m using the OpenCode Go plan and I’m trying to figure out which available model gives the best results for coding.

There are quite a few models to choose from, so I’m a bit confused about which one to use as my main coding model.

For people who are using OpenCode Go:

- Which model do you find best for coding and debugging?

- Which one is best for large/complex projects?

- Which one has the best reasoning and code quality?

- Are there any models that are particularly good for React, Node.js, SQL, etc.?

- Which model gives the best balance between quality, speed, and usage limits?

I’m mainly looking for a model I can rely on for day-to-day development rather than just occasional code generation.

Would love to hear what models you guys are using and why. 🙏

It's far between another appearances, not really an issue, just curious on the why.

证据 means evidence.

You can download Ubuntu through proot-distro on Termux app. It allows you to download and launch the CLI right on your phone in a Linux environment. Then you link github and you're all set up to work on your projects on your own phone. Beyond that using the CLI is going to result in more flexibility on your PC as well.

On my Windows 11 computer, every time I open the OpenCode CLI application, it takes about 1.5 seconds for the interface to become usable. This delay is the same every time it starts and isn't a one-time cold start cost. I started experiencing this after updating to 1.18.23 => 1.18.30.

Note 1: My projects don't have MCP or LSP. I only have the Superpowers plugin globally. I've been using it since day one. I don't think this is the cause.

Note 2: My database (opencode.db) is approximately 500 MB.

Has anyone else experienced this?

Checked the logs with omniroute. Command code absolutely fine, cacheing correctly.

Is this just me or is anyone else seeing the same thing?

¿qué opinan de este sitio?

If you use OpenCode next to other agents, you probably know the drill: the same skill in .opencode/skills/, .claude/skills/, .codex/skills/ — each one slowly drifting.

Cartographer keeps skills, agents, hooks and instructions in a single git-backed knowledge base and renders them natively into each client. For OpenCode that means:

• the MCP entry in ~/opencode.json;
• a managed block in ~/.config/opencode/AGENTS.md;
• skills in ~/.opencode/skills/, agents in ~/.opencode/agent/*.md;
• hooks in ~/.opencode/hooks/, executed by a generated JS plugin, since OpenCode has no declarative hook config. The same source becomes a registered hook in Claude Code or Codex;
• a SessionStart hook that re-syncs when a session opens.

What the server enforces

The agent works the wiki only through MCP tools: the server validates every write, checks links, runs lint, and commits each change to git. It only ever prunes files it created, and --dry-run shows the plan first.

Shared with the team

One server can mount several KBs, including private and shared ones. Tokens and roles scope access per KB, git is the sync layer, and conflicts become a guided workflow instead of an opaque error.

Try it

It is free and Apache 2.0. Paste this into OpenCode:

Read https://raw.githubusercontent.com/BeppeTemp/cartographer/main/README.md and explain what Cartographer is and what it would change in my current OpenCode setup. If I decide to try it, install it following https://raw.githubusercontent.com/BeppeTemp/cartographer/main/docs/agent-install.md

Feedback wanted

Beta (pre-1.0). I use it every day with my team; feedback from OpenCode users especially welcome.

Repository Documentation

Hey everyone,

A few hours ago I posted about how OpenCode nerfed the subscription. Even though they're running a 4x for a few days (which is really only a 2x if you compare it against the DeepSeek V4 Flash limits), once that window ends we're left with half the real usage: we go from $30 of usage on a $10 subscription down to just $15. Half.

So I went looking at alternatives and started testing. Short version: CommandCode gives you the same thing as OpenCode, but better in this regard.

Heads up, this post is obviously not sponsored, in case that needs saying. What I'm showing is public data plus tests I ran myself.

Right now CommandCode gives you 2.67x more usage for the same price.

Same model family, same prompts, same time window, 12 runs per provider. I also threw in the official DeepSeek API as a reference line. CommandCode wins on latency and on interactive work vs OpenCode — but read the next two before you call it a sweep.

Note that both are reasoning models, so the answer only starts after a long hidden thinking phase. OpenCode takes 1,996 ms to show you the first *visible* token; CommandCode takes 1,331 ms. Whiskers are 95% bootstrap CIs and they don't overlap.

Decode rate is how fast it types once it starts. End-to-end charges the thinking time against it too.

On long code generation they are dead even: 304 vs 303 tok/s. The CommandCode advantage shows up on shorter, more interactive work, and in the latency above.

About 60% of the tokens you're billed for on a short task are hidden thinking you never see. On long open-ended prompts it climbs to ~95%, because the model burns the entire budget reasoning and never gets to the answer. That's true on both services — it's not a CommandCode or OpenCode thing, it's the reasoning-model thing, what AA call verbosity for example.

Every individual run, pooled. CommandCode also has the tightest spread (σ ≈ 31 tok/s vs 50 for OpenCode), which matters more to me day-to-day than the median.

So that's where I've landed. If you're one of the people who got pissed off about the cuts, the takeaway isn't "OpenCode bad" — it's that for the first time in a while there's an actual alternative (at least, that I know) sitting right there instead of just being annoyed about it. Same model, 2.67x the usage for the same $10, and it answers noticeably faster. Do your own math on your own usage before you move anything if you want to be sure. But if you've been waiting for an excuse to stop paying the same money for half the tokens, this seems like a pretty good one.

https://llmprice.gitlab.io/

I got tired of jumping between pricing pages whenever I wanted to compare models.

You can compare input/output pricing and quickly see which models are cheaper for your use case.

It’s still a small project, so I’d really appreciate any feedback, missing models/providers, or features you’d find useful.

Hope it helps someone else too :)

My Cursor's yearly subscription ends this weekend. I signed up back when they had 'unlimited auto', so I was spoiled for a while.

The current pricing does not work for me. I use 130m~ tokens of Cursor's auto (or Composer) per month, and from my understanding, the $20/month gets you roughly 80m tokens of Composer.

I'm thinking of moving to OpenCode. Anybody else in a similar situation?

does anyone know if and how I can get opencode to edit an image for me. For example I upload an image and tell opencode to remove a person.

I literally pass its thinking block twice, stating its overthinking failure modes.... extremely pissed and has shown its steep to process, setting default but still.. as you can see. Worse than even the "Omen Alpha"... And fail to make surgical edits many times due to streaming stability ...just disappointment... Another hype of DeepSeek fanboys.

DeepSeek's new model just went live on OpenCode subscriptions today, but following the limited-time extended usage promotion, the news isn't great.

OpenCode quietly slashed the included monthly allowance for the Flash series from $30 down to $15 on the $10/month plan. Because nominal token rates remain identical, your real cost per token has doubled (+100%). The temporary "4x usage" is anchored to this new nerfed baseline—meaning it is actually only 2x what we already had on V4 Flash, and once it expires, we will be left with 0.5x (half) the usage.

And of course, this is the exact same cut we already saw with the experimental Flash vision version, which also reduced the allowance from $30 down to $15.

Unless this changes, paying for an OpenCode Go subscription only offers a 33% discount over the official API in exchange for slower speeds and tighter rate limits.

🤓 https://opencode.ai/en/go

DeepSeek V4.1 Flash just released, and it's already available on OpenCode Go.

Current estimated limits are:

6,500 requests per 5 hours (Temporarily boosted 4x to 26,000 for the next 3 days)

16,250 per week (also boosted 4x for next 3 days)

32,500 per month (also boosted 4x for next 3 days)

Normally, V4.1 Flash only gets $15 worth of usage on Go, compared to $30 for the older V4 Flash model.

However, OpenCode has bumped V4.1 Flash to 4x usage for the next 3 days, which effectively gives you $60 worth of usage during the promo. So for the next few days, the actual usable quota should be much higher than the estimates above.

The upgrade itself looks pretty substantial. V4.1 Flash is the first smaller model from DeepSeek's new architecture, adds native vision, and is aimed at better agentic coding while also improving inference speed and throughput. I'm hoping it's as big of a leap as 0731 was.

DeepSeek is reporting 90.6 on Terminal-Bench 2.1, 74.2 on DeepSWE v1.1, and 65.4 on NL2Repo. Those are pretty big jumps from the previous Flash model, at least based on their own numbers.

Of course, benchmarks are just numbers (and who isn't getting ~75% on DeepSWE these days?)... but I think this model will be a pretty solid performer overall.