[GH-ISSUE #309] Feat: Allow configurable API URL for search providers #222

New issue

Open

opened 2026-10-18 14:03:55 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-18 14:03:55 +00:00

Owner

Originally created by @jaykayenn on GitHub (Sep 28, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/309

Search provider engines are currently hardcoded to the official service provider API.
Allowing configurable API endpoints will enable using local/3rd party/router providers.

A generic engine will not work as each engine type has its custom schema, which is already coded for each existing engine. Just add a custom endpoint field for users to configure.

Originally created by @jaykayenn on GitHub (Sep 28, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/309 Search provider engines are currently hardcoded to the official service provider API. Allowing configurable API endpoints will enable using local/3rd party/router providers. A generic engine will not work as each engine type has its custom schema, which is already coded for each existing engine. Just add a custom endpoint field for users to configure.

bsakaguchi commented

2026-10-18 14:03:55 +00:00

Author

Owner

@owui-terminator[bot] commented on GitHub (Sep 28, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

🟣 #67 feat: configurable perplexity base URL for web search - litellm is perplexity search API compatible
This issue is the closest match: it asks for a configurable base URL for a specific search provider, enabling alternative/local compatible endpoints instead of the hardcoded official service. The new issue has the same core need, generalized to all search providers.
by Classic298
🟣 #98 feat: add SearXNG as a search provider
This issue adds another self-hosted search provider and shows the project already supports provider-specific search engines with custom setup. It is related because the new request is about extending that model to allow custom endpoints per engine.
by 0be30301

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

@owui-terminator[bot] commented on GitHub (Sep 28, 2026):  🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#67](https://github.com/open-webui/computer/issues/67) **feat: configurable perplexity base URL for web search - litellm is perplexity search API compatible** *This issue is the closest match: it asks for a configurable base URL for a specific search provider, enabling alternative/local compatible endpoints instead of the hardcoded official service. The new issue has the same core need, generalized to all search providers.* *by Classic298* 2. 🟣 [#98](https://github.com/open-webui/computer/issues/98) **feat: add SearXNG as a search provider** *This issue adds another self-hosted search provider and shows the project already supports provider-specific search engines with custom setup. It is related because the new request is about extending that model to allow custom endpoints per engine.* *by 0be30301* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.

bsakaguchi commented

2026-10-18 14:03:56 +00:00

Author

Owner

@jaykayenn commented on GitHub (Sep 28, 2026):

Currently only SearXNG allow custom endpoint. Others should too (especially Exa and Tavily).

@jaykayenn commented on GitHub (Sep 28, 2026): Currently only SearXNG allow custom endpoint. Others should too (especially Exa and Tavily).

bsakaguchi referenced this issue

2026-10-18 14:03:58 +00:00

[GH-ISSUE #315] bug: OpenCode agent adapter is incompatible with OpenCode V2 #228