Label: bug, priority: high, backend
Description: Currently, our primary search backend (SearXNG) frequently returns 500 errors or zero results, especially when running from cloud environments (Vercel, AWS). Major search engines (Google, Bing) often block our private instance's IP, leading to a degraded user experience where the AI must rely solely on public fallbacks which are also prone to rate-limiting.
Context:
Observed in
src/app/api/search/route.ts
where private instances fail and race public ones.
Cloud IP ranges are flagged as "bot activity" by primary providers.
Requirements:
Implement a more robust "Search Orchestrator" that can rotate between multiple providers.
Add support for rotating User-Agents and header randomization.
Goal: Achieve a 95%+ search success rate even under high load.
Label: bug, priority: high, backend
Description: Currently, our primary search backend (SearXNG) frequently returns 500 errors or zero results, especially when running from cloud environments (Vercel, AWS). Major search engines (Google, Bing) often block our private instance's IP, leading to a degraded user experience where the AI must rely solely on public fallbacks which are also prone to rate-limiting.
Context:
Observed in
src/app/api/search/route.ts
where private instances fail and race public ones.
Cloud IP ranges are flagged as "bot activity" by primary providers.
Requirements:
Implement a more robust "Search Orchestrator" that can rotate between multiple providers.
Add support for rotating User-Agents and header randomization.
Goal: Achieve a 95%+ search success rate even under high load.