yj-UdZddlmZddlZddlZddlmZmZmZddl m Z ej e Z iZded<ejZdd Zd dZd!dZd"dZdZd#dZd$ddd%dZd&dZd&dZd'dZdS)(u. Web Search Provider Registry ============================ Central map of registered web providers. Populated by plugins at import-time via :meth:`PluginContext.register_web_search_provider`; consumed by the ``web_search`` and ``web_extract`` tool wrappers in :mod:`tools.web_tools` to dispatch each call to the active backend. Active selection ---------------- The active provider is chosen by configuration with this precedence: 1. ``web.search_backend`` / ``web.extract_backend`` (per-capability override). 2. ``web.backend`` (shared fallback). 3. If exactly one capability-eligible provider is registered AND available, use it. 4. Legacy preference order — ``firecrawl`` → ``parallel`` → ``tavily`` → ``exa`` → ``searxng`` → ``brave-free`` → ``ddgs`` — filtered by availability. Matches the historic ``tools.web_tools._get_backend()`` candidate order so installs that never set a config key keep landing on the same provider they did before the plugin migration. 5. Otherwise ``None`` — the tool surfaces a helpful error pointing at ``hermes tools``. The capability filter (``supports_search`` / ``supports_extract``) is applied at every step so a search-only provider (``brave-free``) configured as ``web.extract_backend`` correctly falls through to an extract-capable backend. ) annotationsN)DictListOptional)WebSearchProviderzDict[str, WebSearchProvider] _providersproviderrreturnNonec<t|ts$tdt|j|j}t|t r|stdt5t |}|t|<dddn #1swxYwY|0t d|t|jdSt d|t|jdS)uRegister a web search/extract provider. Re-registration (same ``name``) overwrites the previous entry and logs a debug message — makes hot-reload scenarios (tests, dev loops) behave predictably. z>register_provider() expects a WebSearchProvider instance, got z-Web provider .name must be a non-empty stringNz(Web provider '%s' re-registered (was %r)z!Registered web provider '%s' (%s)) isinstancer TypeErrortype__name__namestrstrip ValueError_lockrgetloggerdebug)r rexistings ?/home/ragecks/.hermes/hermes-agent/agent/web_search_registry.pyregister_providerr0sa h 1 2 2  ->>* - -    =D dC J JHIII $$>>$''# 4$$$$$$$$$$$$$$$ 6 $x..)      / $x..)     s%B11B58B5List[WebSearchProvider]ct5tt}dddn #1swxYwYt |dS)z0Return all registered providers, sorted by name.Nc|jSNr)ps rz list_providers..Rsqv)key)rlistrvaluessorted)itemss rlist_providersr)Ns **Z&&(())*************** %-- . . ..s ';??rrOptional[WebSearchProvider]ct|tsdSt5t|cdddS#1swxYwYdS)z5Return the provider registered under *name*, or None.N)r rrrrrr s r get_providerr,Us dC t ,,~~djjll++,,,,,,,,,,,,,,,,,,s,AAApath Optional[str]c ddlm}|}|}|D]/}t|tsdS||}0t|t r(|r|SnF#t$r9}t dd ||Yd}~nd}~wwxYwdS)zGResolve a dotted config key from ``config.yaml``. Returns None on miss.r)load_config_readonlyNzCould not read config %s: %s.) hermes_cli.configr0r dictrrr Exceptionrrjoin)r-r0cfgcursegmentexcs r_read_config_keyr:bs J::::::""$$ # #Gc4(( tt'''""CC c3   CIIKK 99;;  JJJ 3SXXd^^SIIIIIIIIJ 4s,BAB C/CC) firecrawlparalleltavilyexasearxngz brave-freeddgs configured capabilityc4t5tt}dddn #1swxYwYd fd d d|r^||}| |r|S|td|ntd |fd |D}t|d kr|d StD]3}||}||r|r|cS4dS)uResolve the active provider for a capability ("search" | "extract"). Resolution rules (in order): 1. **Explicit config wins, ignoring availability.** If ``web.{capability}_backend`` or ``web.backend`` names a registered provider that supports *capability*, return it even if its :meth:`is_available` returns False — the dispatcher will surface a precise "X_API_KEY is not set" error to the user instead of silently routing somewhere else. Matches legacy :func:`tools.web_tools._get_backend` behavior for configured names. 2. **Single-provider shortcut.** When only one registered provider supports *capability* AND ``is_available()`` reports True, return it. 3. **Legacy preference walk, filtered by availability.** Walk the :data:`_LEGACY_PREFERENCE` order (firecrawl → parallel → tavily → exa → searxng → brave-free → ddgs) looking for a provider whose ``supports_()`` is True AND whose ``is_available()`` is True. Matches the historic ``tools.web_tools._get_backend()`` candidate order so users with credentials but no explicit config key keep landing on the same provider as pre-migration. This is the path that fires when no config key is set — pick the highest-priority backend the user actually has credentials for. Returns None when no provider is configured AND no available provider matches the legacy preference; the dispatcher then returns a "set up a provider" error to the user. Nr!rr boolcdkr!t|Sdkr!t|SdS)NsearchextractF)rDsupports_searchsupports_extract)r!rBs r_capablez_resolve.._capablesR  ! !))++,, ,  " "**,,-- -ur#c t|S#t$r,}td|j|Yd}~dSd}~wwxYw)zDWrap ``is_available()`` so a buggy provider doesn't kill resolution.z$provider %s.is_available() raised %sNF)rD is_availabler4rrr)r!r9s r_is_available_safez$_resolve.._is_available_safesd (()) )    LL? M M M55555 s # A!AAzz_resolve..sJ 8A;;--a00 r#r)r!rr rD) rr3rrrrr&len_LEGACY_PREFERENCE)rArBsnapshotr eligiblelegacyrJrMs ` @@r_resolverXs< $$ ##$$$$$$$$$$$$$$$ << ++  HHX$6$6 O   LLN     LLUJ   ??$$H 8}}{$<<''  "" !""8,, !OOO 4s ,00rBc dd}|s'|dvr#td|dptdd}|sd S||} d d lm}|}|jD]s\}}t |t r|d s0|jr8|j d krD| ddd}|||kr|cStn2#t$r%} t d| Yd } ~ nd } ~ wwxYwd S)uReturn the plugin key of a *disabled* bundled web plugin that would have provided the configured backend, or None. When a user sets ``web.extract_backend: firecrawl`` (or the search equivalent) but also lists ``web-firecrawl`` in ``plugins.disabled``, the provider never registers and the dispatcher would otherwise emit a misleading "No web extract provider configured. Set web.extract_backend to ..." error — even though the backend IS configured correctly. The real fix is to re-enable the plugin. This helper detects that case so the dispatcher can point the user at the actual cause (issue #40190 follow-up: pi314's disabled-plugin symptom). Pass ``capability`` ("search" | "extract") to resolve the configured name straight from ``config.yaml`` (``web._backend`` → ``web.backend``). This is more reliable than the resolved backend the dispatcher fell back to, since a disabled provider fails the ``_is_backend_available`` gate and the dispatcher silently drops to the shared default. An explicit ``configured`` name still wins when given. Matching is by convention: bundled web plugins live under the ``web/`` key with the provider ``name`` differing only in hyphen/underscore (``brave-free`` provider ⇄ ``web/brave_free`` key, ``firecrawl`` ⇄ ``web/firecrawl``). We normalize both sides before comparing so every bundled provider is covered without hardcoding a per-vendor table. srr cv|ddS)N-_)rlowerreplace)r[s r_normz'_disabled_web_plugin_for.._norms*wwyy  ((c222r#)rFrGweb_backendbackendNr)get_plugin_managerzweb/zdisabled via config/rRz%disabled-web-plugin lookup failed: %s)r[rr r)r:hermes_cli.pluginsre_pluginsr(r r startswithenablederrorsplitr4rr) rArBrawantrepmr$loadedvendorr9s r_disabled_web_plugin_forrqs83333  *(=== Uz$;$;$; < < 2y11  t 5  DC999999   ! !;,,..  KCc3'' s~~f/E/E ~ |444YYsA&&q)FuV}}$$ %  CCC rs@#"""""''''''''''777777  8 $ $,. ----     <////,,,,0VVVVr8^b888888v33334444r#