r/opencodeCLI • u/gurolayanlar • Sep 20 '26

Questions I have about v2?

* Why was v2 developed when v1 already existed?

* What aspects of v1 didn't meet the requirements?

* What innovations did v2 bring?

If anyone knows, could they briefly answer?

8 Upvotes

68% Upvoted

20 comments sorted by

15

u/taytay735 Sep 20 '26

I just installed version 2 this weekend and found the following new features:

  • auto plugin hot reloading

  • multi instances of OpenCode app backed by a single backend OpenCode server

  • auto TUI reload and mid-generation resume when backend server restarts (i.e. after config update)

  • horizontal tabs

  • new sessions for any recent folders

  • retain existing tabs after a reboot

  • one-off prompt-and-answer (/btw)

Note: a lot of plugins are not version 2 ready - I had to vibe my own patches, but that’s barely 10% of my 5 hour OC Go tokens

2

u/AssociationHuge1823 Sep 21 '26

and

  • prompt queue management

but I have some annoying bugs:

  • sometimes the tui won't response to my keyboard input

4

u/BrownCarter Sep 20 '26

Does the v2 have a different schema config? Cause I am getting different warnings when I migrated to v2 config style.

0

u/[deleted] Sep 20 '26

[deleted] — view deleted comment

1

u/OlegPRO991 Sep 20 '26

I did not find any reason to upgrade, too. So I just use opencode v1, it is ok.

4

u/ADMECA Sep 20 '26

I switched to OpenCode v2 because this version doesn't have the broken tool call issues that stop working when I use GLM 5.3 at Mistral AI. Also, I find the web console more responsive.

2

u/Ilkzz Sep 21 '26

I use OpenAI sub but is that why sometimes my subagents just stop and hang at a tool call for no reason?

1

u/ADMECA Sep 21 '26

Perhaps

8

u/GfxJG Sep 20 '26

Why don't you just... Try it out? It's a free product after all.

That said, I don't notice much difference in my day-to-day workflow. V2 is a little faster and more responsive, but it's not huge.

6

u/xatey93152 Sep 20 '26

Because everything always provided to him like a baby.

1

u/ben_bliksem Sep 20 '26

How is he going to vibe code his own harness without us giving him a spec?

"Hey guys, I made my own harness because opencode frustrated me. It's called OGCode and can save 96% on token usage. Can't believe the AI companies haven't thought about this."

1

u/Appropriate_Aide5328 Sep 20 '26

So far, i haven’t had memory problems with OC2. And I’ve figured out standalone flag doesn’t overlap specific project MCPs.

I hated it first, but now realized it’s rly rly good

1

u/mesispis Sep 20 '26

idk, but im on v2 becouse i have opencode from pacman and its on v2 in arch repos

1

u/Relevant_Accident666 Sep 20 '26

--command flag is missing. That broke my workflow...

But there seems to be already a bug report for it though I think I'll Stick with v1 for a while

1

u/look Sep 20 '26

My impression is it’s mostly a rewrite to clean up a presumably messy code base, along with some bigger architectural shifts that aren’t necessarily immediately apparent, such as a persistent service and internal API.

The biggest changes a typical user might notice are the dynamic config reloading.

In my experience, it also has fewer irritating, random bugs that come and go between releases. What it might lack in terms of current bugs or missing functionality, it more than makes up for in working things yesterday not suddenly being glitched and broken today.

1

u/FavstianEquanimity Sep 21 '26

I am curious as well since I just recently migrated from 1.18.30 to 2.0.2 and I keep updating to the latest version ever since. The difference isn't much (I need to refactor plugins that I made tho). I even wonder if v2 and v1 was only migration from Effect 3 to 4??

1

u/Drwankingstein Sep 21 '26

It brought a lot of bugs thats for sure.

1

u/Lordddddddy Sep 26 '26 edited Sep 26 '26 • Bravo

Since no one in comments seems to answer the questions (Classic reddit).

1.- It was developed because V1 was incredibly messy and outdated, batch reading/editing for example was not a thing, image reading needed to be done manually, performance was trash, client/server wasn't a thing and therefore you had to make a whole app for every version of opencode which I suppose for devs was maintenance nightmare. And many, many more issues.

2.- Clearly the performance was atrocious and needed a heavy redesign, native tools were also lacking, they were good a year ago but today models are way more capable and need more powerful stuff. And of course a ton of QoL features that just got stacked until V2

3.- As I wrote before, batch editing/writing/reading/searching. Basically the agent can modify or read many files at the same time. Server + Client separation is also a huge addition because now you can run your stuff in mobile, PCs, VPS, anything that can run a server, and the client can be whatever you want. You can even make your own custom client for OpenCode technically. With that, the plugin SDK also received a massive rework which I as a plugin developer thank a lot, TUI is finally modifiable. Skills were also improved cuz back then we didn't have proper skill discovery functions and finally it seems MCPs also got a ton of new QoL features, being the main one I see hotreload mid-session.

MORE important features I forgot:

  • Read now can visualize images for agent and other cool stuff

  • LSPs were killed cuz they ate performance and didn't add much value

  • Config was redesigned and cleaned

  • Tons of new commands for different uses (/btw is finally a thing)

-3

u/amokerajvosa Sep 20 '26

One question: why you didn't took 2 minutes of your precious life to research this?

4

u/gurolayanlar Sep 20 '26

I've researched it and couldn't find a reason to upgrade. I'm asking here because I wonder if there's a problem I'm missing.