feat(opencode): add iFlow provider for web tools#31515
Open
zhengyanglsun wants to merge 1 commit into
Open
Conversation
Contributor
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
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.
Issue for this PR
Closes #
Type of change
What does this PR do?
Adds an opt-in iFlow provider path for OpenCode's existing
websearchandwebfetchtools.When explicitly configured,
websearchcalls iFlowPOST /api/search/webSearchandwebfetchcalls iFlowPOST /api/search/webFetch:The current default behavior is unchanged. Setting only
IFLOW_API_KEYdoes not change the selected provider.OPENCODE_ENABLE_IFLOW=trueis supported only for tool availability checks.The implementation also normalizes iFlow search/fetch responses into model-friendly text and keeps API keys and Authorization headers out of tool output and metadata.
How did you verify your code works?
Ran the focused tool tests:
bun test --timeout 30000 test/tool/iflow-search.test.ts test/tool/iflow-fetch.test.ts test/tool/websearch.test.ts test/tool/webfetch.test.tsResult:
40 pass, 0 fail.Ran typecheck:
Result: passed.
Also manually smoke-tested
webSearchandwebFetchagainst iFlow using a localIFLOW_API_KEY. No API key or Authorization header is included in this PR.Screenshots / recordings
Not applicable; this is not a UI change.
Checklist