+ jHj7a0t$Rt^RIHt^RIt^RIt^RIHtHt^RI H t ^RI H t H t HtHt^RIHt]P$!4t]!4tR]R&/tR ]R &RsR ]R &RsR ]R&RRltRRltRRltRRltRRltRRltRRlt RR/RR llt!R!t"]R"R#l4t#R$R%lt$R&R'lt%R(R)lt&R7RR/R*R+lllt'R,R-lt(R.R/lt)R7R0R1llt*R2RRRR3R4/R5R6llt+R#)8z9Shared CLI/TUI-safe helpers for background MCP discovery.) annotationsN)contextmanager nullcontext) copy_context)DictIteratorOptionalSet)hermes_home_keyzset[str]_mcp_discovery_startedzdict[str, threading.Thread]_mcp_discovery_threadzOptional[threading.Timer]_mcp_discovery_deferredOptional[list[str]]_mcp_server_filterc V^8dQhRRRR/#)toolsetsobjectreturnr)formats";/home/ubuntu/.hermes/hermes-agent/hermes_cli/mcp_startup.py __annotate__rsF/Bc.p\V\4'dGVPR4Uu.uF*q"P4'gKVP4NK, ppMZ\V\\ \ 34'd:VF3pVPR\V4PR444K5 V'dRV9gRV9d Rs\#Vs\#uupi)a Derive the MCP spawn allowlist from a ``-t/--toolsets`` value. Built-in toolset names in the list are harmless (they never match a configured ``mcp_servers`` key). ``all``/``*`` or an empty/absent value clears the filter. Returns the stored list for logging/tests. ,c3p"TF,qP4'gKVP4xK. R#5iN)strip).0ts& r (set_mcp_server_filter..*s"N,@qGGI,@s66all*N) isinstancestrsplitrlisttuplesetextendr)rnamesr items& rset_mcp_server_filterr.sE(C  $,NN3$7E$7q779$7E HtUC0 1 1D LLNCIOOC,@N N EUNcUl! # Fs CCcV^8dQhRR/#)rrrr)rs"rrr2s2rc\#r)rrrrget_mcp_server_filterr12s rcV^8dQhRR/#rrboolr)rs"rrr6s  T rc^RIHpV!4;'g/p\VPR4\4'dVR,'dR#^RIHpV!V4# \dR#i;i)zBCheap config probe so non-MCP users avoid importing the MCP stack.)read_raw_config mcp_serversT)has_enabled_agent_plugin_mcp)hermes_cli.configr6r%getdicthermes_cli.agent_pluginsr8 Exception)r6 raw_configr8s r_has_configured_mcp_serversr?6s] 5$&,," jnn]3T : :z-?X?XI+J77 sA6A A A,+A,cV^8dQhRR/#r3r)rs"rrrEsddTdrc\;QJd&RT;'g.4F 'gK R# R#!RT;'g.44#)atTrue when a discovery run left servers usable: a live session OR a lazy registration. A ``lazy: true`` server never connects until first use, so an all-lazy config (the memory-saving setup the feature exists for) looked like a run that achieved nothing: the zero-connected warning fired on every startup and the retry path re-ran discovery on every later call (#111717). c3z"TF1qPR4;'gVPR4R8HxK3 R#5i) connectedstatuslazyN)r:)rentrys& rr!0_discovery_registered_servers..Ms2cUa5yy%FF8)<)FFUas;;TF)any)rDs&r_discovery_registered_serversrIEsG 3cU[UaUa_aUac33c3c3cU[UaUa_aUac ccrcV^8dQhRR/#r3r)rs"rrrPsAADArcB^RIHp\V!4;'g.4#)get_mcp_status)tools.mcp_tool_discoveryrNrIrMs r_any_mcp_connectedrPPs7 ()9)?)?R @@rcV^8dQhRR/#)rrz list[str]r)rs"rrrVsff9frcv^RIHpV!4p\fV#VUu.uFq"\9gKVNK up#uupi)rL)mcp_servers_awaiting_connect)rOrSr)rSpendingns r_servers_awaiting_connectrVVs7E*,G(07e'6e'QRdMdqq'6ee6es 66c V^8dQhRRRR/#)r thread_namer&rNoner)rs"rrr]s::3:4:rc raa\4o\;_uu_4S\9d\P S4pVe"VP 4'd RRR4R#\ 4pV'd \4M.pT'dT'g RRR4R#T'd#SPRRPT44MSPR4\PS4\PSR4\PS4\4'g RRR4R#RVV3Rllp\ P"!\%4P&V3VRR7pV\S&VP)4RRR4R# \d RRR4R#i;i +'giR#;i) aSpawn one background MCP discovery thread per profile home. If the first run exits without connecting any server (e.g. startup cancellation / OOM restart), later calls may retry instead of pinning the profile in "already started" with zero MCP tools. Likewise a server added to ``mcp_servers`` after that run (``hermes mcp add`` against a running Desktop backend) is connected by the next call, which every agent build makes, so a new session gets its tools without a reload (#76954). Discovery is additive: live servers are untouched. Nz5MCP server(s) %s not connected yet; running discoveryz, z_Background MCP discovery previously exited with no connected servers; retrying discovery threadcV^8dQhRR/#rrrYr)rs"rr4start_background_mcp_discovery..__annotate__s > >4 >rc <\4\4'gSPR4\ ;_uu_4\ PSR4RRR4R# \dSP RRR7LOi;i \dSP RRR7Lsi;i +'giR#;i \ ;_uu_4\ PSR4RRR4i +'gii;i;i)z>Background MCP discovery completed with zero connected serversz7Failed to inspect MCP status after background discoveryTexc_infoz$Background MCP tool discovery failedN)-_discover_mcp_tools_without_interactive_oauthrPwarningr=debug_mcp_discovery_lockr pop)home_keyloggersr _discover1start_background_mcp_discovery.._discovers >=?k-//'gh )()--h=)( !kLL!ZeiLjk T Cd S T)(((()--h=)(((si B!AB&A?<B=B:>A??BB# B:"B##B:& B7 :C< C) C<) C9 4C<T)targetargsnamedaemon)r rdr r r:is_aliverPrVr=infojoinrbdiscardreaddr? threadingThreadrrunstart)rgrXthreadrCrTrhrfsd$ @rstart_background_mcp_discoveryrx]s] H   - -*..x8F!foo&7&7    .0 9B35   SUYU^U^_fUgh9 # * *8 4 ! % %h 5""8,*,, 1  @ > >!!););9,U`imn*0h' a         sU:F%F%"F F%F%F%F%#BF%1AF% F"F%!F""F%% F6 single_queryFc$V^8dQhRRRRRR/#)rexplicit float | Noneryr4rfloatr)rs"rrrs"Y^rc:VeV#V'dRMRpV'dRMRp^RIHpHp\VP W#44p\T!4;'g/P Y&44pT^8dT#T# \ dTu#i;i \ dTu#i;i)zResolve the MCP discovery wait bound: explicit arg > config.yaml > ``DEFAULT_CONFIG``. Lazy and fail-safe: a missing/invalid value or broken config falls back to a short bound so startup can never hang or crash. "mcp_single_query_discovery_timeoutmcp_discovery_timeoutg.@g?) load_configDEFAULT_CONFIG)r9rrr}r:r=)r{rykeyfallbackrrdefaultvals&$ r_resolve_discovery_timeoutrs 2> .D[C#tHA**39:[]((b--c;<Ags*7*  s/"A7B B 5B 7 BB BBgMb@?cV^8dQhRR/#)rrzIterator[None]r)rs"rrrs$$~$rc#"\P!4p\P!\4Rx\P!V4R# \P!T4i;i5i)zTemporarily lower the interpreter switch interval so discovery's CPU work can't monopolize the GIL against concurrent threads (see _DISCOVERY_SWITCH_INTERVAL_S).N)sysgetswitchintervalsetswitchinterval_DISCOVERY_SWITCH_INTERVAL_S)prevs r_discovery_gil_budgetrsH  "D67$  d#d#s0A*AA*A''A*cV^8dQhRR/#r\r)rs"rrrsEEtErc <^RIHp\ 4;_uu_4V!4;_uu_4^RIHp\f V!4M V!\R7RRR4RRR4R# \d \pLki;i +'giL1;i +'giR#;i)zCRun MCP discovery without letting OAuth read from the user's stdin.)suppress_interactive_oauth)discover_mcp_toolsN)allowed_mcp_names)tools.mcp_oauthrr=rrrOrr)rrs rrarasm1>  "<">">?  %  1C D#?  1%0"1#?"> s3A B $A7 B  A43A47 B B  B c$V^8dQhRRRRRR/#)rrXr&delayr|rrYr)rs"rrrs"3|X\rcHaa\;_uu_4\4\9g \e RRR4R#RVV3Rllp\P !Vf^MTV4pRVnS R2VnVsVeVP4RRR4R# +'giR#;i)ahArm ``start_background_mcp_discovery`` to run ``delay`` seconds from now. Used by the Desktop ``serve`` backend after its socket is announced: the thread's first act is the ~350ms ``mcp`` SDK import, which would hold the GIL against the renderer's connect + first hydration reads (or the web_server import) if started earlier. ``delay=None`` arms without a clock: the standalone dashboard fires it from the first ``/api/ws`` client (``start_deferred_mcp_discovery_now``) or the first agent build (``wait_for_mcp_discovery``), so an idle, unvisited dashboard never spawns the configured stdio MCP servers (#58733). NcV^8dQhRR/#r\r)rs"rr4defer_background_mcp_discovery..__annotate__s S St Srcz<\;_uu_4RsRRR4\SSR7R# +'giL;i)NrgrX)rdr rxrsr_fire-defer_background_mcp_discovery.._fires'$$*.'% *&k R%$s* : Tz -deferred) rdr r r rsTimerrmrlrv)rgrXrrtimersdd$ rdefer_background_mcp_discoveryrs     6 6:Q:]    S SU]uE #}I. "'   KKM#    sBAB B! cV^8dQhRR/#r\r)rs"rrrs$rc\;_uu_4\RupsRRR4XfR#VP4VP4R# +'giL8;i)zBRun an armed deferred start immediately (idempotent, thread-safe).N)rdr cancelfunction)rs r start_deferred_mcp_discovery_nowrs@  )@$&&  } LLN NN  s A  A c$V^8dQhRRRRRR/#)rtimeoutr|ryr4rrYr)rs"rrrs' X XL X$ X[_ Xrc\4\4pVeVP4'gR#VP\ WR7R7R#)a>Wait for background MCP discovery before the first tool snapshot. ``join`` returns the instant discovery completes, so this only blocks for a still-pending server's real connect time. ``single_query`` uses ``mcp_single_query_discovery_timeout`` (15s vs 1.5s) because one-shot sessions have no second turn to recover. N)ryr)r_current_home_threadrnrpr)rryrws&$ rwait_for_mcp_discoveryrs:%& ! #F ~V__.. KK27VKWrcV^8dQhRR/#)rrzOptional[threading.Thread]r)rs"rrrs8888rc<\P\44#)zFDiscovery thread for the profile home the caller is scoped to, if any.)r r:r rrrrrs $ $_%6 77rcV^8dQhRR/#r3r)rs"rrrs 4 4 4rcN\4pVRJ;'dVP4#)aTrue if THIS module's discovery thread (for the current profile home) is still running. Mirrors ``tui_gateway.entry.mcp_discovery_in_flight``; surfaces that start discovery here (desktop, dashboard sidecar) populate this thread, so the late-refresh scheduler consults both. 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)rrn)rws rmcp_discovery_in_flightrs&" #F   3 3&//"33rc V^8dQhRRRR/#)rrr|rr4r)rs"rrr%s!! !!rcp\4pVfR#VPVR7VP4'*#)zBlock up to ``timeout`` for THIS module's discovery; True once complete, False if still running. For the off-critical-path late-refresh waiter (accepts a long wait, reports outcome).Tr)rrprn)rrws& rjoin_mcp_discoveryr%s2" #F ~ KKK   rrrXzcli-mcp-discoveryc(V^8dQhRRRRRRRR/#) rrr|ryr4rXr&rrYr)rs"rrr/s:___ _  _ 04 _rc\WR7\WR7R# \dTPRRR7R#i;i)uEGive configured MCP tools a bounded chance to register before AIAgent. Non-interactive first turns (``chat -q``, ``hermes -z``) can construct ``AIAgent`` before any path started discovery, and ``wait_for_mcp_discovery()`` only joins an existing thread — so start discovery if needed, then wait up to the configured bound. r)rryz7MCP discovery readiness check failed before agent buildTr_N)rxrr=rc)rgrryrXs$$$$r'ensure_mcp_discovery_before_agent_buildr/s;_&fNwJ _ NY] ^_s >>r),__conditional_annotations____doc__ __future__rrrs contextlibrr contextvarsrtypingrrrr hermes_constantsr Lockrdr*r __annotations__r r rr.r1r?rIrPrVrxrrrrarrrrrrr)rs@rrs?" 2$00,nn& $'5(57275929 +/'.* dA f:zu: &$$E&@ XQV X X8 4!_!_ _ + __r