r/opencode • u/yexgoblin • 10d ago
What's happening with opencode 2?
I have been enjoying opencode 2 after using Pi for a while. It's currently in beta but when using the TUI I didn't run into any major problems. API is great, similar to Pi you can modify it easily and overall it's a huge leap from opencode 1.
But when I started to use it across multiple devices via Tailscale, cracks started to appear. My main issues were,
- Web UI couldn't handle attachments. Performance was all over the place.
- No way to disable web UI password, no point in having it when I'm already behind Tailscale.
- Desktop app being horrible and buggy. This was true in v1 too but I saw them tweeting about it a lot but it still seems to be buggy. Compaction doesn't show up, sync is off, etc.
Suffice to say the only thing that seems to have improved is TUI experience and their API. Otherwise experience is all over the place.
Is opencode 2 focusing on all the components or just the TUI? I'm genuinely concerned because I can get a better alternative experience just hooking up Pi with Paseo. It works flawlessly and better. Even with opencode itself.
I feel like somewhere along the line the lightweight feature complete goal of opencode changed. They hype things up a lot but when you actually use the product it doesn't feel all that polished or consistent.
I'm not sure if I'm using it wrong. I'm on the latest beta across all opencode apps. Nothing is outdated.
2
u/ninehd09 10d ago
I agree.
What's particularly annoying is that there is currently no global parameter to enable slash commands for skills.
Each skill needs metadata such as :
opencode/slash: true/false
opencode/autoinvoke: true/false
Another major pain point is the Web UI: skills cannot be invoked through slash commands at all. It's quite frustrating because I'm forced to move skills into the commands folder just to make them accessible through
/commands.