2. opencode 2.0 does not exists. I mean it: there is no release[1] and per their own instructions, `npm i -g @opencode/cli@latest` does not install opencode 2.0.
3. `Error: @opencode/cli's postinstall script was not run.` Not even running postinstall.js can fix that, neither on linux nor macos. And even if it works, in a couple of days or on the next upgrade it will fail again.
Fun fact: The npm release does not contain the code, it is downloaded by the postinsta script. Galaxy brain.
npm install -g --allow-scripts=@opencode/cli @opencode/cli- several poor security mistakes or choices that broke my trust
- trying to be closer to an IDE, all these harnesses want to be the interface to rule them all, that's not what I want in my harness
- doing things that another tool, which is harness independent, should own (multiple async/parallel agents)
- too much change dropped at once, so many breaking changes, several I cannot migrate at work without impacting the devs I support
I heard it from someone as well, but I cannot find the link or specific details.
Can someone summarise what are the security issues related to using opencode?
Do these issues still exist, especially in V2 ?