߲j%4UdZddlmZddlZddlmZddlmZmZddl m Z eje Z ede e Zd ed <ej!edd Zdd Zd ZdZddZddZddZd ddd!dZd"dZd"dZddlmZddlmZddlZddiZdZ y)#uWeb Search Provider Registry. Populated by plugins via :meth:`PluginContext.register_web_search_provider`; consumed by the ``web_search`` / ``web_extract`` wrappers in :mod:`tools.web_tools`. Active selection, in precedence order (the ``supports_search`` / ``supports_extract`` capability filter applies at every step, so a search-only provider configured as ``web.extract_backend`` falls through): 1. ``web.search_backend`` / ``web.extract_backend``, then ``web.backend``. 2. The single capability-eligible provider that is registered AND available. 3. Legacy preference walk (``_LEGACY_PREFERENCE``) filtered by availability — the historic ``tools.web_tools._get_backend()`` order, so installs that never set a config key keep landing on the same provider. 4. Keyless free-tier walk (``_KEYLESS_PREFERENCE``), last resort. 5. ``None`` — the tool points the user at ``hermes tools``. ) annotationsN)Optional)ProviderRegistryis_available_safe)WebSearchProviderWeb)label provider_clsloggerz#ProviderRegistry[WebSearchProvider] _registrycL ddlm}|}|D]%}t|tsy|j |}'t|t r |j r|j Sy#t$r0}tjddj||Yd}~yd}~wwxYw)zGResolve a dotted config key from ``config.yaml``. Returns None on miss.r)load_config_readonlyNzCould not read config %s: %s.) hermes_cli.configr isinstancedictgetstrstrip Exceptionr debugjoin)pathrcursegmentexcs >/home/ubuntu/.hermes/hermes-agent/agent/web_search_registry.py_read_config_keyr$s J:"$ #Gc4('''"C # c3 CIIK99;   J 3SXXd^SII Js#A*AA** B#3&BB#c<td|dxs tddS)zN``web._backend`` (preferred) or ``web.backend`` (shared fallback).web_backendbackend)r capabilitys r_configured_backendr%5s% Ej\#: ; a?OPUW`?aa) firecrawlparalleltavily perplexityexasearxngz brave-freeddgs)r+r(r'keenablec ddlm}m}|t|z}t ||d|d|zS#t $r%}t jd|Yd}~tSd}~wwxYw)zKeyless walk order, starting at the ring cursor in :mod:`plugins.web.keyless_mcp` so resolution and dispatch agree on which vendor a fresh install starts at; the rest follow in ring order.r) _KEYLESS_RING _ring_cursorNz"keyless ring order unavailable: %s) plugins.web.keyless_mcpr0r1lentuplerr r_KEYLESS_PREFERENCE)r0r1startrs r_keyless_preferencer7Esb@Gs=11]56*]6E-BBCC @ 93?? @s), AAActj}d fd }d d}|rM|j|}| ||r|S|tj d|ntj d||j Dcgc]}||s ||s|}}t |dk(r|dStD]}|j|}|||vs|cStr@tD]3} |j| }|||s |jr|cS5ycc}w#t$r!} tj d| | Yd} ~ ad} ~ wwxYw) aResolve the active provider for a capability ("search" | "extract"). Rules, in order (see module docstring): explicit config wins even when ``is_available()`` is False (the dispatcher surfaces a precise "X_API_KEY is not set" error instead of a silent switch); then the single available capable provider; then the availability-filtered legacy walk; then the keyless free-tier walk; else None. c~tdk(r|jSdk(r|jSdS)NsearchextractF)boolsupports_searchsupports_extract)pr$s r_capablez_resolve.._capable^sM#-#9A     )3y)@##%  FK  r&c$t|tdS)Nz$provider %s.is_available() raised %s)rr )r?s r _availablez_resolve.._availableds F,RSSr&NzDs:= A&A!!A&r#cd d}|s|dvr t|}|sy||} ddlm}|}|jj D]g\}}t |t s|jds)|jr6|jdk(sF||jdd d |k(se|cS y#t$r }tjd |Yd}~yd}~wwxYw) u7Plugin key of a *disabled* bundled web plugin that would have provided the configured backend (``web._backend`` → ``web.backend``), or None. Lets the dispatcher say "re-enable web-firecrawl" instead of "No web extract provider configured". Resolved from config.yaml rather than the resolved backend because a disabled provider fails the availability gate and silently drops to the default. Bundled web plugins live under ``web/`` with the provider name differing only by hyphen/underscore, so both are normalized. 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. 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). c^|jjjddS)N-_)rlowerreplace)ss r_normz'_disabled_web_plugin_for.._norms"wwy ((c22r&)r:r;Nr)get_plugin_managerzweb/zdisabled via config/rCz%disabled-web-plugin lookup failed: %s)r[rrDr)r%hermes_cli.pluginsr]_pluginsitemsrr startswithenablederrorsplitrr r) rJr$r\wantr]pmkeyloadedrs r_disabled_web_plugin_forrjs 3 *(==(4   D C9  !;;,,. KC3$)?LL$99eCIIcSTDUVWDX>Y]a>a    C CCc.ttddS)z1Resolve the currently-active web search provider.r:r#rPr%r&rget_active_search_providerrns '1h GGr&c.ttddS)z2Resolve the currently-active web extract provider.r;r#rlrmr&rget_active_extract_providerrps ' 2y IIr&)Dict)Listhermes_home_key)hermes_constantsrsctj|}|tdtd|ddl}ddlm}|t|g|t|j|d|dS)Nzmodule z has no attribute r) warn_oncerC) _PLUGIN_COMPAT_LAZYrAttributeError__name__ importlibhermes_cli.plugin_compatrvgetattr import_module)rOtargetrzrvs r __getattr__rse $ $T *F ~wxl2DTHMNN2 h&v& 9**6!95vay AAr&)rrrD Optional[str])r$rrDr)rDr4)rJrr$rrDOptional[WebSearchProvider])rDr<)N)rJrr$rrDr)rDr)!__doc__ __future__rloggingtypingragent.provider_registryrragent.web_search_providerr getLoggerryr r __annotations__exportglobalsrr%rGr5r7rPrHrjrnrprqrr threadingrwrrmr&rrs$#G7   8 $2B /2 . "bo C 8v %^b%PH J> Br&