`gj& @dZddlmZddlmZmZdZd dZd dZd dZ y) uHACP auth helpers — detect and advertise Hermes authentication methods.) annotations)AnyOptionalz hermes-setupc ddlm}|}|jd}|jd}t|tr|j syt|txr|j }t |xrt|t }|s|r|j jS y#t$rYywxYw)uResolve the active Hermes runtime provider, or None if unavailable. Treats a ``Callable`` ``api_key`` (Azure Foundry Entra ID bearer token provider — see :mod:`agent.azure_identity_adapter`) as a valid credential. Without this, ACP sessions for Entra-configured Foundry deployments silently default to ``"openrouter"`` and the ACP auth handshake rejects the legitimate provider. r)resolve_runtime_providerapi_keyproviderN) hermes_cli.runtime_providerrget isinstancestrstripcallablelower Exception)rruntimerr is_string_keyis_callable_providers C/root/.hermes/venv/lib/python3.12/site-packages/acp_adapter/auth.pydetect_providerr s H*,++i(;;z*(C(0@"7C0DW]]_ '0QGS9Q5Q 0>>#))+ +1  sAB6A!B66 CCctduS)zCReturn True if Hermes can resolve any runtime provider credentials.N)rr has_providerr$s  D ((rc ddlm}m}g}t}|r!|j |||dd|d|j |t ddd d g |S) aReturn registry-compatible ACP auth methods for Hermes. The official ACP registry validates that agents advertise at least one usable auth method during the initial handshake. A fresh Zed install may not have Hermes provider credentials configured yet, so Hermes always advertises a terminal setup method. When credentials are already present, it also advertises the resolved provider as the default agent-managed runtime credential method. r)AuthMethodAgentTerminalAuthMethodz runtime credentialsz3Authenticate Hermes using the currently configured z runtime credentials.)idname descriptionzConfigure Hermes providerz~Open Hermes' interactive model/provider setup in a terminal. Use this when Hermes has not been configured on this machine yet.terminalz--setup)rrr typeargs) acp.schemarrrappendTERMINAL_SETUP_AUTH_METHOD_ID)rrmethodsr s rbuild_auth_methodsr()s|?G H  z!56Ij 57    NN,,T   NrN)returnz Optional[str])r)bool)r)z list[Any]) __doc__ __future__rtypingrrr&rrr(rrrr.s%N" !/2) &r