Repository navigation
[FEATURE]: Parallel Search: Improve api CALL #28216
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The Parallel branch of the websearch tool currently sends objective and search_queries[0] as the same string — the model's single query. That throws away the two complementary inputs Parallel's Search API is designed around: a natural-language objective for ranking by reasoning utility, and a small batch of diverse keyword search_queries for retrieval. As a result, agents on opencode end up chaining multiple single-query Parallel calls instead of taking advantage of Parallel's batched-query design — slower, more expensive, lower coverage per call.
Proposed enhancement: expose objective and additionalQueries (capped per Parallel's docs) on the websearch tool schema only when Parallel is the resolved provider (env override or flag). Wire them through to the Parallel MCP call. Adapt the field descriptions and tool guidance from docs.parallel.ai/search/best-practices so the model is nudged toward one batched call per intent rather than chained searches. Exa-only sessions keep the current schema unchanged.
I have a PR ready against this issue: #28219.
Activity
github-actions commentedon May 18, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:. Please use the Feature Request template, add[FEATURE]:to the title, and include the verification checkbox confirming the feature hasn't been suggested before._No response_.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
[-]Parallel Search: Improve api CALL[/-][+][FEATURE]: Parallel Search: Improve api CALL[/+]github-actions commentedon May 18, 2026
Thank you for updating the title to start with
[FEATURE]:and adding a description!However, this issue is still not fully compliant with our contributing guidelines. Here's what still needs to be fixed:
Missing required field:
The easiest fix is to close this issue and re-submit it using the Feature Request template from the issue creation page, which will include all required fields. Alternatively, you can edit this issue to add the missing checkbox.
Please update within 2 hours, or this issue may be automatically closed.
github-actions commentedon May 18, 2026
Thanks for updating the issue! It now follows the contributing guidelines. The feature request looks good with the verification checkbox checked and a clear description.
github-actions commentedon Jul 18, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.