Comment by ghrl
4 days ago
I've been using OpenCode V2 since it first appeared on the website, and I can only repeat the positive views on usability, the client/server model and self-awareness/ability to edit it's config and write plugins.
I'd like to mention two other impressive things about OpenCode.
First, their issue tracker on GitHub works really well. They have the OpenCode GitHub App connected, and for any bug report it reads the issue, tests on the mentioned version and latest dev branch, and comments the findings along with a reproduction script. For TUI Bugs it even records a video. And all that in less than two minutes, usually.
https://github.com/anomalyco/opencode/issues?q=is%3Aissue+st...
Another thing they are working on is opentunnel, where you can tunnel services to https on <random>.opentunnel.xyz and its subdomains. What's notable is that the subdomain is persistent and unique to you, and a wildcard ssl cert is actually generated on your machine, so the platform cannot see the traffic. Their primary use case seems to be making the OpenCode Server usable from anywhere, but it can do much more with their cli:
> the client/server model
I see people talking about this being new in v2 everywhere but it's not the case. What's new is that it's the default (and also not really since `opencode service` and `opencode serve` start two different things). But in v1 it was very possible to run one opencode instance and have multiple clients connect to it (like Openchamber and neovim).
issue tracker is awesome, will have to copy that for sure!
The opentunnel feature is probably related to the "official native apps that are in the coming" mentioned in the article
Try pangolin for tunneing , it works so well.