fix(opencode): let recall use server relevance - #4107
Open
arikmeyer wants to merge 1 commit into
Open
Conversation
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
recallPurposesetting; explicitnullomits both the purpose and preset quotas so server relevance can select contextmax_tokenscodingdefault and synchronize the shared recall implementation across agent integrationsThis fixes a concrete case where
autoRecall.limit: 1produced six quota slots and injected unrelated categories. OpenCode users can now choose server relevance without disabling automatic recall or query expansion.Type of Change
Testing
node --test examples/memory-plugin-shared/*.test.mjs(62 passed)npm test --prefix examples/opencode-plugin(28 passed)npm run check --prefix examples/opencode-pluginnode examples/memory-plugin-shared/sync.mjsgit diff --checkChecklist