+ kHjqx:a0t$Rt^RIHt^RIt^RIt^RIt^RIt^RIt^RI t ^RI t ^RI t ^RI H t ^RIHtHt^RIHt^RIHt^RIHt]P.!]4t/tR]R &/tR ]R &/tR ]R &RsR ]R&RsR]R&Rs Rs!Rt"]!RR44t#/t$R]R&] PJ!4t&] !RRR7t'R]R&]!](4PS4PTPTR, R, t+RRlt,RR lt-R!R"lt./t/R#]R$&/t0R%]R&&]1!4t2R'R(lt3R)R*lt4R+R,lt5R-R.lt6R/R0lt7R1R/R2R3llt8R4R5lt9R6R/R7R8llt:R9R:lt;R;R<ltlt=R?R@lt>RARBlt?RCRDlt@RERF/RGRHlltARIRJltBRKRLltCRMRNltDRORPltER#)Qu6Provider module registry. Provider profiles can live in three places: 1. Bundled plugins: ``plugins/model-providers//`` (shipped with hermes-agent) 2. User plugins: ``$HERMES_HOME/plugins/model-providers//`` 3. Pip-installed plugins: distributions exposing a ``hermes_agent.plugins`` entry point (``module:func`` callable or a self-registering ``module``) 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()`` imports the bundled and pip-installed plugins once per process; the ``$HERMES_HOME`` plugins of the profile home bound at lookup time load into that home's own layer, so one process serving several profiles (multiplex gateway, Desktop ``serve``) resolves each profile's installs. User plugins override bundled plugins on name collision, 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) ContextVar) dataclassfield)Path)Any)ProviderProfiledict[str, ProviderProfile] _REGISTRYdict[str, str]_ALIASES_SOURCES str | None_current_sourcezlist[ProviderProfile] | None_PROVIDER_LIST_CACHEFg?cp]tRt^Ct$Rt]!]R7tR]R&]!]R7t R]R&R t R]R&R t R ]R &R t R #) _HomeLayeruiThe ``$HERMES_HOME/plugins`` providers of ONE profile home. One process serves many profiles (multiplex gateway, Desktop ``serve``) and each profile installs its own plugins, so user plugins are keyed by the home bound at lookup time instead of the home that happened to be bound at first discovery — that made a plugin installed in a secondary profile ``Unknown provider`` in Desktop while the same profile worked in a terminal (#88143). ``stamps`` are the plugin dirs' mtimes: a directory added by ``hermes plugins install`` while the process runs changes them, and the next lookup imports it without a restart. )default_factoryr registryr aliasestuplestampsNz float | Nonestamp_checked_at) __name__ __module__ __qualname____firstlineno____doc__rdictr__annotations__rrr__static_attributes__r7/home/ubuntu/.hermes/hermes-agent/providers/__init__.pyrrCs=,1+FH(F#D9G^9FE%)l)r"rzdict[str, _HomeLayer] _HOME_LAYERS_provider_registration_target)defaultzContextVar[_HomeLayer | None]_REGISTRATION_TARGETpluginsmodel-providerscV^8dQhRR/#returnNoner)formats"r# __annotate__r0bs==T=r"cRF=wr\\PPV4VR4pVfK5V!4K? R# \d"p\ P RY4Rp?KjRp?ii;i)aMirror profiles into the ``hermes_cli`` snapshots (auth registry, picker catalog) that are loaded. ``hermes_cli.auth`` takes its own snapshot of ``list_providers()`` when it is imported. If a plugin's imports pull that module in while :func:`_discover_providers` is still running, the snapshot is partial and later plugins never reach the auth registry ("Unknown provider", #102123). Calling back into auth once discovery is complete closes that window. Looked up via ``sys.modules`` on purpose: this layer must never import ``hermes_cli`` (that would run auth's top-level code mid-scan and risk a circular import). Never raises: registration must not fail because of the auth mirror. Nz%s sync skipped: %s))zhermes_cli.authsync_plugin_provider_registry)z hermes_cli.models_catalog_staticsync_plugin_provider_catalog)getattrsysmodulesget Exceptionloggerdebug)moduleattrsyncexcs r#_sync_auth_registryr?bsc s{{v.d; <  = F = LL. < < =sA A2A--A2c V^8dQhRRRR/#)r,profilerr-r.r)r/s"r#r0r0zs4r"c\P4pVeFWPVP&VPFpVPVPV&K M\V\ VP&\ ;'gR\VP&VPFpVP\V&K Rs \'d\'g \4R#R#R#)uMRegister 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. A registration made while a ``$HERMES_HOME`` plugin is being imported lands in that home's layer. Nruntime) r'r7rnamerr rr r r _discovered _discoveringr?)rAlayeraliass& r#register_providerrIzs ! $ $ &E '.w||$__E#*<.__annotate__sII#I0Ir"c<SPPV4;'g\PW4pSPPV4;'g\PV4#N)rr7r rr )rirOrGs& r#lookup$get_provider_profile..lookupsNMM%%a(>>HLL,> ~~!!),HH i0HHr"zcustom:Tforcecustom) agent.safe_worker_policyrgrE_discover_providers_bound_home_layer_refresh_home_layer isinstancerKlower startswithrb) rDrgrTkeycheckedrmrAis_custom_routerGs & @r#get_provider_profiler|s = ;(*E4!%3GIITlG !s+RR 0G0G 0ROw udt < <TlG?" :dC00 %d# 6 6X&G Nr"c$V^8dQhRRRRRR/#)r,providerrKmodelr-rWr)r/s"r#r0r0s&```C`D`r"c\T;'gR4P4P4p\V4pVeVPRJdR#^RIHpV!V4'gR#\T;'gR4P4PR4wrVpV'd V'gR#\VP4P44pVRJ;'dVPRJ#)aWhether an active route or its aggregator-targeted model rejects image tool parts. Routing aggregators such as ``openrouter`` send vendor-prefixed model IDs (for example, ``xiaomi/mimo-v2.5``), but their own profile cannot describe every routed provider's tool-message compatibility. Preserve the transport profile as the default and consult a registered target profile only for routing aggregators. Missing or unrecognized identities deliberately fail open. NFT)is_routing_aggregator/)rKstriprwr|supports_vision_tool_messageshermes_cli.providersr partition) r~r provider_namerAr target_name separator_target_profiles && r#)routed_model_rejects_vision_tool_messagesrsB'--/557M"=1GwDDM;  / / #EKKR 0 6 6 8 B B3 GKA K)+*;*;*=*C*C*EFN  % _ _.*V*VZ_*__r"cV^8dQhRR/#)r,r-zlist[ProviderProfile]r)r/s"r#r0r0s-r"cd^RIHpV!4'd.#\'g \4\ 4p\ fg\ 4p.p\P4F@p\V4V9gKVP\V44VPV4KB Vs\ Uu.uF!qUPVP9gKVNK# ppTPVPP4Uu/uFp\V4VbK upP44V#uupiuupi)zReturn all registered provider profiles (one per canonical name); the bound home's ``$HERMES_HOME`` plugins shadow process-wide profiles of the same name.rf)rrrgrErsrNrsetr valuesidaddappendrDrextend)rgrGseencacherApresults r#list_providersrs= ; ME#') '')G'{$&G% W%* %- N-Au~~1Maa-F N MMU^^%:%:%<=%<2a5!8%<=DDFG MO=s,D( D(<D-cV^8dQhRR/#)r,r-zset[str]r)r/s"r#r0r0sr"cB\4p\4F7pVP4'gVPVP4K7K9 V# \ dB\ PRTPRR7TPTP4Ki;i)anRegistered profiles that discovery surfaces (provider pickers, setup lists, the accounts tab) must not offer: pre-release ones the user has not opted into. Resolution never consults this: an unlisted profile still resolves, authenticates and serves turns by name. A raising ``listed()`` counts as unlisted, because a broken gate must never advertise a dark launch. z&provider %s listed() raised; hiding itT)exc_info)rrlistedrrDr8r9r:)hiddenrAs r#unlisted_provider_namesrsuF!# %>>## 7<<($$ M % LLA7< r"c^RIHpHpV!4pV!V4p\;_uu_4\ P V4pVf\4;p\ V&RRR4XW#3# \dRRr2LWi;i +'giL(;i))get_hermes_homehermes_home_keyNr)hermes_constantsrrr8_HOME_LAYERS_LOCKr$r7r)rrrTryrGs r#rtrt7s{E d#    % =(2 4EL%  $  "c  sA -A4 A10A14 B rpc ,V^8dQhRRRRRRRRR R/#) r,rGrrTrUryrKrprWr-r)r/s"r#r0r0Fs1z3RVcgr"cR\P!4pVe2V'g,VPeW@P, \8gR#\ V4pWPP 8wd:\ W4WPnW@n\'d\'g \4W@nR#)aLRe-stat the layer's plugin dirs when due (or *force*d); True when it stat'ed this call. Stamps are read before the scan: a plugin that lands mid-scan changes them and the next check picks it up. Checking on a short cadence keeps a newly installed plugin discoverable without making every model lookup perform two filesystem stats. FT) time monotonicr_PLUGIN_DIR_STAMP_TTL_SECONDS_plugin_dir_stampsr_scan_home_layerrErFr?)rGrTryrpnowrs&&&$ r#ruruFsz .. C |  ! ! ) '' '+H H  %F $ "% ;||  !  r"c V^8dQhRRRR/#)r,rTrr-rr)r/s"r#r0r0csRRTReRr"cXRRlpV!VR, 4V!VR, R, 43#)z[mtimes of ``plugins/`` and ``plugins/model-providers/``: they change when a child is added.cV^8dQhRR/#)r,pathrr)r/s"r#r0(_plugin_dir_stamps..__annotate__esDr"ch\P!V4P# \dR#i;irl)osr\ st_mtime_nsr])rs&r#stamp!_plugin_dir_stamps..stampes- 774=,, ,  s " 11r(r)r)rTrs& r#rrcs. $" #U4)+;>O+O%P QQr"cV^8dQhRR/#r,r-rUr)r/s"r#r0r0ms;r"c^RIHpV!4R, R, pVP4'dV#R# \dR#i;i)z>Return ``$HERMES_HOME/plugins/model-providers/`` if it exists.rr(r)Nrris_dirr8rds r#_user_plugins_dirrmsD4   ),= =HHJJq(D( s0777 AAcV^8dQhRR/#rr)r/s"r#r0r0xs   r"c^RIHpV!4R, pVP4'dV#R# \dR#i;i)uReturn ``$HERMES_HOME/plugins/`` if it exists. This is where ``hermes plugins install`` clones a plugin — flat, one directory per plugin, NOT under ``model-providers/``. See :func:`_discover_installed_provider_plugins`. rr(Nrrs r#_installed_plugins_dirrxs>4   )HHJJq(D( s)000 ??c V^8dQhRRRR/#)r, plugin_dirrr-rWr)r/s"r#r0r0s  d t r"cR EF"pW, pVP4'gK$VPRRR7p^RIHpT!T4p\ T\ 4'd/\TPRR44P4R8Hu#TP4FpTP4pTPR 4'gR T9dK3TPR 4wrp TP4R8XgK^T P4PR 4R8Huu# R# R# \dR#i;i \dLi;i) u[Whether ``plugin_dir``'s manifest declares ``kind: model-provider``. Only that kind is imported from the flat install directory — every other plugin there belongs to ``PluginManager``, which owns its lifecycle and consent flow. Parsed with ruamel.yaml when available, falling back to a line scan so provider discovery never hard-depends on it. utf-8replace)encodingerrorsF)fast_safe_loadkindrzmodel-provider#:z"')z plugin.yamlz plugin.yml) is_file read_textr8r[rrvrrKr7r splitlinesrxr) rfilenamemanifesttextrdatalinestrippedryrvalues & r#_declares_model_provider_kindrs42(!!  %%wy%ID  ,!$'D$%%488FB/0668$..s3MCEyy{f${{}**515EEE &/20 %     s#D,AD?, D<;D<? E  E c$V^8dQhRRRRRR/#)r,rGrryrKr-r.r)r/s"r#r0r0s!))J)S)T)r"c\PV4\r2Rs\4pVej\ VP 44FLpVP 4'gKVPPR4'dK>\VRVR7KN \4pVe\ VP 44FnpVP 4'd3VPPR4'gVPR8XdKM\V4'gK`\VRVR7Kp \PV4VsR# \PT4Tsi;i)aImport the bound home's not-yet-imported provider plugins into *layer*. ``$HERMES_HOME/plugins/model-providers//`` first, then plugins cloned flat by ``hermes plugins install`` into ``$HERMES_HOME/plugins//`` that declare ``kind: model-provider`` (PluginManager owns every other kind there). Per-home module names let two profiles carry the same plugin without aliasing each other's registrations. TNrM)home_keyr)r.) r'rrFrsortediterdirrrDrx_import_plugin_dirrrreset)rGrytokenprior_discoveringuser_dirchild installed_dirs&& r#rrs  477> L)$&   0 0 23<<>>%***?*? *K*K&ufsC4/0  $ 5 5 78||~~)>)>z)J)Jejj\mNm077&ufsC 9 ""5)(  ""5)( s=E EBEEE c$V^8dQhRRRRRR/#)r,rrrrKr-r)r/s"r#r0r0s&QQ$Q#Q#Qr"c\P!VPR44P4R,pRV RVPP RR4 2#)r:N N_hermes_user_provider_r-)hashlibsha1encode hexdigestrDr)rrdigests&& r#_user_module_namersL \\(//'2 3 = = ? DF #F81Z__-D-DS#-N,O PPr"rrc(V^8dQhRRRRRRRR/#)r,rrsourcerKrr-r.r)r/s"r#r0r0s)4444434PT4r"cVR, pVP4'gR#VR8wdF^RIHpHpV!4V8Xd2^RIHpVsV!V\W44Fp\V4K RsR#VR8Xd!RVPPRR 4 2p M \W4p V \P9dR#Vs\ P"P%W\'V4.R 7p V eV P(fRsR#\ P"P+V 4p V \PV &V P(P-V 4RsR# \d-p\PRTPT4Rp?ELRp?ii;i Rsi;i \dLp\PR YPT4\PP/T R4Rp?LRp?ii;i Rsi;i) zImport a single plugin directory so it self-registers. ``source`` is "bundled" or "user"; it is recorded per registered profile (``_SOURCES``). z __init__.pyNbundled)ISOLATION_HOSTisolation_mode)load_hosted_profilesz=Failed to load user provider plugin %s in the plugin host: %szplugins.model_providers.rr)submodule_search_locationsz(Failed to load %s provider plugin %s: %s)existshermes_cli.plugin_isolationrrhermes_cli.plugin_host_profilesrrrrIr8r9warningrDrr5r6 importlibutilspec_from_file_locationrKloadermodule_from_spec exec_modulepop) rrr init_filerrrrAr> module_namespecr;s &&$ r#rrs ]*I      N  ~ - L$O '3J@QR\@ghG%g. i #'  01H1Hc1R0ST ' = ckk!O~~55 J?P6  <4;;. 006#) K  'G 5^)55 5#'2 + 6QT   T** + s\$E :=Feprrefusalloadeds r#_discover_entry_point_providersr&sB( (R&((*  "E   3 ! !SZZeZ45ISWWUB/0I  77' !RWW%8 LLH"''  I+.RSUSZSZR],^_  NN4 )  WWYF F  "6** HGG  A7  ( #%(  E?FF G *GG  H!HH I!H<<IcV^8dQhRR/#)r,r-rWr)r/s"r#r0r0kstr"c^RIpVPV4pTPP 4F|pTP TPPTPPTPP39gKUTPTPPJgK{R# R# \\3dR#i;i)a>True when ``fn`` cannot be called with zero arguments. Used to distinguish provider registration hooks (zero-arg by contract) from general plugin hooks (``register(ctx)``) sharing the same entry-point group. Unintrospectable callables (C extensions) are treated as zero-arg and left to the per-entry exception guard. NFT) inspect signature TypeError ValueError parametersrr ParameterPOSITIONAL_ONLYPOSITIONAL_OR_KEYWORD KEYWORD_ONLYr&empty)fnr)r`params& r#rrks#&&( ::    - -    3 3    * *  mmw00666 )  z "sB33CCcV^8dQhRR/#r+r)r/s"r#r0r0sTr"c^RIHpV!4'dR#\'dR#RsRs\ 4Rs\ 4R# Rs\ 4i;i)aPopulate the process-wide registry by importing every provider plugin. Order: 1. Bundled plugins at ``/plugins/model-providers//`` 2. 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. ``$HERMES_HOME`` plugins are per profile home and load through :func:`_home_layer` at lookup time. rfNTF)rrrgrErF_run_discovery_stepsr?rfs r#rsrssN={KL    s AAcV^8dQhRR/#r+r)r/s"r#r0r0s+ + d+ r"cr\4\P4'dj\\P 44FHpVP4'd"VP P R4'dK<\VR4KJ ^RIp^RI pVPVP4F@wr4pVP R4'gVR8XdK&\P!RV 24KB R# \d"p\P!RYF4Rp?KmRp?ii;i \"dR#i;i)zLThe discovery passes, in precedence order (see :func:`_discover_providers`).rrNbasez providers.z.Failed to import legacy provider module %s: %sr)r&_BUNDLED_PLUGINS_DIRrrrrDrxrpkgutil providers iter_modules__path__r import_module ImportErrorr9rr8)rr<_pkg _importermodname_ispkgr>s r#r7r7s $%""$$088:;E<<>>UZZ%:%::%F%F ui 0<  *1*>*>t}}*M &I!!#&&'V*; ''*WI(>? +N  Dg     s=A D'C82D'8 D$DD'D$$D'' D65D6)F__conditional_annotations__r __future__rrrimportlib.utilloggingrr5 threadingr contextvarsr dataclassesrrpathlibrtypingrproviders.baser getLoggerrr9r r r r rrrErFrrr$Lockrr'__file__resolveparentr;r?rIrPrQrRobjectr^rbr|rrrrNrtrurrrrrrrr&rrsr7)rFs@r#rVs D#  "(*   8 $)+ %*..""5929  #  * *  * ') #(NN$ 7AA`jn6o3o N##**Y69JJ =00 #(24.3)++"H*&R`62&U Y^:R  F):Q 44ndN0:+ r"