yjy)UdZddlmZddlZddlmZddlmZejZ da da de d<dd Z ddZddd dZd!dZ d"ddd#dZddZd"d$dZddddd%dZdS)&z9Shared CLI/TUI-safe helpers for background MCP discovery.) annotationsN) nullcontext)OptionalFzOptional[threading.Thread]_mcp_discovery_threadreturnboolc ddlm}|pi}|d}t|trt |dkrdSddlm}||S#t$rYdSwxYw)zBCheap config probe so non-MCP users avoid importing the MCP stack.r)read_raw_config mcp_serversT)has_enabled_agent_plugin_mcp) hermes_cli.configr get isinstancedictlenhermes_cli.agent_pluginsr Exception)r raw_configr r s z1start_background_mcp_discovery..3s.BB%uyy--BBBBBBz_Background MCP discovery previously exited with no connected servers; retrying discovery threadFT)get_hermes_home_overriderrcd} ddlm}|}n#t$rd}YnwxYw t ddlm}|pg}t d|Dsdn'#t$rddYnwxYwn'#t$rd dYnwxYw|# dd lm }||n#t$rYnwxYwt5da ddddS#1swxYwYdS#|# dd lm }||n#t$rYnwxYwt5da dddw#1swxYwYwxYw) Nr)set_hermes_home_overriderc3@K|]}|dVdSrr r!s rr$zDstart_background_mcp_discovery.._discover..]s.JJ%uyy55JJJJJJr%z>Background MCP discovery completed with zero connected serversz7Failed to inspect MCP status after background discoveryTexc_infoz$Background MCP tool discovery failed)reset_hermes_home_override) hermes_constantsr(r-_discover_mcp_tools_without_interactive_oauthtools.mcp_toolranywarningdebugr,_mcp_discovery_lockr)tokenr(rstatusr, home_overrideloggers r _discoverz1start_background_mcp_discovery.._discoverPsE EEEEEE00??     1=???k======+^--3FJJ6JJJJJ\!kkkLL!ZeiLjjjjjk T T T Cd SSSSS T$OOOOOO2259999$(11,0)111111111111111111$OOOOOO2259999$(11,0)1111111111111111s &&B"AA:9B":!BB"BB"!D"!CDCD C C+*C+5DD  D ED('E( D52E4D55 E?E EE EE E)targetnamedaemonrr)r3_mcp_discovery_startedris_aliver/rr0rr1rr-r& threadingThreadstart)r7rthreadrr5r&r8r6s` @rstart_background_mcp_discoveryrC s MM ! )*F!foo&7&7! MMMMMMMM  999999'))/RBB6BBBBBMMMMMMMM   MMMMMMMM  NN5   &+ "$( !!%*,,  -MMMMMMMM> ! A A A A A A4466MM ! ! ! MMM ! 1 1 1 1 1 1 1B!    !' [MMMMMMMMMMMMMMMMMMsX&D0+A87D08 BD0B-D0 CD0 C,)D0+C,,7D00D47D4 single_queryexplicit'float | None'rEfloatc6||S|rdnd}|rdnd} ddlm}m}t|||} |pi||}t|}|dkr|n|S#t $r|cYSwxYw#t $r|cYSwxYw)uResolve the MCP discovery wait bound: explicit arg > config > default. Reads ``mcp_discovery_timeout`` from config.yaml, defaulting to the value in ``DEFAULT_CONFIG`` (single source of truth) when the key is absent. Kept lazy and fail-safe — a missing/invalid value or a broken config falls back to a short safe bound so startup can never hang or crash. When ``single_query`` is True (``hermes -z "..."`` / ``-q``), the larger ``mcp_single_query_discovery_timeout`` bound is used instead. In single-query mode there is only ONE turn, so the between-turns late-binding refresh never runs — a server that misses the small interactive bound would be invisible to the LLM for the whole session. The wait still returns the instant discovery completes (see ``wait_for_mcp_discovery``), so fast servers pay ~0s; the larger bound only caps how long a genuinely slow cold-start may block. N"mcp_single_query_discovery_timeoutmcp_discovery_timeoutg.@g?r) load_configDEFAULT_CONFIG)r rLrMrHrr) rFrEkeyfallbackrLrMdefaultrawvals r_resolve_discovery_timeoutrSzs$  %,, $ $,ttH AAAAAAAA**399:: ;==&B++C99C**C''33w .   NNN  s.+B 8A77 BB BB BBc ddlm}n#t$r t}YnwxYw|5ddlm}|ddddS#1swxYwYdS)zCRun MCP discovery without letting OAuth read from the user's stdin.r)suppress_interactive_oauth)discover_mcp_toolsN)tools.mcp_oauthrUrrr/rV)rUrVs rr.r.s1>>>>>>> 111%0"""1 $ # % %555555s AA A timeoutct}||sdS|t||dS)uWait for background MCP discovery before the first tool snapshot. ``thread.join(timeout)`` returns the INSTANT discovery completes, so this only ever blocks for the real connect time of a still-pending server — users with no MCP servers or fast servers pay ~0s. The bound (from ``mcp_discovery_timeout`` in config) just caps the wait so a dead server can't freeze startup; servers that miss it are picked up by the automatic late-binding refresh. When ``single_query`` is True, the bound comes from ``mcp_single_query_discovery_timeout`` instead (default 15s vs 1.5s interactive) because one-shot sessions have no second turn to recover. NrDrX)rr>joinrS)rXrErBs rwait_for_mcp_discoveryr\sI #F ~V__..~ KK27VVVKWWWWWr%c@t}|duo|S)a5Return True if THIS module's background discovery thread is still running. Mirrors ``tui_gateway.entry.mcp_discovery_in_flight`` for the surfaces that start discovery through ``start_background_mcp_discovery`` here (the desktop app + dashboard WebSocket sidecar via ``tui_gateway/ws.py``, and ``hermes dashboard``). Those processes populate THIS module's ``_mcp_discovery_thread``, not ``tui_gateway.entry``'s, so the late-refresh scheduler must consult both to decide whether a slow server's tools are still pending (see #51587). N)rr>)rBs rmcp_discovery_in_flightr^s##F   3&//"3"33r%cnt}|dS||| S)alBlock until THIS module's background discovery finishes, up to ``timeout``. Returns True if discovery has completed (thread absent or no longer alive), False if it is still running after the timeout. Unlike ``wait_for_mcp_discovery`` this accepts an unbounded/long wait and reports the outcome, for the off-critical-path late-refresh waiter. NTrZ)rr[r>)rXrBs rjoin_mcp_discoveryr`s:#F ~t KKK      r%zcli-mcp-discovery)rXrErc t||t||dS#t$r|ddYdSwxYw)uLGive configured MCP tools a bounded chance to register before AIAgent. Non-interactive first turns (``chat -q``, ``hermes -z``) can construct ``AIAgent`` before the normal banner or tool-list paths touch ``get_tool_definitions()``. Because the agent snapshots its tool registry at construction time, the first and only model turn can miss native ``mcp__...`` tools even when the MCP server is healthy. ``wait_for_mcp_discovery()`` only joins an already-created discovery thread, so it no-ops if a direct/single-query path reaches agent construction before MCP startup created that thread. This helper makes the construction site self-sufficient: start discovery if needed, then wait up to the configured bound. When ``single_query`` is True, the larger ``mcp_single_query_discovery_timeout`` bound is used (default 15s vs 1.5s interactive) because one-shot sessions have no second turn to recover. Failures are swallowed so a broken MCP config never aborts agent construction — the agent runs without MCP tools, same as before. )r7r)rXrEz7MCP discovery readiness check failed before agent buildTr*N)rCr\rr2)r7rXrErs r'ensure_mcp_discovery_before_agent_buildrbs8  &#     w\JJJJJJ     E        s"&!A  A )rr)rrrr)rFrGrErrrHr<)N)rXrGrErrr)rXrGrr)rXrGrErrrrr)__doc__ __future__rr? contextlibrtypingrLockr3r=r__annotations__rrCrSr.r\r^r`rbr%rrjso???""""""""""""$in&&488888$WWWWv7<%%%%%%P    #X