+ jHj>a0t$Rt^RIHt^RIt^RIt^RIt^RIHt^RI H t H t ]P!] 4t]!4tR]R&]!0R3m4tRtR4tRR ltR R ltR R ltRRltRRltRRltRRltRRltRR/RRlltRRltRRlt RR lt!R!]"/R"R#llt#R$R%lt$R&R'lt%R(R)lt&R*R/R+R,llt'R-R.lt(R!]"/R/R0llt)R!R/R1R2llt*R#)5uDMove a user from a memory provider that left core onto its catalog plugin. A bundled ``plugins/memory/`` that becomes a standalone catalog plugin keeps the same provider name, the settings it already read, its data directory and tool names, so the migration is only "the code now lives under ``HERMES_HOME/plugins/``". Two hooks call :func:`migrate_home`: * ``hermes update`` — for every profile home that shares the venv (primary; runs where the venv was just rebuilt anyway). * agent init — when the configured provider cannot be found at all, once per process (Desktop users update through the app and never run ``hermes update`` by hand). After a failed attempt, starts skip it for :data:`STARTUP_RETRY_SECONDS`, doubling with each further failure up to :data:`STARTUP_RETRY_MAX_SECONDS` (``hermes update`` always retries): every ``hermes chat``, cron run and Desktop restart otherwise paid the network round trip again and showed the same failure. Both install the catalog entry at its reviewed pin through the normal plugin install path (kill list, dependency constraints, enable), never a custom source. Every outcome — installed, refused, failed, absent from the catalog — reaches the user (terminal, Desktop, chat platform), never only ``agent.log``: a provider that silently stays missing is lost memory. ) annotationsN)Path)CallableOptionalzset[tuple[str, str]] _attemptedg @c$V^8dQhRRRRRR/#)homerpluginstrreturn)formats"I/home/ubuntu/.hermes/hermes-agent/hermes_cli/memory_provider_migration.py __annotate__r-s!999s9t9c*VR, RV R2, #)zeWritten on every failed automatic install: its mtime and failure count gate the next startup attempt.cachez left-core-z.failedr r r s&&r_failure_stampr-s '>j8 88rc V^8dQhRRRR/#)rstamprr intr )rs"rrr2s..$.3.rcVPRR7P4pTP4'd \ T4#^# \d^#i;i)z^Consecutive failures recorded in *stamp*; the empty stamp an older Hermes touched counts once.z utf-8-sigencoding) read_textstripOSErrorisdigitr)rtexts& r_failure_countr!2sO 4::< 3t9-A- s A AAc$V^8dQhRRRRRR/#rr rr r r Noner )rs"rrr;s&PPPcPdPrc\W4pVPPRRR7VP\ \ V4^,4RR7R# \ d"p\PRY4Rp?R#Rp?ii;i)T)parentsexist_okzutf-8rz,left-core retry stamp not written for %s: %sN) rparentmkdir write_textr r!rloggerdebug)r r rexcs&& r _note_failurer.;so 4 (EP 4$7 ^E2Q67'J P CTOOPsA A B#A??Bc$V^8dQhRRRRRR/#)rr rr r r boolr )rs"rrrDs&]]4]]]rc(\W4p\P!4VP4P, p\ \ T4^ 4pT\ \^T^, ,,\48# \dR#i;i)F) rtimestatst_mtimerminr!STARTUP_RETRY_SECONDSSTARTUP_RETRY_MAX_SECONDS)r r ragefailuress&& r_failed_recentlyr:Dsv 4 (EiikEJJL111>%("-H *Q8a<-@@B[\ \\ s4B BBc$V^8dQhRRRRRR/#r#r )rs"rrrNs!999c9d9rc<\W4PRR7R#)zXA later failure (the plugin removed, then missed again) starts the backoff from an hour.T) missing_okN)runlinkrs&&r _note_successr?Ns4 ''4'8rc V^8dQhRRRR/#rr rr r r )rs"rrrSs55d5s5rc^RIHpV!V4;'g/PR4;'g/p\VPR4;'gR4P 4#)z<``memory.provider`` of *home*'s effective config, or ``""``.)read_home_selectionmemoryprovider)pm.plugins_staterCgetr r)r rCrDs& rconfigured_providerrISsO4!$'--2 2 28 < B BF vzz*%++ , 2 2 44rc$V^8dQhRRRRRR/#)rnamer r rr r0r )rs"rrrZs! * *3 *d *t *rcn^RIHp^RIHpHpV!V4pV!V4RJV!V4# T!T4i;i)zTrue when the provider resolves anywhere Hermes looks for *home* (bundled, that home's user plugins, entry point). The lookup reads the active home, so it is bound explicitly: the update hook walks several profile homes from one process.)find_provider_dirreset_hermes_home_overrideset_hermes_home_overrideN)plugins.memoryrMhermes_constantsrOrP)rKr rMrOrPtokens&& rprovider_presentrTZs81U $T *E* &d2"5)"5)s * 4c V^8dQhRRRR/#)rrKr r Optional[str]r )rs"rrrgs5555rcB^RIHpV!V4pVe VP#R#)zZThe catalog entry that ships provider *name*, or None when the catalog has no such plugin.)get_live_catalog_entryN)hermes_cli.plugin_catalogrXrK)rKrXentrys& rcatalog_sourcer[gs#@ "4 (E*5::44rcategoryc$V^8dQhRRRRRR/#)rrKr r\rVr r )rs"rrrns!55s55-5rc^RIHpV'd V!V4MRpTeTeTPT8wdR#^RIHp\ Y!44# \dR#i;i)u``hermes [-p ] plugins install `` when this checkout's catalog ships plugin *name* (of *category*, when given), else None. Recovery copy for a provider that left core and is not installed (offline, lazy installs off, a failed migration): doctor, ``memory status``, ``memory setup `` and the CLI's unknown-command error point at the one command that fixes it. In-tree catalog only, never the network — these run offline and on error paths.)get_catalog_entryN)get_hermes_home)rYr_ Exceptionr\rRr`_install_command)rKr\r_rZr`s&$ rcatalog_install_hintrcnsZ?+/!$'T }-%..H2L0 D/"3 44 s A A AAc$V^8dQhRRRRRR/#)rr rsayCallable[[str], None]r rVr )rs"rrrs"  D *? M rc\V4p^RIHpV!V4'g\W 4'dR#\ V4fV!RV R24R#V#)zThe provider *home* needs from the catalog, or None (nothing to do, or a catalog miss already reported through *say*). Read-only.)is_core_memory_providerN ⚠ Memory provider 'z' is configured but not installed and not in the plugin catalog. Install it with `hermes plugins install ` or change memory.provider.)rIagent.memory_providerrhrTr[)r rerKrhs&$ r_pending_providerrksY t $D=t$$(8(D(Dd# %dV,[ \ ] Krc$V^8dQhRRRRRR/#)rrKr r rr r )rs"rrrs! 9 93 9d 9s 9rcr^RIHp^RIHpV!V4pVeVR8XdV!4R8XdRV 2#RV RV 2#)a The exact command that installs *name* into *home*. ``-p`` is dropped only for the default home while no sticky profile is set: a bare command run from a shell targets the sticky profile, never the home of the agent (Desktop, gateway, ``hermes -p``) that printed it.)get_active_profileprofile_name_for_homedefaultzhermes plugins install z hermes -p z plugins install )hermes_cli.profilesrnrRrp)rKr rnrpprofiles&& rrbrbsL76#D)G7i/4F4HI4U(// y 1$ 88rc ,V^8dQhRRRRRRRRR R /#) rr rrKr installCallable[[str], dict]rerfr r0r )rs"rrrs24s8M/48rc LV!V4pVPR4'dV!RV R24R#\VPR4;'gR4PR4pV!R V R V R \ W4 R 24R# \dpRRR\T4/pRp?LRp?ii;i) okFerrorNu ✓ Memory provider 'u' moved out of core — installed its plugin from the catalog (memory.provider and your stored memories are unchanged; check its settings with `hermes memory status`).Tz unknown errorz. riz>' moved out of core and could not be installed automatically: z. Run ``.)rar rHrstriprb)r rKrureresultr-rys&&$$ r_install_pendingr}s2zz$ %dV,' ( )  7#66 7 > >t DE !$'e ')$56b :;  2wC12sA?? B# BB#rec(V^8dQhRRRRRRRR/#) rr rrurvrerfr rVr )rs"rrrs1 T Tt T)> TEZ Tgt TrcT\WR7pVfR#\WWR7'dV#R#)a4Install the configured provider's catalog plugin into *home* when the provider is gone. Returns the installed plugin name, or None when nothing needed doing or the install could not happen (already reported through *say*). Never raises: memory being down must not take the update or the agent down with it. reNrure)rkr})r rurerKs&$$ r migrate_homers- T +D |#DII4StSrcV^8dQhRR/#rr r0r )rs"rrrskkdkrc\PRJ;'d_\PRJ;'dE\PP4;'d\PP4#N)sysstdinstdoutisattyr rr _interactiversO 99D j jSZZt%; j j @P@P@R j jWZWaWaWhWhWjjrcV^8dQhRR/#rr )rs"rrrs::T:rcJ^RIHp\4'*;'dV!4#)aWithout a terminal (Desktop, gateway, ``hermes update`` from a script) nobody can answer the dependency prompt, so every provider that declares Python deps would fail to migrate. The configured ``memory.provider`` plus ``security.allow_lazy_installs`` (read for the active home, i.e. the one being migrated) is the same consent that let the bundled provider install its deps on demand; with a terminal the user is still asked.lazy_installs_allowed) pm.installrrrs r_unattended_consentrs 1~  9 9"7"99rc V^8dQhRRRR/#)rr rr r0r )rs"rrrs****rcb^RIHpHpV!V4p\4V!V4# T!T4i;i)rN)rRrOrPr)r rOrPrSs& r _home_consentrs,U $T *E*"$"5)"5)s $ .consentc$V^8dQhRRRRRR/#)rr rrzOptional[bool]r rvr )rs"rrrs"   . DY rcaaRVV3RllpV#)c V^8dQhRRRR/#)rrKr r dictr )rs"rr#_install_into..__annotate__s . .s .t .rc<^RIHp^RIHpHpV!S4pT!RRRTSfV\ 9;'d \ 4MSR7V!V4# T!T4i;i)r)dashboard_install_pluginrNrFFT)forceenable catalog_nameassume_deps_consent)hermes_cli.plugins_cmdrrRrOrP _LEFT_COREr)rKrrOrPrSrr s& r_install_install_into.._installs_CY(. .+BeDW[/6BFASAmAmXkXmDKM 'u - &u -sA A Ar )r rrsfd r _install_intors . . Orc V^8dQhRRRR/#rAr )rs"rrrs<TPS T3.4PT4Kc .pVP4EFwwo r\V 4^8dB\4'd2S!RS R \V 4 R R PR V 44 R 24V!4;_uu_4\!V 4Fwr\#VS \%V4V!V4R7'dVPS 4K<W^,Rp V 'dMS!RS RR PRV 44 R2R PV 3RlV 44,R,4M RRR4EK V# \d#p\PRYW4Rp?EKRp?ii;i +'giEKe;i \&d S!R4T#i;i)a``hermes update`` hook: every profile home sharing this venv. Returns installed plugin names. Each line names the profile it is about. Homes missing the same provider share one environment, so they share one set of dependency answers (#125794): the first install asks, the rest reuse its answers. Homes are grouped by provider AND by their unattended consent (each home's own ``security.allow_lazy_installs``), so a refusal only speaks for homes that would be refused the same way: when an install in a group fails, the rest of that group are named in one line instead of failing (or re-prompting) one by one, and the other groups still migrate. Ctrl-C ends the migration with a message, not a traceback into the updater. )shared_dependency_answers)dependency_homesc V^8dQhRRRR/#)rr rr rfr )rs"rr'migrate_all_homes..__annotate__sRRtR 5Rrc<aVV3Rl#)cN<S!R\S4 RVP4 24#)z [z] )rlstrip)messager res&r5migrate_all_homes..labelled..s%sST):(;2gnn>N=O#PQrr )r resfrlabelled#migrate_all_homes..labelleds QQrrz,memory provider migration skipped for %s: %sNz Memory provider 'z' is configured in z profiles (z, c38"TFp\V4xK R#5irr.0hs& r $migrate_all_homes..s!@%Q+a..%zA); your answers to its dependency questions apply to all of them.rriz' was not installed for c38"TFp\V4xK R#5irrrs& rrrs(FAQrz either. Run c3D<"TFpR\SV4 R2xK R#5i)`N)rb)rrrKs& rrrs%'WRVQ!,` (with `-p `) for the rest.)hermes_cli.plugins_cmd_installrrGrrkr0rrar+r, setdefaultappenditemslenrjoin enumerater}rKeyboardInterrupt)rerrrpendingr rr- installed_consenthomesindexrestrKsd @rmigrate_all_homesrs I1RR35G " $Tx~>D4j88]4%8G 4   g 3 : :4 @#IW'.}} # T85zA~,..)$/B3u:,O !@%!@@AB678+,,#,U#3KE'dM$ 7 HHHc$V^8dQhRRRRRR/#)rrKr rezOptional[Callable[[str], None]]r r0r )rs"rrrs#,,S,*I,UY,rc $a^RIHpHpV!4pV!V4V3pV\9dR#\P V4RV3Rllp^RIHpV!4'gV!RV R\W4 R24R#V\9d,\WFR 7V8XdV!RV R \W4 R24R#\W@4'dV!RV R \W4 R24R#\V\VR R 7VR7V8HpV'd\W@4V#\W@4V#)zAgent-init hook for a configured provider that resolved nowhere. One attempt per process per home and name; honours ``security.allow_lazy_installs`` because it installs code. True when installed.)r`hermes_home_keyFc V^8dQhRRRR/#)rrr r r$r )rs"rr(recover_at_startup..__annotate__$sTTTTrc<\PV4Se S!V4R#R# \d\PRRR7R#i;i)Nz$Memory migration notification failedT)exc_info)r+warningrar,)rres&rreport"recover_at_startup..report$sJw ? TG   T Cd S Ts("A Aru⚠ Memory provider 'z' is not installed, so external memory is off for this session. security.allow_lazy_installs is off, so Hermes did not fetch it: run `rzrz' is not installed, so external memory is off for this session. It never shipped with Hermes, so Hermes installs it only when you ask: run `zl' is not installed, so external memory is off for this session. Its automatic install failed recently: run `T)rr)rRr`rraddrrrbrrkr:rrr?r.) rKrer`rr keyrrrs &d rrecover_at_startuprs4B  D 4 $ 'C jNN3TT1 " "&tf-'34B8 9  : T .$ 6 *4&1+D78< =##&tf->>Nt>Z=[[]_ `T=t+LRXY]aaId!  d! r>mem0honchoretaindb byterover hindsight openviking holographic supermemorygu"A)+__conditional_annotations____doc__ __future__rloggingrr2pathlibrtypingrr getLogger__name__r+setr__annotations__ frozensetrr6r7rr!r.r:r?rIrTr[rcrkrbr}printrrrrrrrr)rs@rrs(# %   8 $#&5 ( { | +9 .P]9 5 *555&  9" T]b Tk:* 4 < 1e1h,D,,r