߲jxdZddlmZddlmZd dZd dZ ddZ ddZddZ dd Z dd Z y )zFHelpers for reading the effective fallback provider chain from config.) annotations)Anycdt|tr|jjdSdS)N/) isinstancestrstriprstrip)values ?/home/ubuntu/.hermes/hermes-agent/hermes_cli/fallback_config.py_normalized_base_urlrs'(25#(>5;;=   $FBFcPt|tsyt|jdxsdj x}r|St|jdxs|jdxsdj x}r$ddlm}||xsdj xsdSy)aAPI key for one fallback entry: inline ``api_key``, else ``key_env``. Mirrors the custom-provider convention (``api_key_env`` accepted as alias); None when neither yields a value so ``resolve_runtime_provider`` falls through to standard credential resolution. ``key_env`` goes through ``agent.secret_scope.get_secret``, not raw ``os.getenv``: in a multiplexed gateway a bare env read ignores the active profile's scope and can return another profile's credential. Napi_keyrkey_env api_key_envr) get_secret)rdictr getr agent.secret_scoper)entryinlinerrs r resolve_entry_api_keyr s eT "UYYy)/R06688v8 eii *Leii .FL"MSSUUwU17#)r002:d: rcH|xsi}t|jdxsdj}|jdk7r|St|jdxs|xsijdxsdj}|r|jdk7r|S|S)u8Provider identity to persist/display for a resolved fallback entry. ``resolve_runtime_provider`` returns the bare billing class ``"custom"`` for every named ``providers:`` / ``custom_providers:`` entry; the entry's configured id only survives in ``requested_provider``. Fallback resolvers that persist ``runtime["provider"]`` as the agent identity therefore label sessions/billing rows ``custom`` instead of the configured provider name — while the manual ``/model`` switch path correctly persists the named id (#98739). Same class as the delegation fix in ``tools/delegate_tool.py``. Returns the entry's requested identity when the resolved provider is the bare ``custom`` class; a genuinely ad-hoc endpoint (requested provider IS ``custom``) keeps the bare class unchanged. providerrcustomrequested_provider)r rr lower)rruntimeresolved requesteds r effective_runtime_providerr#s"mG7;;z*0b1779H~~8# ()  KR  Z (   eg  Y__&(2 Orcdjd||fDxsd}djd||fDxsd}d|d|dS) aUser-visible one-shot line for a provider switch made during credential resolution, before any AIAgent exists (#74349). Shared by the messaging gateway, the TUI/Desktop gateway and cron so the three pre-agent fallback paths cannot drift in wording.rc3TK|] }|st|j"ywNr r .0ps r z,pre_agent_fallback_notice..DsYZCFLLN[((primaryc3TK|] }|st|j"ywr&r'r(s r r+z,pre_agent_fallback_notice..Es^\]SV\\^^r,fallbacku⚠️ Provider fallback: z unavailable; using z for this response.)join)primary_provider primary_modelfallback_providerfallback_model primary_desc fallback_descs r pre_agent_fallback_noticer7>s[ 88}4U[[h_hLHH^6G5X^^lblM ' ~5I-Xk llrct|tr|gnt|tr|ng}g}|D]}t|tst|j dxsdj }t|j dxsdj }|r|sqi|||d}t |j d}|r||d<|j||S)Nrrmodel)rr9base_url)rrlistr rr rappend)raw candidatesentriesrrr9 normalizedr:s r _iter_fallback_entriesrAJs$S$/#JsD %-Jz "z" # Nrc8t|jdxsdjjt|jdxsdjjt |jdjfS)Nrrr9r:)r rr rr)rs r _entry_identityrC\sv EIIj ! 'R(..0668 EIIg  $"%++-335UYYz2399; rc|xsi}g}t}dD]S}t|j|D]4}t|}||vs|j ||j |6U|S)anReturn the effective fallback chain merged across old and new config keys. ``fallback_providers`` remains the primary source of truth and keeps its order. Legacy ``fallback_model`` entries are appended afterwards unless they target the same provider/model/base_url route as an earlier entry. The returned list always contains fresh dict copies. )fallback_providersr4)setrArrCaddr<)configchainseenkeyridentitys r get_fallback_chainrMdsu\rF"$E&)eD7$+FJJsO< $E&u-Ht#" U#  $$ LrN)r rreturnr )rdict[str, Any] | NonerNz str | None)rrOr rOrNr ) r1rr2rr3rr4rrNr )r=rrNlist[dict[str, Any]])rzdict[str, Any]rNztuple[str, str, str])rHrOrNrP) __doc__ __future__rtypingrrrr#r7rArCrMrr rUsxL"G& +@>mm*-mBEmWZmm$r