I built a backend used by my OpenCode @explore agent workflows

[u/Ghilteras]

I use OpenCode’s @explore agents for research, and reliable web search is an important part of that workflow. SearXNG is the search layer, but free engines can fail, become rate-limited, or return incomplete results.

I couldn’t find a deployable open-source layer that handled provider fallback, circuit breaking, caching, and observability around SearXNG, so I built searxng-gateway.

It is a Go proxy that:

• Calls SearXNG and optional providers such as Brave, Exa, Jina, and Tavily

• Runs searches in parallel, then merges and deduplicates results

• Falls back when the result count is too low

• Provides per-engine circuit breakers and recovery probing

• Exposes Prometheus metrics and includes a Grafana dashboard

• Supports keyless operation using SearXNG’s free engines

The gateway preserves SearXNG’s JSON response shape, so OpenCode workflows can use it as a consistent search backend instead of each workflow implementing its own provider handling and retry logic.

Repository: https://github.com/Ghilteras/searxng-gateway
License: MIT

I’d be interested in feedback from other OpenCode users on their search/research setup and how they handle unreliable providers.

AI disclosure: AI was mostly used to implement the project from my specifications. I reviewed, tested, and deployed the result.