[j dZddlmZddlZddlZddlZddlZddlZddlm Z m Z m Z m Z m Z ddlmZddlmZddlmZejeZdd d d d d ddd idddgddZddd d dd ddd d dd ddgddZddd d dd d d gd!d"d d d d#dgddZd$d%d d&d d d igddZd'd(d d d)d d d*d d+d,d d d-d d d.d d/gddZeeeeegZGd0d1eZd5d4ZdS)6uVHoncho memory plugin — MemoryProvider for Honcho AI-native memory. Provides cross-session user modeling with dialectic Q&A, semantic search, peer cards, and persistent conclusions via the Honcho SDK. Honcho provides AI-native cross-session user modeling with dialectic Q&A, semantic search, peer cards, and conclusions. Five tools (profile, search, reasoning, context, conclude) are exposed through the MemoryProvider interface. Config: Uses the existing Honcho config chain: 1. $HERMES_HOME/honcho.json (profile-scoped) 2. ~/.honcho/config.json (legacy global) 3. Environment variables ) annotationsN)AnyCallableDictListOptional)sanitize_context)MemoryProvider) tool_errorhoncho_profileuRead or write a peer's CARD — a short, curated list of standing facts about that peer (name, role, preferences, communication style, recurring patterns). This is the cheapest, fastest Honcho call: no query, no LLM, just the current card. Pass `card` to overwrite it; omit `card` to read. An empty read returns a `hint` explaining why (observation disabled, fresh peer, representation still warming up) — that is NOT an error; the card accumulates over time from observed conversation. Related tools: honcho_context for the fuller standing snapshot (card + representation + summary + recent messages); honcho_search to find specific things that were actually said; honcho_reasoning for a synthesized answer to a question.objectstringzaPeer to query. Built-in aliases: 'user' (default), 'ai'. Or pass any peer ID from this workspace.)type descriptionarrayrzGNew peer card as a list of fact strings. Omit to read the current card.)ritemsr)peercard)r propertiesrequired)namer parameters honcho_searchu2Hybrid (semantic + keyword) search over a peer's actual message history across ALL past sessions they took part in — not just the current one. Returns RRF-ranked raw message excerpts (what was literally said, including the assistant's own messages about the peer), no LLM synthesis. Cheaper and faster than honcho_reasoning. Use this to recall specific past facts — 'what did I say about X', 'what was the regimen/decision/config we settled on' — and reason over the excerpts yourself. For nuanced questions needing synthesis, use honcho_reasoning instead.uqWhat to look for — a topic, keyword, name, or natural-language description of the fact you're trying to recall.integerztApproximate budget for returned excerpts (default 800, max 2000). Larger budgets return more/longer ranked snippets.zWhose history to search. Built-in aliases: 'user' (default), 'ai'. Or pass any peer ID from this workspace. Spans every session that peer took part in.)query max_tokensrrhoncho_reasoninguGAsk Honcho's dialectic agent a natural-language question about a peer and get back a SYNTHESIZED answer. This is the only Honcho tool that runs an LLM: it agentically searches both raw messages and derived conclusions, reasons over them, and writes a prose answer — so it is the slowest and most expensive call (seconds + tokens). Reach for it for nuanced or open-ended questions ('how does this person prefer to receive feedback?', 'what's their relationship to project X?') where you want Honcho to do the synthesis. For a specific fact that was stated, prefer honcho_search (cheap, raw excerpts, you synthesize). For standing profile facts, prefer honcho_profile / honcho_context (no LLM). Pass reasoning_level to control depth: minimal (fast/cheap), low (default), medium, high, max (deep/expensive). Omit for the configured default.zA natural language question.uOverride the default reasoning depth. Omit to use the configured default (typically low). reasoning_level parameter guide: - minimal: use ONLY for a single quick factual lookup (e.g. 'what is the user's name'). Honcho hard-caps this tier's output at 250 tokens combined with the model's own hidden reasoning tokens — a multi-part answer can get cut off mid-thought before it even reaches the final-answer phase, especially on models with reasoning/thinking enabled. - low/medium/high/max: use for anything requiring a synthesized, multi-fact, or summary-style answer (e.g. 'summarize known facts about this peer', 'what are their communication preferences'). These tiers have no output-token cap of their own (fall back to Honcho's 8192-token global default), so they don't have minimal's cutoff failure mode. - low: straightforward questions with clear answers - medium: multi-aspect questions requiring synthesis across observations - high: complex behavioral patterns, contradictions, deep analysis - max: thorough audit-level analysis, leave no stone unturned Default to at least 'low' unless the query is genuinely a single fact lookup.minimallowmediumhighmax)rrenum)rreasoning_levelrhoncho_contextuRetrieve the standing SNAPSHOT Honcho holds for the current session — session summary, the peer's representation, the peer card, and the most recent messages — in one call. No query, no LLM synthesis (cheaper than honcho_reasoning). Use it to orient yourself on what Honcho currently knows about this conversation and peer. This is a fixed snapshot, not a search: to look up a specific past fact use honcho_search; to ask a question and get a synthesized answer use honcho_reasoning; for just the compact card use honcho_profile.rhoncho_concludeu^Write, delete, or list CONCLUSIONS — persistent, derived facts about a peer that feeds their long-term profile (card + representation). Use this to record something durable you've learned about the peer (a stable preference, a correction, a standing constraint) so future sessions carry it forward. You MUST pass exactly one of `conclusion` (to create), `delete_id` (to delete), or `list` (to list/search); any other combination is an error. A deletion ID is an opaque server-generated string: first call with `list=true` and optionally `query`, then pass the returned ID as `delete_id`. Deletion exists only for PII removal — for merely wrong facts, write a corrected conclusion instead; Honcho self-heals contradictions over time. This is a WRITE tool: to read the profile use honcho_profile / honcho_context, and to search what was said use honcho_search.zxA factual statement to persist. Provide this when creating a conclusion. Do not send it together with delete_id or list.uConclusion ID to delete for PII removal. Provide this when deleting a conclusion. Do not send it together with conclusion or list. Get this id from a prior `list` call — never guess it.booleanzSet to true to list or search stored conclusions (with their ids) instead of creating or deleting one. Do not send together with conclusion or delete_id.z}Optional semantic search query, used only when `list` is true. Omit to list the most recent conclusions instead of searching.ztThe peer the conclusion is ABOUT. Built-in aliases: 'user' (default), 'ai'. Or pass any peer ID from this workspace.) conclusion delete_idlistrrceZdZUdZdcdZdddedZedfd Zdgd Zd Z dZ dhdZ didZ djdZ dddkdZdidZdgdZdgdZdld Zdfd!Zd"d#dmd%Zdfd&Zdnd(Zd"d#dod)Zd*d+d*d+d*d,d-Zd.ed/<d0Zd1Zd2Zd3Zd4Zd5Zd6Z d3Z!dgd7Z"dpd9Z#dqd:Z$drd;Z%dsdtd=Z&dudAZ'e(dvdCZ)dDdEdwdGZ*e+j,dHe+j-Z.e/dxdIZ0dydLZ1e(dzdOZ2d{dRZ3d"d#d|dUZ4 ddd}dZZ5d~d]Z6dd^Z7ddaZ8ddbZ9dS)HonchoMemoryProviderzHHoncho AI-native memory with dialectic Q&A and persistent user modeling.return List[str]cg} ddlm}|}|t|jn#t $rYnwxYw|S)zHoncho keeps its peer/session config under ~/.honcho when no profile-local honcho.json exists (see client.resolve_config_path).)resolve_global_config_path)clientr2appendstrparent Exception)selfpathsr2 global_cfgs @/home/ice/.hermes/hermes-agent/plugins/memory/honcho/__init__.py backup_pathsz!HonchoMemoryProvider.backup_pathsss  : : : : : :3355J LLZ.// 0 0 0 0    D  s7< A A Nquery_rewriterOptional[Callable[[str], str]]c,d|_d|_d|_||_d|_t j|_d|_d|_ d|_ d|_ t j|_ d|_ d|_d|_d|_d|_d|_d|_d|_d|_d |_d |_d |_d |_d|_d|_d|_d|_d|_t j|_d|_ d|_!dS) NhybridrFz every-turnr1Tr")"_manager_config _session_key_query_rewriter_prefetch_result threadingLock_prefetch_lock_prefetch_thread _sync_thread _recall_mode_base_context_cache_base_context_lock _turn_count_query_rewrite_enabled_injection_frequency_context_cadence_dialectic_cadence_dialectic_depth_dialectic_depth_levels_reasoning_heuristic_reasoning_level_cap_last_context_turn_last_dialectic_turn_prefetch_thread_started_at_prefetch_result_fired_at_dialectic_empty_streak_session_initialized_lazy_init_kwargs_lazy_init_session_id _init_thread _init_lock _init_error _cron_skipped)r8r=s r;__init__zHonchoMemoryProvider.__init__s'  - "'n..<@8<$37 "+."2"2&+#$0! !"# !9=$*.!)/!"&$(!36(.2&,-$%*!1548"8<#.**#r5cdS)Nhonchor8s r;rzHonchoMemoryProvider.name*sxrgboolc ddlm}|}|jot |jp|jS#t$rYdSwxYw)z0Check if Honcho is configured. No network calls.r)HonchoClientConfigF)plugins.memory.honcho.clientrnfrom_global_configenabledrlapi_keybase_urlr7)r8rncfgs r; is_availablez!HonchoMemoryProvider.is_available.sj  G G G G G G$7799C;D4 (Cs|#D#D D   55 s;> A  A c$ddl}ddl}ddlm}||dz }i}|r4 |j|}n#t$rYnwxYw||ddl m }|||ddS)zDWrite config to $HERMES_HOME/honcho.json (Honcho SDK native format).rN)Pathz honcho.json)atomic_json_writei)mode) jsonospathlibrwexistsloads read_textr7updateutilsrx) r8values hermes_homerzr{rw config_pathexistingrxs r; save_configz HonchoMemoryProvider.save_config7s        d;''-7        %4:k&;&;&=&=>>    +++++++xe<<<<<$[kuM N N.Q R R  rgrconfigdictNonecTddl}ddlm}||dS)z:Run the full Honcho setup wizard after provider selection.rN) cmd_setup)typesplugins.memory.honcho.clirSimpleNamespace)r8rrrrs r; post_setupzHonchoMemoryProvider.post_setupMs? 777777 %''))*****rg session_idc  |dd}|dd}|dvs|dkr%td||d|_d Sd d lm}m}d d lm}| }|j r|j s#|j std d S||_ |j|_td|j|j|_|j|_|j|_|j|_|j|_|j|_t9dt;|jd|_|j |_!|j"|_#|j$|j%vr |j$|_&tO||_(||_)|j*||fi||_+|jdkr9|j,r|-d Stdd S|.dd S#t^$rtdYd St`$r-} t1d| d |_2Yd } ~ d Sd } ~ wwxYw)zInitialize Honcho session manager. Handles cron guards, recall configuration, session resolution, memory migration, and optional dialectic prewarming. agent_contextr@platformcli>cronflushrzBHoncho skipped: cron/flush context (agent_context=%s, platform=%s)TNr)rnget_honcho_clientHonchoSessionManageru)Honcho not configured — plugin inactivezHoncho recall_mode: %sr1toolsuGHoncho tools-only mode — deferring session init until first tool callg? wait_timeoutu3honcho-ai package not installed — plugin inactivezHoncho init failed: %s)3getloggerdebugrerornrplugins.memory.honcho.sessionrrprqrrrsrE recall_moderNinjection_frequencyrScontext_cadencerTdialectic_cadencerU query_rewriterRfirst_turn_base_wait_FIRST_TURN_BASE_TIMEOUTfirst_turn_dialectic_wait_FIRST_TURN_DIALECTIC_CAPr#mindialectic_depthrVdialectic_depth_levelsrWreasoning_heuristicrXreasoning_level_cap _LEVEL_ORDERrYrr`ra_resolve_session_keyrFinit_on_session_start_ensure_session_start_session_init_background ImportErrorr7warningrD) r8rkwargsrrrnrrrtes r; initializezHonchoMemoryProvider.initializeSs < !"JJ;;Mzz*e44H 111X5G5G a*H666%)" Z Z Z Z Z Z Z Z J J J J J J$7799C; s{ cl  HIIIDL #D  LL143D E E E(+(?D %$'$7D !&)&;D #*-*;D ',/,DD )-0-JD *$'3s/BA+F+F$G$GD !+.+ED ((+(?D %&$*;;;,/,C) &*&\\D ")3D & 9 9#z T TV T TD  G++,((***F fggg  / /S / A A A A A P P P LLN O O O O O O ! ! ! NN3Q 7 7 7 DMMMMMMM !s8AHAH0D*HH8H$I-7 I-"I((I-c |d}|d}||||p|pdS)z??  $ $+%$7 %       rgrCrrfloatc`jsjrdSjrjdSj5jsjr ddddSjr'jr ddddSjrj ddddSjtjjpdd fd }tj |dd_j |d krj | ddddS#1swxYwYdS) aStart Honcho session initialization in a daemon thread. This keeps Hermes CLI/gateway startup responsive when Honcho is down, slow, or its database is unhealthy. The thread may still take the SDK timeout path, but it cannot block agent construction or first prompt assembly. ``wait_timeout`` lets fast/mock initializations finish before returning while still failing open for slow backends. Nrr.rc jfid_d_d_dS#t$rA}t |_d_td|Yd}~dSd}~wwxYw)Nr@z)Honcho background session init failed: %s) _do_session_initr`rardr7r5rDrr)rrt init_kwargsinit_session_idr8s r;_runzAHonchoMemoryProvider._start_session_init_background.._runsS)D)#NN+NNN-1D*15D.')D$$$ SSS'*1vvD$$(DMNN#NPQRRRRRRRRRSs$) A46A//A4Tzhoncho-session-inittargetdaemonrrtimeoutr.r) rer_rEr`rcrbis_aliverrarIThreadstartjoin)r8rrrtrrs` @@@r;rz3HonchoMemoryProvider._start_session_init_backgrounds0   !:  F| t5= F _ = =! T%>  = = = = = = = =  T%6%?%?%A%A   = = = = = = = = < 4#9#A  = = = = = = = =,Ct566K"8LrAcontextzcSummarize what you know about this user. Focus on preferences, current projects, and working style.r.rc d}nC#t$r6}td|xjdz c_Yd}~dSd}~wwxYw|rQ|r=j5|_d_dddn #1swxYwYd_ d_dSxjdz c_dS)NFuse_query_rewritez#Honcho dialectic prewarm failed: %sr1r _run_dialectic_depthr7rrr^striprKrHr]r[)rexc_prewarm_queryr8s r;_prewarm_dialecticzAHonchoMemoryProvider._do_session_init.._prewarm_dialectics9 55*e6% %JCPPP44944:QWWYY:!0??45D1=>D:???????????????561784444494444s& A+AA;BBBTzhoncho-prewarm-dialecticrz0Honcho dialectic prewarm started for session: %szEHoncho generic dialectic prewarm skipped: awaiting first user messager)rorrrrrrDrrFrr get_or_createmessagessession_strategyhermes_constantsrr5migrate_memory_filesr7rNrGrRtime monotonicr\rIrrrLr_)r8rtrrrrr3sessionrmem_dirrrprewarm_threadrs` @r;rz%HonchoMemoryProvider._do_session_initsBBBBBBFFFFFF""3'',,-#)::i#8#8#@D'-zz-'@'@'HD     6D5c:PPPP 68IJJJ---d.?@@ H# (< (M(M<<<<<<oo//*<== 2243DgNNN Y[_[lmmmm%66 u% H H H LLCQ G G G G G G G G H   5 5 5#+43N+Q :::::::$48>3C3C0!*!1-3""" $$&&&(6% OQUQbcccc [%)!!!s2BE FE;;Fc|jr |jrdS|jrdS|jr|jrdS|jr|jdS |j|j|jpdfi|jd|_d|_|jduS#t$r4}d|_d|_t d|Yd}~dSd}~wwxYw)zLazily initialize the Honcho session (for tools-only mode). Returns True if the manager is ready, False otherwise. TFNrz#Honcho lazy session init failed: %s) rDr_rerbrrEr`rrar7rr)r8rs r;rz$HonchoMemoryProvider._ensure_session(s = T6 4   5   !2!;!;!=!= 5| t5=5  !D ! *>.>  (    &*D ")-D &=, ,    DM(-D % NN@! D D D55555  s 6B C)B==Ccv|jr|jsdS|jrdS|jo|j S)aReturn whether a manager/session key can be used safely. Background initialization sets ``_manager`` before the blocking get-or-create call completes, so ``_session_initialized`` guards real async startup. Tests and legacy direct construction may inject a ready manager/session key without setting that flag; allow that only when no init thread is currently in flight. FT)rDrFr_rbrrks r;_session_readyz#HonchoMemoryProvider._session_readyFsM} D$5 5  $ 4%F$*;*D*D*F*FGGrgctxcg}|dd}|r|d||dd}|r|d||dd}|r|d||dd}|r|d ||d d}|r|d ||sdSd |S) zEFormat the prefetch context dict into a readable system prompt block.summaryr@z## Session Summary representationz## User Representation rz## User Peer Card ai_representationz## AI Self-Representation ai_cardz## AI Identity Card  )rr4r)r8rpartsrreprai_reprs r;_format_first_turn_contextz/HonchoMemoryProvider._format_first_turn_contextUs9'')R((  ; LL999 : : :gg&++  ; LL9C99 : : :wwvr""  7 LL5t55 6 6 6,b11  A LL?v?? @ @ @'')R((  < LL::: ; ; ; 2{{5!!!rgc|jrdS|jr|js |jsdS|jdkrd}n|jdkrd}nd}|S)uReturn system prompt text, adapted by recall_mode. Returns only the mode header and tool instructions — static text that doesn't change between turns (prompt-cache friendly). Live context (representation, card) is injected via prefetch(). r@ru# Honcho Memory Active (context-injection mode). Relevant user context is automatically injected before each turn. No memory tools are available — context is managed automatically.ru# Honcho Memory Active (tools-only mode). Use honcho_profile for a quick factual snapshot, honcho_search for raw excerpts, honcho_context for raw peer context, honcho_reasoning for synthesized answers (pass reasoning_level minimal/low/medium/high/max — you pick the depth per call), honcho_conclude to save facts about the user. No automatic context injection — you must use tools to access memory.u# Honcho Memory Active (hybrid mode). Relevant context is auto-injected AND memory tools are available. Use honcho_profile for a quick factual snapshot, honcho_search for raw excerpts, honcho_context for raw peer context, honcho_reasoning for synthesized answers (pass reasoning_level minimal/low/medium/high/max — you pick the depth per call), honcho_conclude to save facts about the user.)rerDrFrErN)r8headers r;system_prompt_blockz(HonchoMemoryProvider.system_prompt_blockrs   2} D$5 < r   ) )) F  ' ) )Z F@  rgr@)rrct jrdSjdkrdSd}jdkraj}t jdd}|t |td|}tj td|z} sm |Aj }|8| td|tj z  sdSjdko jdk}r-}|r|ndSg} |sj5jdu} | rd_j_j} dddn #1swxYwY| r jridfd } t-j| d d } | |$td|tj z nd}| |d}|r_jj|}|r(j5|_dddn #1swxYwY|} n/| rt<d|| sgjr`jj}|r?|}|r(j5|_dddn #1swxYwY|} | r| | j!5tEj#}dddn #1swxYwY|rj$dkr j_$j$dkr%r"j%}t jdd}|t |td|}&r j'}|| |nv|}jdfd }tj _(t-j|d d}||_'j' |j'r4j'rt<d|}|r)|)r| || sdSd | }|}|S)uReturn base context (representation + card) plus dialectic supplement. Assembles two layers: 1. Base context from peer.context() — cached, refreshed on context_cadence 2. Dialectic supplement — cached, refreshed on dialectic_cadence Returns empty in tools-only mode and respects the configured injection frequency and context budget. r@rNr1rrCr first-turnr.rc  jjpdpi}|d<|r"jj|dSdS#t$r&}t d|Yd}~dSd}~wwxYw)Nrz)Honcho first-turn base context failed: %s)rDget_prefetch_contextrFset_context_resultr7rr)rr _ctx_holderrr8s r; _fetch_basez2HonchoMemoryProvider.prefetch.._fetch_basesU"m@@ -u} .1 E*U M<._run_first_turn"s< 55e<<$ %MsSSS44944:QWWYY:!0GG45D1=FD:GGGGGGGGGGGGGGG5>1784444494444& A+AA9BBBzhoncho-prefetch-firstuSHoncho first-turn dialectic still running after %.1fs — will surface on next turnrr)*rerNrQrgetattrrErr#rrrrrbrrS_is_trivial_prompt_consume_pending_dialectic_truncate_to_budgetrPrOrZrDrIrrrpop_context_resultrFrrrrr4rKrlrHr[r_thread_is_liverLr\r)r8rrfirst_turn_base_deadline base_waitrequest_timeoutrb _skip_basereadyr_first_base_fetch base_contextr _bt _base_wait_ctx formatted fresh_ctx_prewarm_landed _dia_wait_live_first_turn_timeoutrfirst_turn_threaddialectic_resultresultr rs`` @@r;prefetchzHonchoMemoryProvider.prefetchs4   2   ' '2#'  q 5I%dlItDDO* 3sO+D+DEE '+~'7'7#c9:M:M'M $""$$   / / 1 1 1'3#0 + %% #C)ADNDTDT)T U U&&&(( r  % 5 N$:JQ:N   " "5 ) ) D3355E6;C4++E222 C; +( 8 8$($<$D!$?/1D,.2.>D+#7  8 8 8 8 8 8 8 8 8 8 8 8 8 8 8!$ T]$ /1  U U U U U U U U &&t:M 0;58H8HHIII ,,,"u-- M44T5FGGG $ ? ? E EI 1!4AA7@D4AAAAAAAAAAAAAAA'0 \\^^LL45? % 1 1 M<3C3C0$-$4*4>U%%%!"'')))(9%%**3F*GGG$ )>)G)G)I)I  0 ::<<  + 0 6 6 8 8 + LL) * * * 2U##))&11 sH.&F  F$'F$=JJJL**L.1L.M66M:=M:c>|j5|j}|j}d|_d|_dddn #1swxYwY|j|jz}|r8|dkr2|j|z |kr$t d||j|dS|r|r|ndS)zPop any pending dialectic result, applying the stale-discard guard. Returns an empty string when no result is ready or the pending result is older than the configured cadence window. r@rBNrzKHoncho pending dialectic discarded as stale: fired_at=%d, turn=%d, limit=%d) rKrHr]rU_STALE_RESULT_MULTIPLIERrQrrr)r8r(fired_at stale_limits r;rz/HonchoMemoryProvider._consume_pending_dialecticPs   2 2#4 5H$&D !-1D *  2 2 2 2 2 2 2 2 2 2 2 2 2 2 2-0MM  A 43Ch3NR]2]2] LL$%-t/?   2$4Z9I9O9O9Q9QZXZZs 155textc|jr |jjs|S|jjdz}t||kr|S|d|}|d}||dzkr |d|}|dzS)z9Truncate text to fit within context_tokens budget if set.N g?u …)rErlenrfind)r8r/ budget_chars truncated last_spaces r;rz(HonchoMemoryProvider._truncate_to_budgetfs| 4<#> K|2Q6 t99 $ $K,' __S))  s* * *!+:+.I6!!rgcjrdSjdkrdSrsdSrdSjdkpjjz jk}jdkrb|r`j_ j j n2#t$r%}td|Yd}~nd}~wwxYwrtddS}jjz |kr7td|jjjjz dSjfd}t)j_t/j|d d }||_dS) zFire background prefetch threads for the upcoming turn. Context and dialectic refreshes have independent cadence controls. Nrr1rz"Honcho context prefetch failed: %sz=Honcho dialectic prefetch skipped: prior thread still runningzhHoncho dialectic prefetch skipped: effective cadence %d (base %d, empty streak %d), turns since last: %dc }nC#t$r6}td|xjdz c_Yd}~dSd}~wwxYw|rQ|r=j5|__dddn #1swxYwY_ d_dSxjdz c_dS)NzHoncho prefetch failed: %sr1rr)r)rrrr8s r;rz1HonchoMemoryProvider.queue_prefetch.._runs+ 22599    91===,,1,,  2&,,.. 2(??,2D)5>D2???????????????-6)/0,,,,,1,,,,rTzhoncho-prefetchr)rerNrrrrTrQrZrSrDprefetch_contextrFr7rrr_effective_cadencer[rUr^rrr\rIrrrL) r8rr context_duer effectiverprefetch_threadrs `` @r;queue_prefetchz#HonchoMemoryProvider.queue_prefetchtsG    F   ' ' F""$$ E   / / 1 1 1 F  " "5 ) )  F  !Q & U 4#::t?TT   $ 4 4 4&*&6D # F ..t/@%HHHH F F F A1EEEEEEEE F    ! !  LLX Y Y Y F++--  t8 8I E E LLC42D4P 4#<<     F$  2 2 2 2 2 2 2 ,0>+;+;(#*+<     /s B;; C*C%%C*baserr ))r1r)r)rAr1)rr)rr1)rrAzdict[tuple[int, int], str]_PROPORTIONAL_LEVELSrxig@rAg@c*|jr|jsdS|jr|jjr |jjnd}t j|jz }|||jzkr&t d|||jzdSdS)zThread-alive guard that treats threads older than the stale threshold as dead, so a hung Honcho request can't block new fires.Fg @uSHoncho prefetch thread age %.1fs exceeds stale threshold %.1fs — treating as deadT) rLrrErrrr\_STALE_THREAD_MULTIPLIERrr)r8rages r;rz$HonchoMemoryProvider._thread_is_lives$ D,A,J,J,L,L 5+/<YDL=120 chars, +2 at >=400. rr1rA)rXrr3_HEURISTIC_LENGTH_MEDIUM_HEURISTIC_LENGTH_HIGHindexrYr)r8r@rnbumpbase_idxcap_idxs r;_apply_reasoning_heuristicz/HonchoMemoryProvider._apply_reasoning_heuristics (  K t( ( (K JJ t, , ,DD , , ,DDD$**400#))$*CDD X_g!>!>??rgpass_idxc|jr%|t|jkr |j|S|jr |jjnd}|j|j|f}||dkr|||S|S)utResolve reasoning level for a given pass index. Precedence: 1. dialecticDepthLevels (explicit per-pass) — wins absolutely 2. _PROPORTIONAL_LEVELS table (depth>1 lighter-early passes) 3. Base level = dialecticReasoningLevel, optionally scaled by the reasoning heuristic when the mapping falls through to 'base' r Nr@)rWr3rEdialectic_reasoning_levelrBrrVr_)r8r`rr@mappings r;_resolve_pass_levelz(HonchoMemoryProvider._resolve_pass_level&s  ' :Hs4;W7X7X,X,X/9 9:>,Q 66E+//1F0QRR ?g//224?? ?rg prior_results list[str]is_coldc|dkr|r dS dS|dkr|r|dnd}d|dSd t|dkr|dnd d t|dkr|dnd d S) aBuild the prompt for a given dialectic pass. Pass 0: cold start (general user query) or warm (session-scoped). Pass 1: self-audit / targeted synthesis against gaps from pass 0. Pass 2: reconciliation / contradiction check across prior passes. rzWho is this person? What are their preferences, goals, and working style? Focus on facts that would help an AI assistant be immediately useful.zGiven what's been discussed in this session so far, what context about this user is most relevant to the current conversation? Prioritize active context over biographical facts.r1r@z Given this initial assessment: z What gaps remain in your understanding that would help going forward? Synthesize what you actually know about the user's current state and immediate needs, grounded in evidence from recent sessions.z Prior passes produced: Pass 1: z(empty)z Pass 2: z Do these assessments cohere? Reconcile any contradictions and produce a final, concise synthesis of what matters most for the current conversation.)r3)r8r`rergpriors r;_build_dialectic_promptz,HonchoMemoryProvider._build_dialectic_prompt8s q== 7 S   ]])6>M"%%BE4U444 003M0B0BQ0F0FM!,,I0003M0B0BQ0F0FM!,,I000 rgr)c:|r%t|dkrdSd|vrJd|vsDd|vs@tjd|tjs tjd|tjrdSt|d kS) zCheck if a dialectic pass returned enough signal to skip further passes. Heuristic: a response longer than 100 chars with some structure (section headers, bullets, or an ordered list) is considered sufficient. dF z##u•z^[*-] z ^\s*\d+\. Ti,)r3rresearch MULTILINE)r)s r;_signal_sufficientz'HonchoMemoryProvider._signal_sufficient_s V\\^^,,s225 6>> FNNyFBL99y ==46<<>>""S((rgTrrc|jr|jsdS|j }g}d}|ri|jrb|jr[ ||}n2#t $r%}td|Yd}~nd}~wwxYwt|j D]7}d|D}|dkr|p| d||} n|r>| |dr#td|j |n|s;td|j ||p| d||} n| |||} | || } td |j || ||j|j| | d } || pd9t!|D]} | r| r| cSdS) u[Execute up to dialecticDepth .chat() calls with conditional bail-out. Cold start (no base context): general user-oriented query. Warm session (base context exists): session-scoped query. Each pass is conditional — bails early if prior pass returned strong signal. Returns the best (usually last) result. r@z Honcho query rewriter failed: %sNc>g|]}|||Srj)r).0rs r; z=HonchoMemoryProvider._run_dialectic_depth..s*CCC11CCQCCCrgrrizCHoncho dialectic depth %d: pass %d skipped, prior signal sufficientuYHoncho dialectic depth %d: pass %d has no non-empty prior — falling back to base prompt)rz5Honcho dialectic depth %d: pass %d, level=%s, cold=%suser)r%r)rDrFrOrRrGrr7rrrangerVrkrrrddialectic_queryr4reversed) r8rrrgresultsrewritten_queryrirepromptlevelr)rs r;rz)HonchoMemoryProvider._run_dialectic_depthss} D$5 2..  F!< FAU F F"&"6"6u"="="C"C"E"E F F F ?EEEEEEEE Ft,-- ) )ACCCCCMAvv(D,H,H}g-- !T%<%<]2=N%O%OLL!f!%!6;;;E$ULL"?@D@UWXZZZ,0L0L='11FF"99!]GTTF,,Qe,<EJ,>I9~~** 5Hiify6HIII  +G--''CY_$$mmD))!881HCY_$$mmC((Y_$$dsdO**,,E!#$$..00I ' MM% E1 4 rgrDict[str, Any]c^|j}g}||dkr=tt|dd}tt|dd}n._syncBs ?-55d6GHH!001CYOO77E''6666!001H)TT<>>>>>>>> ?sBB C &CC @rTz honcho-syncr)rerNrrrEmessage_max_charsr rrMrrrIrr)r8rrrrrrrs` @@@r; sync_turnzHonchoMemoryProvider.sync_turn0s_    F   ' '0C0C0E0E ' F""$$   / / 1 1 1 F6:lMDL22 -l.@bAAGGII"23D3J"K"K"Q"Q"S"S ? ? ? ? ? ? ? ?   0!2!;!;!=!= 0   " "3 " / / /%,M    !!!!!rgactionrmetadataOptional[Dict[str, Any]]c4|dks|dkssdSjrdSjdkrsdSsdSfd}t j|dd}|dS) aiMirror built-in user profile writes as Honcho conclusions. ``metadata`` is accepted for compatibility with the write-origin work landed in main (commit 6a957a74); it's not yet threaded into the Honcho conclusion payload. Left as a follow-up so this PR stays focused on the 7-PR consolidation and its review follow-ups. addrwNrc jjdS#t$r&}td|Yd}~dSd}~wwxYw)NzHoncho memory mirror failed: %s)rDcreate_conclusionrFr7rr)rrr8s r;_writez4HonchoMemoryProvider.on_memory_write.._writelst C //0A7KKKKK C C C >BBBBBBBBB Cs % AAATzhoncho-memwriter)rerNrrrIrr)r8rrrrrts` ` r;on_memory_writez$HonchoMemoryProvider.on_memory_writeTs U??f..g. F    F   ' '0C0C0E0E ' F""$$   / / 1 1 1 F C C C C C C  F4>O P P P  rgrList[Dict[str, Any]]c|jrdS|jsdS|js"|jr|jrdS|jr4|jr|jd |jdS#t$r&}t d|Yd}~dSd}~wwxYw)z4Flush all pending messages to Honcho on session end.Ng$@rz#Honcho session-end flush failed: %s) rerDr_rbrrMr flush_allr7rr)r8rrs r;on_session_endz#HonchoMemoryProvider.on_session_endus    F}  F( T-> 4CTC]C]C_C_  F   1!2!;!;!=!= 1   " "4 " 0 0 0 C M # # % % % % % C C C LL> B B B B B B B B B Cs8B CB>>CcV|jrgS|jdkrgSttS)ziReturn tool schemas, respecting recall_mode. Context-only mode exposes no Honcho tools. r)rerNr+ALL_TOOL_SCHEMASrks r;get_tool_schemasz%HonchoMemoryProvider.get_tool_schemass6   I   ) )I$%%%rg tool_nameargsc  |jrtdS|jsR|jr(|jrtdS|stdS|jr|jstdS |dkr|dd}|d}|r[|j |j|| }|td Stj d t|d |dS|j |j| }|s'tj ||Stj d|iS|dkr|dpd}|stdSt!t#|ddd} |dd}|j|j|| |}|stj ddiStj d|iS|dkr|dpd}|stdS|dd}|d} |j|j|| |d}|j|_tj d|pdiS|dkrq|dd}|j|j| } | stj ddiSg} | d r| d!| d | d"r| d#| d"| dr| d$| d| d%rG| d%} d&d'| d(d D}| d)|tj dd*| pd+iS|d,kr|d-pd}|d.d}t3|d/}|dd}t3|}t3|}t5|||gd0krtd1S|dpd}|r|std2S|r:|j|j|pd |3}tj d4|iS|rQ|j|j|| }|rtj dd5|d6iStd7|d8S|j|j|| }|rtj dd9|d:|iStd;Std<|S#t<$r;}t> d=||td>|d?|cYd }~Sd }~wwxYw)@zFHandle a Honcho tool call, with lazy session init for tools-only mode.z$Honcho is not active (cron context).z8Honcho session is still initializing; try again shortly.z(Honcho session could not be initialized.z&Honcho is not active for this session.r rrwr)rNzFailed to update peer card.zPeer card updated (z facts).)r)rr)rrr@z!Missing required parameter: queryri i)rrzNo relevant context found.rr%F)r%rapply_injection_capzNo result from Honcho.r&zNo context available yet.rz ## Summary rz## Representation z## Card recent_messagesrnc3NK|] }d|dd|dddV!dS)z [rolez] rNrj)rums r; z8HonchoMemoryProvider.handle_tool_call..sX((@ai??1Y<+=??((((((rgz## Recent messages rzNo context available.r'r*r)r+r1z?Exactly one of conclusion, delete_id, or list must be provided.z&query is only valid when list is true.)rr conclusionsz Conclusion z deleted.zFailed to delete conclusion .zConclusion saved for z: zFailed to save conclusion.zUnknown tool: zHoncho tool %s failed: %szHoncho z failed: )!rer r_rbrrrDrFr set_peer_cardrzdumpsr3 get_peer_cardrrrrHsearch_contextryrQr[get_session_contextr4rrlsumlist_conclusionsdelete_conclusionrr7rerror)r8rrrr card_updater)rrrr%rrmsgsmsg_strr*r) list_mode has_delete_idhas_conclusionrokrs r;handle_tool_callz%HonchoMemoryProvider.handle_tool_callsb   FDEE E( N  ^T%6%?%?%A%A ^!"\]]]'')) N!"LMMM} HD$5 HFGG Gc A,,,xx//"hhv.. o!]889JK^b8ccF~)*GHHH:1\s6{{1\1\1\fl&m&mnnn}2243D42PPF:d&>&>t&D&DEEEz8T"2333o--'**0b7799K%&IJJJ TXXlC%@%@!A!A4HH xx//55%u$6P:x1M&NOOOz8V"4555000'**0b7799K%&IJJJxx//"&((+<"="=66%u$3(- 7-1,<)z8V-O7O"PQQQ...xx//m778IPT7UUO:x1L&MNNN779%%BLL!@I!@!@AAA77+,,PLL!Ns;K7L!N!NOOO776??<LL!:S[!:!:;;;77,--C01D"ii((!%bcc(((GLL!A!A!ABBBz8V[[-?-?-ZCZ"[\\\///!XXk228b??AA !XXlB77==??  &!1!122 xx// $Y !%j!1!1 ~yABBaGG%&ghhh'**0b7799PP%&NOOOD"&-"@"@)$T#A##K :}k&BCCC S889JI\`8aaBZ#z85W95W5W5W*XYYY%&QY&Q&Q&QRRR]44T5F Y]4^^`:x1]1]1]Q[1]1]&^___!">???:y::;; ; A A A LL4i C C C? ??A??@@ @ @ @ @ @ @ AsA%Y>4'Y>A Y>&Y>>Y>?Y>A2Y>AY>D!Y>?CY>;Y>;Y> ?Y> Y>?Y>Y>,Y>> [0Z>8[>[c:|j|jfD].}|r*|r|d/|jrT|jr |jr|jr/ |jdS#t$rYdSwxYwdSdS)Nrr) rLrMrrrDrbr_rr7)r8rs r;shutdownzHonchoMemoryProvider.shutdowns'):; $ $A $QZZ\\ $s### = $"3 8I8R8R8T8T ]a]v   '')))))        s-B BB)r.r/)N)r=r>)r.r5)r.rl)rr5rrr.r)rr5r.r)rr5r.r5)rrr.r)rrr.r5)rr5rr5r.r5)r/r5r.r5)rr5rr5r.r)r.rH)r.r)r@r5rr5r.r5)r@)r`rHrr5r.r5)r`rHrerfrgrlr.r5)r)r5r.rl)rr5rrlr.r5)r/r5r.rl)rrHrr5r.r)rr5rrHr.rf)rr5r.r)rr5rr5rr5r.r) rr5rr5rr5rrr.r)rrr.r)r.r)rr5rrr.r5r):__name__ __module__ __qualname____doc__r<rfpropertyrrurrrrrrrrrrrr*rrr?rB__annotations__rrXrYrFr,rJrrrr;rVr_rdrk staticmethodrrrrocompile IGNORECASEr classmethodrrrrrrrrrrrjrgr;r-r-sTRR    +#+#+#+#+#ZX===    ++++ B!B!B!B!H     GJ,=,=,=,=,=,=\S)S)S)S)j< H H H H"""":))))V9;qqqqqqf[[[[, " " " "?AL0L0L0L0L0L0j 8 8    ?L #  # !L" #    %%%%    &@@@@($%%%%N)))\)&MQ::::::~$ U     [ ''''***\*X7 7 7 7 rY[""""""""""""R.2 BCCCC & & & &qAqAqAqAf      rgr-r.rcXddlm}|t|dS)z,Register Honcho as a memory provider plugin.r)rewrite_memory_query)r=N)plugins.memory.query_rewriterregister_memory_providerr-)rrs r;registerrsEAAAAAA  ,@AAArgr)r __future__rrzloggingrorIrtypingrrrrragent.memory_managerr agent.memory_providerr tools.registryr getLoggerrrPROFILE_SCHEMA SEARCH_SCHEMAREASONING_SCHEMACONTEXT_SCHEMACONCLUDE_SCHEMArr-rrjrgr;rsk  #"""""   66666666666666111111000000%%%%%%  8 $ $  ,! C   (+h   B  (! S " V ! y   I! D  O!= !#,DCC3  8! CA$ $ JIO((!99x  +   C   2  "! Z ! ] " { ! _ ! V#  ,1#++\#M3C^Ude_____>___L)rg