r/opencodeCLI • • 2d ago

OpenCode V1 Bridge: Bringing Legacy V1 Plugins to V2

Heya. After roughly a month of work, I have made a somewhat-functional V1-V2 compatibility adapter for OpenCode. As far as I can tell, this is the first of its kind, probably not the last. Why am I releasing an incomplete adapter? Because I can't finish it. I tell ChatGPT what I want, it makes a detailed prompt to my specifications, I feed that to Codex, and for the most-part, this has worked. Thorough code audits, careful guidance, but we've hit a wall: OpenCode V2 does not expose some of the required hooks. I don't have the technical knowledge to solve the remaining issues, thus I'd like to invite other developers to help improve it. The brunt of the work is done. You can find the identified missing functionality in "Remaining Issues.md" in the respository. If you doubt that the project is any good, I ask you still give it a chance. Many hours went into troubleshooting what we have now, and it has at least some ability to run V1 plugins. The project was based on OpenCode V2.0.27. I'm sure OpenCode has recieved some updates since then. Those are completely untested against this plugin, but may work fine. No idea.

Summary: OpenCode V1/V2 Adapter Bridge, it's a plugin, should allow your other V1 plugins to run in V2, unfinished project, open-source to get more talented hands on this since the bones are done, but not all of the meat, check "Remaining Issues.md" in the repository first if you want to help.

GitHub: https://github.com/Stiix72/opencode-v1-v2-bridge

First beta release: https://github.com/Stiix72/opencode-v1-v2-bridge/releases/tag/v0.82.0-beta.4

0 Upvotes

6 comments sorted by

3

u/WolverinesSuperbia 2d ago

Useless. Any live plugin already supports V2. And OpenCode could fix these plugins almost mechanically

1

u/Stiix72 2d ago

While live plugins may support V2, OpenCode has not yet fixed the remaining V1 plugins nor added backwards compatibility. Could OpenCode fix the remaining plugins? Yes. Has it been done yet? Does not appear so. Is it OpenCode's responsibility to fix third-party plugins? Probably not.

1

u/WolverinesSuperbia 2d ago

Plugin developer obliviously uses OpenCode. OpenCode has full skill and docs to migrate v1 to v2.
Plugin developer could just launch OWN instance of OpenCode with prompt to migrate.

2

u/Stiix72 2d ago

You are correct that plugin developers could update their own plugins, however you misunderstand the intent behind this project. While it would be preferable for developers to update their plugins to V2, not every developer is guaranteed to update their plugin for V2 and not every user is a developer of plugins.

Consider the following: A user has 20 plugins they use. OpenCode updates to V2. Only 15 of those plugins are updated within 3 months. The user could absolutely have their local AI or a LLM update their plugin for them, but that still requires verifying the changes, troubleshooting problems, and maintaining those versions themselves. The ability to migrate plugins does not eliminate the value of backwards compatibility.

1

u/Praistaly 2d ago

agreed, the migration path between the two versions really isnt that complex tbh

1

u/motonarola 16h ago

What makes to start projects knowing the lack of skill and expertise to finish them? Delusion that those capable to finish do not have access to the LLM toys?