fix: use native OpenCode V2 provider runtimes - #153
Merged
Merged
Conversation
Contributor
|
🎉 This PR is included in version 0.10.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenCode V2 was registering Command Code through the legacy
aisdk:adapters. In a real image-bearing session, the provider base URL was not carried into requests reliably, so valid Chat Completions payloads returnedInvalid input; adding a manual provider block masked the bug.This switches only V2 to OpenCode's native Chat, Responses, and Anthropic runtimes. V1 keeps its direct AI SDK packages. The original 121-message failing session now resumes from an exported clone with its PNG intact, and a fresh PNG request succeeds without a provider block.
Validation:
bun run check— 235 tests, 671 expectations, lint, format, typecheckbun run verify:release-candidateMODEL_NOT_IN_PLAN)