nickjvandyke / nickjvandyke/opencode.nvim
feature: OpenCode v2 support
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.8k
- Forks
- 161
- Avg merge
- 13h 14m
- Merged PRs (30d)
- 5
Description
Prerequisites
- I searched the docs
- I searched existing issues
Is your feature request related to a problem? Please describe.
OpenCode v2 is in beta, it seems the server API is changing.
I'm quite curious about testing that new version, but not without the nvim integration.
Describe the solution you'd like
This FR is a starting point to see if there is some interest trying to already port the plugin to v2 api.
Of course I can help implementing this, just maybe need some direction how this should be configured (configuration flag, new plugin branch, ... )
Describe alternatives you've considered
Alternatives:
- switch to an ACP based integration, not integrated in the same way as this plugin
- create a fork and implement the changes there
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing OpenCode server integration and the current nvim plugin entry points, then compare them with the OpenCode v2 API. Clarify whether support should use a configuration flag, a separate branch, or another approach before implementation. Done means the plugin can use the v2 API without breaking the existing integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- ai, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100