feat: sync opencode foundation tail#48
Merged
Merged
Conversation
This was referenced Apr 20, 2026
2 tasks
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.
Summary
Sync the upstream opencode foundation and provider tail needed for the v1.4.11 graft slice.
Restore compatibility surfaces around
Env,Provider,ProviderAuth,ProviderError,ProviderTransform, andModelsDev.Preserve ripgrep
partialresults across JSON serialization and align the/findresponse to return{ items, partial }.Why
PR 9a is the foundation-provider tail of issue #27. The core lane stays inside opencode-internal foundation work under
providerandfile.This PR includes two narrow compatibility exceptions that are required to keep that slice coherent:
packages/opencode/src/env/index.ts: upstream provider wiring now depends onEnv.Service, so this file bridges the new Effect service shape back into PawWork's existing sync surface.packages/opencode/src/server/instance/file.ts:Ripgrep.search()now serializes{ items, partial }, so the/findroute schema needs to match the actual response contract.Reviewed against the three-question philosophy: this is the smallest sound PR for the 9a lane, the remaining scope is sufficient for the upstream sync goal, and the verification plus scope notes are intended to make the slice reassuring to merge.
Related Issue
Part of #27
How To Verify
Screenshots or Recordings
N/A, no visible UI changes.
Checklist
devbranch