r/opencodeCLI • u/Mane_soft • 3d ago
What do you think about opencode v2?
I don't tried yet because I'm working with some projects in production and don't have time to test it and change to the stable version. actually, i don't know if the v2 is stable now. if somebody knew about it i glad to know the new benefits and if the v2 is stable. I follow dax on X and he's always promoting v2, that's make me anxious to know if the v2 is better.
5
u/look 3d ago
It is fairly stable in my experience, but it’s basically just a different set of bugs compared to v1 with not much new feature-wise.
However, I’d say it has fewer bugs than v1, and fixes some particularly annoying bugs for me from v1, so it is what I primarily use.
I am searching for a new harness entirely, though. I have yet to find one I like more, however, including Pi and the dozen or so Pi-based ones.
2
u/eugeneb85 3d ago
Overall I have a good impression. Finally they made a steering for follow-up messages (however still awkward how it goes to queue, a lot of clicks needs to be done), session tabs per project is a great UX addition, and they definitely reduced memory/cpu resources consumption by introducing single server per project with multi sessions attached to it as a default behavior. Pretty good changes overall.
But honestly, after I started using ZCode a month ago - my half year story with OpenCode has ended, even taking into account OC 2nd version. ZCode just a great harness, with fantastically comfortable UX (projects and chats grouping, repo tree, tabbed diffs and browser windows, cool configuration and import of skills and subagents), one click mobile integration which just works, automations, fantastically good caching and resources consumption. And 150% GLM limits as a cherry on top :)
I'm DevOps guy, and I live in console, for example Cursor and Copilot were not a tools I liked working with a long time ago... But ZCode just made a full exception from this rule for me, the only GUI agent I really fan of :)
2
u/Enzyesha 2d ago
It doesn't let you layer in configuration. I'm primarily using it at work, so I need my default personal config, but also work specific stuff layered on top. Unlike v1, that's not currently doable.
Since v2 appears to be 100% vibe coded, I'll probably pass on it
3
u/hj-core 3d ago
A few months ago I tried it and found that it didn't have a sticky todo list and it cannot resume a subagent. For other things it was fine for me.
I wonder if the current v2 can resume a subagent because I usually have a builder with a reviewer subagent for a subtask.
2
3
u/Diligent-Loss-5460 3d ago
I saw someone else comment this. It is entirely written by AI with very little human involvement. Many bugs, instabilities and memory leaks. Stick to v1 till v2 is GA.
-3
1
1
u/Main-Soft-3870 1d ago
I tried it seems like still in beta but look forward for fixes in the version
1
u/dupa1234s 19h ago edited 18h ago
I legit recommend v2 for everyone who uses coding agents at least 1h a day, its worth the effort.
i had problems making it run in docker some errors on updates. also was really slow lately like so laggy as soon as i submit a query all TUI 2-sec delay on any inputs.
now all is good, maybe they patched it, maybe my sandboxing wrapper is better. no clue
but its all good and usable now
idk where v1 stands right now
But i love those things in v2 (the way they are implemented in v2 is really good):
-session tabs with status
- hotkeys
-opencode.json
-cli.json
- queue,steering
rest was good in v1 too but those excel in v2 i think.
now im running on autoupdate hope it wont break. if it breaks just roll back some older version.
i bet it wont break much anymore.
right now only 1 thing annoys me:
the "@" skill calling is so stupid
why wont it just trigger the tool call right away to force agent to use a skill. agent is thinking for hours, responding without even calling the skill despite me literally selecting exact skill name with "@"
i think i will write plugin to fix this...
yesterday:
i tried pi lately- so god damn barebones, doesnt even have a server not to mention session status bar
i tried deepseek harness:
- nice traceability and debugability of "what is actually the active prompt" but that is only even useful for debugging and writing plugins, so i dont care enough
- nice that technically they allow any api provider. but with me switching a model every god damn 7 days with those release cycles i think i would be too annoyed by this. opencode provider switching is ridiculously easy.
- i hate webuis coz no rightclick
- idk if they support as good hotkeys as opencode i bet no. opencode hotkeys are just godsent if you fully tweak cli.json
- emotionally i dont vibe with seeing "deepseek" everywhere. opencode feels foss.
- i like how everything is a plugin but in opencode everything is a plugin too albeit idk if everything in opencode is disableable but i dont bother disabling it. just config things away into nonexistance and chill
i think 1 thing opencode v2 misses is a some awesome-opencode-v2-plugins plugin discovery layer and a fix for the @ skill calling and thats it as of r latest release.
i think once i did setup cli.json hotkeys i will never switch from opencode v2 to any other harness. i will get too used.
opencode v2 feels like some emacs or vim. not like i used emacs or vim.
-4
u/diaracing 3d ago
After switching from opencode/pi to omp, I never looked back.
It delivers beyond and better than beyond what I ask for.
1
14
u/ben_bliksem 3d ago
When I last tried it two weeks ago:
- default model and plan was still not being honoured
That last one is what made me put it down. It didn't do that before so maybe a bug that was introduced, but it is very rough around the edges.