o PL j|@sUdZddlmZddlZddlZddlZddlZddlmZddl m Z m Z e e ZiZded<iZded <d aeejjd d Zd%ddZd&ddZd'ddZd(ddZd)d!d"Zd*d#d$ZdS)+uProvider module registry. Provider profiles can live in two places: 1. Bundled plugins: ``plugins/model-providers//`` (shipped with hermes-agent) 2. User plugins: ``$HERMES_HOME/plugins/model-providers//`` Each plugin directory contains: - ``__init__.py`` — calls ``register_provider(profile)`` at import - ``plugin.yaml`` — manifest (name, kind: model-provider, version, description) Discovery is lazy: the first call to ``get_provider_profile()`` or ``list_providers()`` scans both locations and imports every plugin. User plugins override bundled plugins on name collision (last-writer-wins), so third parties can monkey-patch or replace any built-in profile without editing the repo. For backward compatibility, ``providers/*.py`` files (other than ``base.py`` and ``__init__.py``) are still discovered via ``pkgutil.iter_modules``. This lets out-of-tree users drop a single-file profile into an editable install without the plugin dir structure. New profiles should prefer the plugin layout. Usage:: from providers import get_provider_profile profile = get_provider_profile("nvidia") # ProviderProfile or None profile = get_provider_profile("kimi") # checks name + aliases ) annotationsN)Path)OMIT_TEMPERATUREProviderProfilezdict[str, ProviderProfile] _REGISTRYzdict[str, str]_ALIASESFpluginsmodel-providersprofilerreturnNonecCs$|t|j<|jD]}|jt|<qdS)uRegister a provider profile by name and aliases. Later registrations with the same name replace earlier ones — so user plugins under ``$HERMES_HOME/plugins/model-providers/`` can override bundled profiles without editing repo code. N)rnamealiasesr)r aliasr6/home/kuhnn/.hermes/hermes-agent/providers/__init__.pyregister_provider5s   rr strProviderProfile | NonecCs tstt||}t|S)z{Look up a provider profile by name or alias. Returns None if the provider has no profile (falls back to generic). ) _discovered_discover_providersrgetr)r canonicalrrrget_provider_profileAs  rlist[ProviderProfile]cCsJtstt}g}tD]}t|}||vr"||||q|S)zAReturn all registered provider profiles (one per canonical name).)rrsetrvaluesidaddappend)seenresultr pidrrrlist_providersLs   r# Path | NonecCsDzddlm}|dd}|r|WSdWSty!YdSw)z>Return ``$HERMES_HOME/plugins/model-providers/`` if it exists.r)get_hermes_homerr N)hermes_constantsr%is_dir Exception)r%drrr_user_plugins_dir[s  r* plugin_dirrsourcec Cs|d}|s dS|jdd}|dkrd|}nd|}|tjvr'dSz,tjj||t|gd}|dus=|j dur@WdStj |}|tj|<|j |WdSt yv}zt d ||j|tj|dWYd}~dSd}~ww) zImport a single plugin directory so it self-registers. ``source`` is "bundled" or "user", used only for log messages. z __init__.pyN-_bundledzplugins.model_providers._hermes_user_provider_)submodule_search_locationsz(Failed to load %s provider plugin %s: %s)existsr replacesysmodules importlibutilspec_from_file_locationrloadermodule_from_spec exec_moduler(loggerwarningpop)r+r, init_file safe_name module_namespecmoduleexcrrr_import_plugin_dirfs2       rEc Cs$trdSdatr#ttD]}|r|jdrqt|dqt}|durCt|D]}|r<|jdr=q0t|dq0zDddl }ddl }| |j D]2\}}}|ds`|dkraqRz t d |WqRty}z td ||WYd}~qRd}~wwWdStyYdSw) aPopulate the registry by importing every provider plugin. Order: 1. Bundled plugins at ``/plugins/model-providers//`` 2. User plugins at ``$HERMES_HOME/plugins/model-providers//`` 3. Legacy per-file modules at ``providers/.py`` (back-compat) Each step imports its plugins, which call ``register_provider()`` at module-level. Later steps win on name collision. NT)r..r/userrr.basez providers.z.Failed to import legacy provider module %s: %s)r_BUNDLED_PLUGINS_DIRr'sortediterdirr startswithrEr*pkgutil providers iter_modules__path__r6 import_module ImportErrorr<r=r()childuser_dirrM_pkg _importermodname_ispkgrDrrrrs@    r)r rr r )r rr r)r r)r r$)r+rr,rr r )r r )__doc__ __future__rr6importlib.utilloggingr4pathlibrproviders.baserr getLogger__name__r<r__annotations__rr__file__resolveparentrIrrr#r*rErrrrrs(        &