+ jHja0t$Rt^RIHt^RIHtHtHtRRRRRRR R /3R R R RRR/3RRRRRR/3RRRRRR/3RRRR R!R"R#R$R%R&/3R'R(R)R*R+R,R#R-R.R/R0R1/3R2R3R4R5R6R7R#R$/3R8R9R:R;RR?R@RARBRCR#R$/33 tRD] RE&RFRGR$RHR-R-/t RI] RJ&R-#)KaThe ``register__provider`` table behind :class:`hermes_cli.plugins.PluginContext`. Every ``register__provider`` shares one body (:meth:`PluginContext._register_scoped_provider`): type-check, register in the scope-keyed process-global registry, lease the slot so unload restores the displaced entry. ``hermes_cli.plugins`` generates one ctx method per row. Rows: (method, kind, registry module, base-class module:attr, label, docstring, options). ``normalize``: ``strip`` (default), ``lower`` (strip+lowercase) or ``None`` (raw name). Object-taking rows also need a ``plugin_isolation.HOST_OBJECT_BASES`` entry so the provider works under ``plugins.isolation: host``. ) annotations)AnyCallableOptionalregister_image_gen_providerimage_gen_providerzagent.image_gen_registryz)agent.image_gen_provider:ImageGenProviderzimage_gen providerzwRegister an :class:`agent.image_gen_provider.ImageGenProvider`; ``provider.name`` is matched by ``image_gen.provider``.articleanregister_video_gen_providervideo_gen_providerzagent.video_gen_registryz)agent.video_gen_provider:VideoGenProviderzvideo_gen providerzwRegister an :class:`agent.video_gen_provider.VideoGenProvider`; ``provider.name`` is matched by ``video_gen.provider``.register_web_search_providerweb_search_providerzagent.web_search_registryz+agent.web_search_provider:WebSearchProviderz web providerzRegister an :class:`agent.web_search_provider.WebSearchProvider`; ``provider.name`` is matched by ``web.search_backend`` / ``web.extract_backend`` / ``web.backend``.register_browser_providerbrowser_providerzagent.browser_registryz&agent.browser_provider:BrowserProviderzbrowser providerzRegister an :class:`agent.browser_provider.BrowserProvider`; ``provider.name`` is matched by ``browser.cloud_provider`` (consulted by ``tools.browser_tool_cloud._get_cloud_provider``).®ister_terminal_environment_providerterminal_environment_providerzagent.terminal_env_registryz7agent.terminal_env_provider:TerminalEnvironmentProviderzterminal environment provideru%Register a :class:`agent.terminal_env_provider.TerminalEnvironmentProvider`; ``provider.name`` is matched by ``terminal.backend`` when no built-in backend has that name. Built-in names (local, docker, modal, daytona, vercel_sandbox, ssh) are rejected — plugins never shadow in-tree backends. normalizelowerreject_messagez6Plugin '%s' terminal environment provider rejected: %sregister_secret_source secret_sourcezagent.secret_sources.registryz&agent.secret_sources.base:SecretSourcez secret sourceakRegister a :class:`agent.secret_sources.base.SecretSource`, run by ``load_hermes_dotenv()`` (after ``~/.hermes/.env``, before credentials are read) when ``secrets.`` is enabled. The orchestrator owns ordering/precedence/provenance; the source only fetches. Since dotenv usually loads before discovery, the manager re-pulls enabled plugin sources afterwards.Nregisterregister_sourceparamsourceregister_tts_provider tts_providerzagent.tts_registryzagent.tts_provider:TTSProviderz TTS providerzRegister an :class:`agent.tts_provider.TTSProvider`; ``provider.name`` is matched by ``tts.provider`` unless it is a built-in name (rejected with a warning) or a ``tts.providers.: type: command`` entry shares it (command-providers win).register_transcription_providertranscription_providerzagent.transcription_registryz2agent.transcription_provider:TranscriptionProviderztranscription providerzRegister an :class:`agent.transcription_provider.TranscriptionProvider`; ``provider.name`` is matched by ``stt.provider`` unless it is a built-in name (rejected) or a ``stt.providers.: type: command`` entry shares it (command-providers win).register_delegation_providerdelegation_providerzagent.delegation_registryz,agent.delegation_provider:DelegationProviderzdelegation provideraRegister an :class:`agent.delegation_provider.DelegationProvider`; ``provider.name`` is matched by ``delegation.backend``. It decides each ``delegate_task`` task's route (model/provider or a Hermes profile) and may add per-task schema parameters; core keeps the subagent lifecycle.z?tuple[tuple[str, str, str, str, str, str, dict[str, Any]], ...]_SCOPED_PROVIDER_REGISTRARSstripc"VP4#N)r"ns&B/home/ubuntu/.hermes/hermes-agent/hermes_cli/plugins_registrars.pyr(Es qwwyc>VP4P4#r$)r"rr%s&r'r(r(EsQWWY__5Fr)z3dict[Optional[str], Optional[Callable[[str], str]]]_NAME_NORMALIZERS) __conditional_annotations____doc__ __future__rtypingrrrr!__annotations__r+)r,s@r'r1s#**#$8:T02F?AJD@QS#$8:T02F?@BD$%: