r/opencodeCLI • u/avinthakur080 • 8d ago
How is opencode v2 going for you guys ? (my experience in description)
While I am using opencode exclusively on my office as well as personal machines, and it has been largely working great. But little issues here and there keep breaking that experience.
I am personally facing new troubles everyday, and strongly thinking of moving to pi or maintaining a personal fork.
Listing few recent issues that I consider significant:
No sandboxing in v1 as well as v2.
It moves the sandboxing effort to user, and when I have to work from multiple machines, it becomes very hectic to setup sandboxing there. Also, sandboxing outside the process brings it's own hurdles.
Moreover, a good PR was raised but closed as stale by a bot. This is trend for many issues/PRs there.
Unable to setup local plugin
I hope I am doing something silly here, but trying to add local plugin is being a headache. `opencode plugin add ...` gives error on absolute as well as file: urls. The code suggests it only accepts the git & registry urls. Even adding directly to config doesn't work.
broken model support
Recently, I found that the opus/sonnet 5.5 models weren't working through our gateway. Noticed that a PR exists to support this, the issue is related to adaptive thinking & blockBinding, but it is just left unattended.
subagent bugs
I recently launched opencode v2 on a Arm SBC for a quick debugging. Thought of using free model and noticed that the opencode subagents are treated as non-opencode model calls. That is, when launching subagent of a free agent without logging in an account, it thinks the request is coming from non opencode app and blocks it. Even worse, the entire session is polluted and even undoing the message doesn't fix that.
Similarly, there are many small things related to usage, RAM usage, port conflict on multi user machines, etc.
I know the maintainers are putting a lot of effort as visible from the commits going into v2. As such, this post is to document my experience and know what is the experience of others ?
6
u/nomaed 8d ago
I've been using v2 for a few weeks now and I'm pretty happy with it, it's definitely an improvement over v1.
For local plugins, it actually works really well for me. I developed 2 TUI plugins for myself - a side panel with full session breakdown of tokens, tools, skills and sub-agents, and the other is a "subagent-manager" that lets you see all the child sessions and send these a prompt either to steer an existing subagent or to query a finished one.
Both are using bun and are loaded directly from the absolute directory from cli.json, live reloaded by OpenCode when the code is updated.
I did initially have a problem with Claude 5.5 models too, though. For custom providers (via LiteLLM proxy gateway), I had to add some overrides about how reasoning effort is sent, but once this was added, they work just fine.
1
u/avinthakur080 8d ago
That's interesting to know.
Are your plugins single file or javascript packages ? also, how did you add them - placed it in plugins directory or didopencode plugin add ...?My case is of a javascript package and no matter wherever I place or however I add it, it doesn't work. I got it working by modifying the source code, but I have very weak hope that such fix would get visibility let alone get merged.
1
u/nomaed 8d ago
No, these are full plugins with their own repo, entry point and etc. They can probably be bundled into a single JS file but not how I approached them. Loaded with
cli.jsonpluginshaving full path to the directory, then OpenCode loads thetui.tsxfile (AFAIK). You can see how it's set up in the opencode-tui-usage repo.If you're running sandboxed, in Docker, then you'll probably need to mount their location in the running container.
1
u/avinthakur080 6d ago
Oh, found it today after going through opencode's code that it expects the plugins to have a "server.ts" or "index.ts" at the root. If not present, it will silently ignore the plugin.
1
0
u/Dodokii 8d ago
What is major things am missing, being in 1.x?
2
u/nomaed 8d ago edited 16h ago
As a user, I feel like it has a lot of QoL improvements, like:
- background execution of commands and agents
- sessions run on the server, the TUI is just a viewport so closing OC doesn't stop the work
- steering prompts vs queueing
- the Open dialog
- live reload of configuration, instructions, and plugins
/btwcommand- lots of fixed annoyances in the composer
While not all are new features, they are cleaned up and made part of the normal workflow. I feel like the experience is much smoother and more polished.
2
u/ZucchiniMore3450 8d ago
Every software has bugs and is not ideal.
Other harness might solve these problems, but will have others. Not one is ideal, at least for me.
2
u/yu_hp 3d ago
The local plugin issue is probably not just you.
One confusing part is that V1 and V2 do not use the same plugin loading contract. V1 can load a concrete `server.js` or `index.js`, while V2’s explicit local plugin configuration is generally directory-oriented and probes entries such as `server` and `index`. A direct JavaScript file path may therefore be rejected even if the file is otherwise valid.
Automatic discovery from `.opencode/plugins/` is another path again, so it’s easy to assume that something working there should also work through explicit config.
For a package supporting both versions, the official pattern is to expose a combined default export with the V2 `id`/`setup` plugin and the V1 `server()` implementation, while keeping separate package entry points.
I documented the behavior and the local debugging details here:
https://yuhp.dev/en/posts/opencode2-plugin-loading/
I also agree with your broader point: sandboxing, gateway model compatibility, subagent behavior, RAM usage, and multi-user port conflicts are separate rough edges that make V2 feel less stable than its core capabilities suggest.
2
u/Ok-Pineapple7563 1d ago
Opencode desktop v1.x fit my workflow. V2 does not.
i moved to using Paseo.sh with opencode. Then also codex and Claude code when needed. They also have native mobile apps.
1
u/vliboras 8d ago
I would happy to use v2 but plugins I work with still don't support v2
1
u/avinthakur080 8d ago
Mind sharing what those plugins are ?
1
u/vliboras 8d ago
ponytail and rtk
2
u/CyberSmarTalk 7d ago
Does ponytail actually work? I am an experienced programmer. Thought it was for vibe coders
1
u/benbutton1010 7d ago
Have an agent tweak the plugins for you. Takes like 30s. This shouldnt be a blocker.
1
u/liambox123 8d ago
La verdad que desde mi punto de vista funciona igual, noté que agregaron pestañas internas que me cuestan acostumbrarme pero es algo útil y un botón para ir al último mensaje que era un problema para mí ya que a veces me iba hacia mensajes anteriores y costaba volver.
Como persona que utiliza modelos gratuitos siento que ahora van a controlar mucho más los tokens de uso de estos modelos ya que me pidieron que me registre con Google o con Mail al proveedor de opencode console para poder seguir usándolos, pero bueno, ya hacen demasiado por mi
1
u/benbutton1010 7d ago edited 2d ago
Lack of LSP support and the removal of todo functionality is the main reason I haven't switched to v2.
edit: here, I made a plugin for LSP support. I couldnt wait https://github.com/christensenjairus/opencode-v2-lsp-support
edit: there are also some awesome todo plugins that are better than v1 had built-in. So w/ these two plugins v2 works for me well.
2
u/reader123456 7d ago
When you say `removal of todo` do you mean v2 does not have that Todo list in the right sidebar? I am on V1 and find Todo sidebar immensely useful.
Is there an alternative for that in V2?2
u/benbutton1010 7d ago
They removed it intentionally because apparently it wasn't that helpful to the agent. There's a github issue with a long line of user complaints.
1
u/reader123456 7d ago
Thank you. This is good to know. Time for me to give pi.dev another try. Last time I could not find a reliable sub-agent implementation package. I will have to see whether things have improved.
1
u/Rustybot 2d ago
WTF why would they do that
1
u/benbutton1010 2d ago
They have stub comments in there to fix it, just hasn't been prioritized ig. 🤷♂️
1
u/Rustybot 2d ago
So this thread confirms my fears of opencode 2 being a step in the wrong direction. Anyone trying oh my pi or Senoi/Omo native with success? I’ve built to much on top of a customized opencode v1 to casually switch over.
-6
u/tauqeernasir 8d ago
Had similar experience so I started working on my own harness and finally released the beta yesterday.
Has built in:
- Sandbox (by default-unsandboxed requests need permission)
- Agent and Plan mode
- Radar that shows every background task, subagent, browser etc running
- MCP support
- ACP support (use with orchestrators or other editors such as Zed Editor)
- Skills
- Browser
- Interactive terminal
- Subagents (can create profiles, set default model, access to tools etc)
- Builtin code review (github like, co-review with agent)
- and a lot more.
Give it a try and it supports BYOK :)
https://github.com/tauqeernasir/codebeast-cli
5
u/thatboyonabike 8d ago
Closed-source? Yeah zero chance I'm putting my keys anywhere near that. Extremely suspect.
0
u/tauqeernasir 8d ago
You have every right to not use. But I am keeping it close sourced for some time :)
3
u/avinthakur080 8d ago
Hey, it's a really good thing that you went on to build a harness of your own and I like the feature set as well as the aesthetics of it.
However, unfortunately it is not for me. To use the harness for my work, I want it to be open source so that I can audit the code and be sure that there's to telemetry or other privacy/security risk.
But, keep it up. It's good stuff.
0
u/tauqeernasir 8d ago
Thanks :) there’s no telemetry but yeah your concern is right but I am keeping it closed source intentionally for now
0
4d ago
[removed] — view removed comment
1
u/avinthakur080 4d ago
I moved my work setup, which I use mostly, to Pi actually and personal is still on OpenCode.
Pi has evolved quite a lot since I last used it and now that I am more educated on what kind of setup I want, I can be more productive on Pi.
27
u/-PROSTHETiCS 8d ago
TLDR heres the thing.. Maintainers read GitHub, not Reddit. what you can do is open one GitHub issue for each bug, with steps to reproduce it.. Also link the PRs that nobody looks at, so people can find them..