New request
#1037: Feature request: Built-in SearXNG web search for Hermes Orchestrator with on/off toggle
We'll provision a sandbox, run an agent against the issue, and open a draft PR. You can pull the branch and iterate from there.
Please add native SearXNG web search as a built-in tool in hermes-webui, with a per-model toggle to turn it on or off independently.
Why the toggle matters
Users running multi-agent swarms will often have specific teams with their own MCP-based search tools already assigned - for example a dedicated research team running SearXNG and a scraping tool via MCP. If hermes-webui's built-in search is always on, it will conflict with and duplicate what those team agents are already doing server-side via their own tools.
The toggle solves this cleanly:
- ON - hermes-webui provides web search natively, useful for the orchestrator handling general questions in chat
- OFF - hermes-webui makes no search calls of its own; the agent's MCP tools handle all search activity without interference
Why per-model rather than global
Different agents in a swarm have different needs. The orchestrator may benefit from a built-in UI-level search for general chat, while team agents should be left as clean pass-throughs so their assigned MCP tools run without any conflict. A single global toggle cannot serve both cases.
Settings location
Settings → Models → [select model] → Built-in Tools → Web Search toggle
New user-facing search capability requiring per-model toggle UI, settings persistence, and backend SearXNG integration.
- api/routes/model_tools.py
- api/search/searxng_client.py
- static/js/settings/models.js
- static/templates/settings.html
- api/schemas/model_config.py