+ iHjBRt^RIHt^RIHtHtHt^RIHtRRlt R#)u2Managed llama.cpp endpoint for auxiliary and fallback client resolution. A bare ``llamacpp`` / ``llama.cpp`` / ``llama-cpp`` alias (no base_url, no configured provider of that name) means "the local server Hermes manages for this profile" — exactly what the main ladder resolves in ``hermes_cli.runtime_provider_custom._resolve_llamacpp_runtime``. With no server running the answer is "unavailable", never the generic custom/API-key discovery: that handed the local model slug to whatever cloud provider held a key (#119227) or to the primary's own endpoint. ) annotations)AnyOptionalTuple)LLAMACPP_ALIASESc(V^8dQhRRRRRRRR/#)providerz Optional[str]base_urlapi_keyrreturnzOptional[tuple[str, Any]])formats"B/home/ubuntu/.hermes/hermes-agent/agent/auxiliary_local_runtime.py __annotate__rs0EE]EmE$'E,EEcT;'gRP4P4pV\9g V'dR#^RIHp^RIHp^RIHpV!V4'dR#V!V!4R7;'g/p\VPR4;'gR4P4T;'gVPR4;'gR 3#) aU``(base_url, api_key)`` of the profile's local llama.cpp server for a bare alias. ``base_url`` is ``""`` when nothing is serving. ``None`` when the request is not a bare alias: an explicit base_url or a configured provider entry under the alias name resolves as before. Read on every call so a restarted server's new port/key is picked up. N) load_config)resolve_llamacpp_endpoint)_get_named_custom_provider)configr r zno-key-required) striplowerrhermes_cli.configr!hermes_cli.local_runtime.endpointrhermes_cli.runtime_providerrstrget)r r r aliasrrrendpoints&&& rbare_llamacpp_endpointr!s^^ " " $ * * ,E $$-KF!%((( >DD"H  Z(..B / 5 5 7  C Cx||I. C C2C EErN) __doc__ __future__rtypingrrrrrr!r rrr%s#''>Er