feat: add OpenCode provider support#67
Open
eetoc wants to merge 1 commit into
Open
Conversation
eetoc
force-pushed
the
feat/opencode-cli-support
branch
from
6e1fd0d to
3166c5d
Compare
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
1 participant
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.
Summary
opencodeprovider normalization, validation, UI selection, SDK/docs coverageagent-compose-runtime-jswith model/system prompt plumbing and session state reuseopencode-aiin the guest imageTests
npm run typecheck && npm run test:unitinruntime/javascripttask testGOFLAGS=-buildvcs=false task lintGOFLAGS=-buildvcs=false task buildgit diff --checkNote: plain Go build/lint VCS stamping fails in this
/tmpworktree witherror obtaining VCS status; the same gates pass withGOFLAGS=-buildvcs=false.