+ lHjWa0t$Rt^RIHt^RIt^RIt^RIt^RIHtRt ]P!R]P!] 4,R,]P4t RRltR t]P !4t/tR ]R &R R ltRRltRtRRltRRltRRltRRltRORRlltRRltRRltRR ltROR!R"lltR#R$lt R%R&lt!R'R(lt"R)R*lt#R+R,lt$]%!0RPm4t&R-R.lt'R/R0lt(R1R2lt)R3R4lt*R5R6lt+R7R8lt,R9R:lt-R;R<lt.ROR=R>/R?R@lllt/RAt0RBt1RCRDlt2RORERFllt3RORGRHllt4RORIRJllt5RORKRLllt6RMRNlt7R#)QuBot Mode roster probe — canonical Bot Chat system prompt section. When any profile carries ``ui_meta['hermes-bots']`` in profile.yaml (Bot-Mode-managed), a bot's canonical "Bot Chat" session — ONLY that session (agent/system_prompt.py enforces the ``BOT_CHAT_TITLE`` gate) — gets a "Messaging other agents" section. Silent (``""``) when no profile is managed or on any error. Older desktop builds appended a frozen copy of the section to SOUL.md; ``strip_legacy_protocol`` drops it at load time so the live roster here is the only copy any session sees. Cached per (process, home) so compression rebuilds produce identical bytes. Toggle: ``agent.bot_mode_protocol``. Also hosts path/roster helpers shared by ``bot_mode_dm`` and ``bot_relay``. ) annotationsN)Pathz## Messaging other agentsz\n*z[ \t]*\n.*?(?=\n## |\Z)c V^8dQhRRRR/#)textstrreturn)formats"9/home/ubuntu/.hermes/hermes-agent/tools/bot_mode_probe.py __annotate__r seeeecr\V9d,\PRV4P4R,#T#)zRSOUL text without the plugin-era "## Messaging other agents" section (idempotent). )_PROTOCOL_HEADING_LEGACY_PROTOCOL_REsubstrip)rs&r strip_legacy_protocolrs2ARVZAZ  " "4 . 4 4 6 =d`ddr zBot Chatzdict[str, str]_cachedcV^8dQhRR/#rrrr )r s"r r r (s**s*r c.^RIHp\V!44#)zIAmbient process HERMES_HOME (env, else the platform default) as a string.get_process_hermes_home)hermes_constantsrrrs r _default_homer(s8 &( ))r c V^8dQhRRRR/#)rhomestr | os.PathLike | Nonerrr )r s"r r r .s8808T8r cV\V'd\V44#\44#N)rrrrs&r _resolve_homer#.s TD 77} 77r c8V!4# \dTu#i;i)uW``fn()`` or ``default`` on any exception — the probe must never crash a prompt build.) Exception)fndefaults&&r _swallowr(2s"t s  c V^8dQhRRRR/#)rrrrr )r s"r r r :sJJtJJr chVPPR8XdVPP#T#)z?Root ~/.hermes for both the default profile and named profiles.profilesparentnamer"s&r _hermes_rootr/:s(!%!1!1Z!?4;;  ITIr c V^8dQhRRRR/#rrrrrr )r s"r r r ?sFFFFr cTVPPR8Xd VP#R#)r+r'r,r"s&r _profile_namer3?s" ((J6499EIEr c V^8dQhRRRR/#)rr.rrr )r s"r r r Cs33#3#3r cVR8XdR#T#)r'hermesr )r.s&r _handler7Csy(82d2r c V^8dQhRRRR/#)rrootrrzlist[tuple[str, Path]]r )r s"r r r Hs''$'1'r c\aaa^RIHoHoVR, o\VVV3Rl.4pRV3.VO#)ud(name, dir) for the default profile + every live named profile, sorted. Same identity predicate as ``profile list``: infra dirs (``sessions/``, ``logs/``) and tombstones are not teammates (#99392), and neither is a marker-carrying dir whose name is not a profile id — a parked backup or staging dir must never become a ``message_agent`` target (#116905).) PROFILE_ID_REnamed_profile_is_liver+c4<SP4'd|\SP44Uu.uFWpVPR8wgKSP VP4'gK9S!V4'gKIVPV3NKY up#.#uupi)r')is_dirsortediterdirr.match)cr;r<r+s r _roster..Qs ??  H,,./ /vv" '4':':166'B G\]^G_ QVVQK/    sB B. B>Br')rr;r<r()r9namedr;r<r+s& @@@r _rosterrFHs< Fj H    E  & &&r c$V^8dQhRRRRRR/#)rpathrneedlez str | Noner dict | Noner )r s"r r r ]s!!!$! !k!r c,aaVV3Rlp\VR4#)zYAML mapping at ``path``, or None when missing / not a mapping / unreadable. ``needle``: cheap substring precheck that skips the YAML parse on the dominant (unmanaged) path.c<SP4'gR#SPRRR7pSe SV9dR#^RIpVPV4p\ V\ 4'dV#R#)Nz utf-8-sigreplace)encodingerrors)is_file read_text hermes_yaml safe_load isinstancedict)rawyamldatarIrHs r _load_read_yaml_dict.._load`s[||~~nnk)nD  &"3"~~c"!$--t747r Nr()rHrIrYsff r _read_yaml_dictr\]s 8 E4  r c V^8dQhRRRR/#)rrXrJrr )r s"r r r ns44[4[4r cV'dVPR4MRp\V\4'dVPR4MRp\V\4'dV#R#)zIThe ``ui_meta['hermes-bots']`` block of a parsed profile.yaml, if a dict.ui_metaN hermes-bots)getrTrU)rXr_botss& r _bots_metarcnsG%)dhhy!tG)3GT)B)B7;;} %DdD))43t3r c V^8dQhRRRR/#)r profile_dirrrboolr )r s"r r r us```$`r c>\\VR, R44RJ#) profile.yamlr`N)rcr\)res&r _is_bot_managedrius okN&BMR S[_ __r c V^8dQhRRRR/#)rr9rrrfr )r s"r r r ys>>t>>r c\;QJd%R\V44F 'gK R# R#!R\V444#)c3<"TFwr\V4xK R#5ir!ri).0_nds& r _any_managed..zs=}ebq!!}sTF)anyrF)r9s&r _any_managedrtys3 3=wt}=33=3=3=wt}= ==r c V^8dQhRRRR/#)rrrrrfr )r s"r r r }sTT6T$Tr c$a\V3RlR4#)uTrue when ANY profile on this install is Bot-Mode-managed. Never raises. The ``message_agent`` injection gate — deliberately independent of the protocol section's emptiness: a SOUL.md carrying the legacy protocol gets an empty section but still gets the tool.c><\\\S444#r!)rtr/r#r"sr rC%is_bot_mode_managed..sLmD6I)JKr Fr[r"sfr is_bot_mode_managedry}s KU SSr c V^8dQhRRRR/#)rpartsrrr )r s"r r r s//s/s/r c2RPRV44#)uH'title — description' from the non-empty parts (either may be absent).u — c38"TFq'gK VxK R#5ir!r rnps& r rq_role_line..s.5aA5  )join)r{s*r _role_liners <<.5. ..r c$V^8dQhRRRRRR/#)rhandlerr{rr )r s"r r r s!//C///r c$\RV R2.VO5!#)uCRoster line: '- `handle`' plus ' — part' for each non-empty part.z- ``)r)rr{s&*r _bulletrs F81o . ..r c V^8dQhRRRR/#)rrerrrr )r s"r r r str c.aRV3Rllp\VR4#)uvTeammate role line: Bot Mode title — profile description; tells a teammate WHO to message for a job. A friendly ``display_name`` (``hermes profile rename``) that differs from both the folder id and the title leads the line, so an untagged "talk to Scribe" maps to the folder handle without a disk search (#100671). Single-line, ≤160 chars, "" when nothing. Never raises.cV^8dQhRR/#rr )r s"r r #_profile_role..__annotate__s,,3,r c l<\SR, 4;'g/p\\V4;'g/PR4;'gR4P 4p\VPR4;'gR4P 4pVP 4SP P 4VP 439dRp\Y!\VPR4;'gR4P 44pRPVP44R,#)rhtitle display_name description :NN) r\rrcrarlowerr.rrsplit)rXrdisplaylineres r _role_profile_role.._roles{^;<BBZ%++009??R@FFHdhh~.44"5;;= ==?{//557G GG'#dhh}.E.K.K*L*R*R*TUxx %d++r rr[)rersf r _profile_rolers ,, E2 r c V^8dQhRRRR/#)rrerrtuple[str, str]r )r s"r r r s%%%/%r c.aRV3Rllp\VR4#)z[(Bot Mode title, profile.yaml ``display_name``) for a profile, "" when unset. Never raises.cV^8dQhRR/#)rrrr )r s"r r %_friendly_names..__annotate__s==?=r c*<\SR, 4;'g/p\\V4;'g/PR4;'gR4P 4\VPR4;'gR4P 43#)rhrrr)r\rrcrar)rXres r _read_friendly_names.._readsw{^;<BBZ%++009??R@FFHDHH^,22399;= =r )rrr[)rersf r _friendly_namesrs== E8 $$r c$V^8dQhRRRRRR/#)rr.rrerrr )r s"r r r s&WWW$W3Wr c`\R\V44R4;'g \V4#)uHuman-facing sender name, in the Desktop's ``botFriendlyNames`` order: Bot Mode title, then profile.yaml ``display_name`` (``hermes profile rename``), else the @handle — the renamed primary signs as ``Maia (@hermes)``, not ``hermes (@hermes)`` (#89720).c38"TFq'gK VxK R#5ir!r rnns& r rq _display_name..s>8qA8rN)nextrr7)r.res&&r _display_namers) >OK8> E V VQUVr c V^8dQhRRRR/#)rvaluerrset[str]r )r s"r r r s]]s]x]r c~\T;'gR4P4P4p\P!RRV4PR4p\P!RRV4pW#3Uu0uF;pV'gK \P !RV4'gK,V\ 9gK9VkK= up#uupi)uLower-cased mention forms of a friendly name, mirroring the Desktop's ``mentionNameForms``: slugified (``"Dr. Foo"`` → ``dr-foo``, what autocomplete inserts) and collapsed (``drfoo``). Reserved tokens and empty forms are dropped.rz [^a-z0-9_-]+-z[a-z0-9][a-z0-9_-]*)rrrrer fullmatch_RESERVED_ALIASES)rr.slug collapsedfs& r alias_formsrs u{{  ! ! # ) ) +D 66/3 - 3 3C 8DD1I( ](! \\"8!< ABJ[A[ A( ]] ]s6 B:B:$B:1B:c V^8dQhRRRR/#)rr9rrdict[str, set[str]]r )r s"r r r s   $  #6  r c.aRV3Rllp\V/4#)u``alias form → {folder ids}`` for every local profile's friendly names (profile.yaml ``display_name`` and the Bot Mode title). Folder ids themselves are not aliases: the caller matches those first, so a target that is an exact folder id always addresses that folder — a friendly name colliding with ANOTHER folder id never steals it. Ambiguity (one alias form shared by several profiles) surfaces as a multi-id set. Never raises.cV^8dQhRR/#)rrrr )r s"r r %local_alias_map..__annotate__s'r c</p\S4F]wr\4P!R\V44!F,pVP V\44P V4K. K_ V#)c38"TFp\V4xK R#5ir!)r)rnrs& r rq2local_alias_map.._build..s%[>Zk!nn>Zs)rFsetunionr setdefaultadd)aliasesr.reformr9s r _buildlocal_alias_map.._builds^')!( D %[ok>Z%[\""4/33D9]"/r r[)r9rsf r local_alias_maprs  FB r c V^8dQhRRRR/#)rr9rr list[str]r )r s"r r r s   ) r c.aRV3Rllp\V.4#)zRegistered peer gateway names (``hermes peer``) from config.yaml, read directly (no config-loader import; the section is absent on most installs). Never raises.cV^8dQhRR/#rrrr )r s"r r _peers..__annotate__sbbIbr c<\SR, R4;'g/PR4p\V\4'd\ RV44#.#)z config.yaml bot_peersc3z"TF1p\V4P4'gK$\V4xK3 R#5ir!)rrrs& r rq)_peers.._names..s$>es1v||~fc!ffes!;;)r\rarTrUr?)peersr9s r _names_peers.._namessK  !5{CIIrNN{[BLUTXBYBYv>e>>a_aar r[)r9rsf r _peersrsbb FB r c V^8dQhRRRR/#)rr9rrz list[dict]r )r s"r r r s*r c(aV3Rlp\V.4#)zADesktop relay roster (``tools/bot_relay.py``); [] on any failure.c <^RIHpV!S4#))read_remote_roster)tools.bot_relayr)rr9s r r_remote_roster.._reads6!$''r r[)r9rsf r _remote_rosterrs( E2 r c V^8dQhRRRR/#)rr9rrrr )r s"r r r sVVDVXVr c\V4UUu0uFwr\V4kK upp\\V44,#uuppi)zBare forms this gateway's own profiles answer to (handles + friendly-name slugs); a remote row must not be offered under any of them, since local resolution wins (``_resolve_local_name``).)rFr7rr)r9r._ds& r local_taken_formsrs5+2$- 8-hdGDM- 83t?T;U UU 8sAc V^8dQhRRRR/#rr9rrrr )r s"r r r sDSr c @\V4pV'gR#^RIHp\W!V\ V444UUu.uF?wr4\ RV 2RVR,;'g VR, 2VR,VR,4NKA pppR R P V4,#uuppi) zYAddendum for agents on OTHER connected machines; only when the relay roster is non-empty.r)remote_target_forms@zon connection_label connection_idrru Teammates on OTHER connected machines (reachable through the Desktop relay — message them with message_agent exactly like local teammates; replies arrive as completion notifications the same way, or via reply_delivery="poll" as below): r)rrrziprrr)r9rosterrrowrliness& r _remote_paragraphrs D !F 3V%8ARSWAX%YZ ZIC !D6 c#&8"9"Q"QS=Q!RSUXY`UacfgtcuvZ    ;>BYYu=M N  s B$Bc V^8dQhRRRR/#rr )r s"r r r s  $ 3 r ch\V4pV'gR#RPRV44pRV R2#)u9Addendum for cross-machine DMs — only when peers exist.rz, c3."TF pRV R2xK R#5i)rNr r~s& r rq"_peer_paragraph..s/A1#QxszO Teammates on OTHER machines: this install also has peer gateways registered (u). Message an agent on a peer the same way — message_agent with target "/" (or "" alone for the peer's main agent). Run `hermes peer list` for the live peer list.)rr)r9rlisteds& r _peer_paragraphrs> 4LE  YY// /F h r c V^8dQhRRRR/#r1r )r s"r r r s%%%#%r c \V4p\V4p\V4'gR#\V4UUu.uF.wr4W28wgK \ R\ V4 2\ V44NK0 pppRPV4;'gRp\ R\ V4 RV 2\V4,\V4,#uuppi)rrrz- (no teammates yet)uq This install runs Bot Mode: each Hermes profile is an agent teammate with one canonical "Bot Chat" conversation, and you have the `message_agent` tool to DM any of them. It is FIRE-AND-FORGET: it delivers your message with your attribution prefixed automatically and returns an acknowledgement immediately — it never returns the reply. Send it, finish your turn, and the reply arrives later as a background-process completion notification that wakes you; relay it to the user then, attributed to that agent — unless the ack returns reply_delivery="poll", in which case follow its process(action="wait") instruction before ending the turn. COMPOSE every message yourself — say what YOU need from that agent; never forward the user's words verbatim, and never reveal private 1:1 chat content. When the user says "ask " or "tell ...", that is a handoff: pick the right teammate from the roster below, message them with message_agent, and report back naming which agent replied. Message ONE clearly relevant teammate; don't fan out to several unless the user explicitly asked. When YOU receive a "Message from 🤖 (@):" message, a teammate agent is talking to you (not the user): address them, reply concisely via message_agent to their handle, and if it is a pure FYI with nothing to add, staying silent is fine — never ping-pong acknowledgements. You are `@z<`. Your teammates (live roster; roles from their profiles): ) r/r3rtrFrr7rrrrr)rr9mer.rp roster_lines roster_blocks& r _build_sectionr s  D t B   RYZ^R_nR_wtcgcmBGa /q1ABR_Ln99\*DD.DL  ,R[M" .1 2 D !3 "4 $ 5 os C%C force_refreshFc$V^8dQhRRRRRR/#)rrrrrfrrr )r s"r r r 4s$!!(@![_!lo!r ca\\V44o\;_uu_4V'g S\9d\ V3RlR4\S&\S,uuRRR4# +'giR#;i)u Cached probe entry point — one filesystem pass per (process, home). ``home`` should be the AGENT'S OWN resolved home (session-db derived), not ambient HERMES_HOME — build threads can lose the ContextVar override and the env var would then name the wrong profile.c,<\\S44#r!)rr)resolvedsr rC/get_bot_mode_protocol_section..;sX1Or rN)rr#_lockrr()rrrs&$@r get_bot_mode_protocol_sectionr4sJ=&'H  HG3 ()OQS TGH x  s 7A&& A7 zCapability epoch: z Capability epoch: ([0-9a-f]{12})c V^8dQhRRRR/#)r model_cfgobjectrrUr )r s"r r r Js4r c^RIHp\V\4'g/pVP R4pRp\V\ 4'dRpM\V\ 4'd V^8dTMRpM^\V\4'dIVP4P4'd%\ VP44pV^8dTMRpRV!VP R44RV/#)u``model.*`` overrides whose flip changes a rebuilt prompt, coerced like their consumers. ``supports_vision`` uses image routing's strict bool so YAML ``yes`` and ``true`` share one epoch. ``context_length`` is the cap ``build_system_prompt_parts`` uses to truncate context files. Routing keys (provider, default, base_url) are identity lines, not this surface — and no model id is special-cased. )_coerce_capability_boolcontext_lengthNsupports_vision) agent.image_routingrrTrUrarfintrrisdigit)rrraw_ctxctxparseds& r _model_prompt_capability_surfacerJs< i & & mm,-G C'4   GS ! ! 1g$ GS ! !gmmo&=&=&?&?W]]_% f29==AR3ST# r c V^8dQhRRRR/#rrrrrr )r s"r r r fsSS!9SSSr caaaa^RIo^RIo\V4o\S4p/o^RIHp^RIHp^RIH pH pV!\S44pV!4;'g/pV!V4\VPR4\4'dVPR4M/p\VPR4\4'dVPR4M/p \V 4SR&\!RVPR 4;'g.44SR &\VPR 4\4'dVPR 4M/p SP#VPR 4;'g/R \R7SR &\!V!V PR444SR&VPR4p \V \4'dSP#V R \R7MRSR&RVV3Rllp RV3Rllp \'V R4SR&\'V .4SR&\)V4p\!RV44SR&\!RV44SR&^SR&\+V4SR&\!R\-S444SR&\'VVV3R lR!4# T!T4i;i \$dLi;i \$d .SR&Lsi;i)"u12-hex digest of the capability surface for ``home``'s profile: disabled skills + enabled toolsets + MCP config, model capability overrides that change the prompt (``supports_vision``, ``context_length``), SOUL.md bytes, installed skill names, the Bot-Mode roster (+ roles), peers and the relay roster. Deliberately NOT cached — the point is detecting on-disk drift against a stored prompt's epoch. Never raises ("unavailable" on failure).N)parse_config_string_list)load_config_readonly)reset_hermes_home_overrideset_hermes_home_overrideskillsmodelmodel_capabilitiesc3T"TFp\V4P4xK R#5ir!)rr)rnss& r rq)capability_fingerprint..s+gEeqCFLLNNEes&(disableddisabled_skillsagentplatform_toolsetsT) sort_keysr'disabled_toolsets mcp_serversrmcpcV^8dQhRR/#rr )r s"r r ,capability_fingerprint..__annotate__sWW3Wr c<SR, pVP4'd.SPVP44P4#R#)zSOUL.mdr)rPsha256 read_bytes hexdigest)soulhashlibrs r _soul%capability_fingerprint.._souls<)#@D w~~doo/0::<VTVVr cV^8dQhRR/#rr )r s"r r r'sPPYPr c<aSR, oSP4'g.#^RIHp\V3RlV!SR444#)r)iter_skill_index_filesc3l<"TF)p\VPPS44xK+ R#5ir!)rr- relative_to)rnr skills_roots& r rq:capability_fingerprint.._skills..s0PN!!((..{;<<Ns14zSKILL.md)r>agent.skill_utilsr2r?)r2r5rs @r _skills'capability_fingerprint.._skillssK) !!##I =P5k:NPP Pr r,c3P"TFwr\V4'gKVxK R#5ir!rmrnrrps& r rqrs"N?1;M11s& &rc3F"TFwrV R\V4 2xK R#5i):N)rr;s& r rqrs#(VvtqA3a a0@/A)Bvs! roster_rolesprotocol_versionrc3^"TF#qR, RVR, RVR, 2xK% R#5i)rr=profilerNr )rnrs& r rqrs1&E]_  a) ~Qqzl;E]s+- remote_rosterc<SPSPSRR7PR44P4R,#)T)r"zutf-8:N N)r)dumpsencoder+)r-jsonsurfacesr rC(capability_fingerprint..s5tzz'TzBII'RS]]_`cdr unavailable)r-rHr#r/r7rhermes_cli.configrrrrrrTrarUrr?rFr%r(rFrr)rr9rrrrtokencfg skills_cfgr agent_cfgr%r.r8rr-rHrrIs& @@@@r capability_fingerprintrQfsT"H  !DG  ?:Y(X7 .&(..BC &u -*4SWWX5F*M*MSWWX&SU (237773CT(J(JCGGG$PR (H(S$%%++gZ^^T^E_EeEeceEe+g%g!" )337773CT(J(JCGGG$PR '+zz#'':M2N2T2TRT`dnqz'r#$'-.Fy}}UhGi.j'k#$ggm$ISTWY]I^I^C4EdfWWPP ub)GFO "-GH""N"NN#)(Vv(V"V #$G d|GG%&EST\E]& GO d q 'u -    > sP%J JJB$JA)J,A8J5J, JJ J)(J),J?>J?c V^8dQhRRRR/#rr )r s"r r r s<<-< ># >=U >ae >r ca^RIpVP!\T;'gR4pV'gR#\V3RlR4pVR8g;'dVP ^4V8g#)uTrue when ``stored_prompt`` is a Bot Chat prompt whose embedded epoch no longer matches disk. Unstamped prompts are never stale. Fails closed to "not stale" — a broken probe must not become a rebuild-every-turn cache burner.NrFc<\S4#r!)rQr"sr rC0stored_prompt_capability_stale..s 5d;r rK)rsearch_EPOCH_RE_TEXTr(group)rXrrmcurrents&f r stored_prompt_capability_stalerasS .-"5"526A ;]KG m # = = g(==r c$V^8dQhRRRRRR/#rWr )r s"r r r s(NNNC[NgkNr cRa\T;'gR9dR#\V3RlR4#)uZTrue when a Bot Chat session's stored prompt PREDATES the epoch mechanism (no stamp — including SOUL-era prompts whose frozen roster rode in from SOUL.md). The caller must only ask for sessions titled "Bot Chat"; we rebuild only when the probe would actually emit a section, and every rebuilt prompt is stamped so this fires once. Fails closed.rFc,<\\S44#r!)rfrr"sr rC6stored_bot_chat_prompt_needs_upgrade..sD!>t!DEr )rTr()rXrs&fr $stored_bot_chat_prompt_needs_upgraderfs& ,,"- Eu MMr cV^8dQhRR/#)rrNoner )r s"r r r sr c\;_uu_4\P4RRR4R# +'giR#;ir!)rrclearr r r _reset_cache_for_testsrks   s. ? r!>alluserr6r'everyone)8__conditional_annotations____doc__ __future__rosr threadingpathlibrrcompileescapeDOTALLrrBOT_CHAT_TITLELockrr__annotations__rr#r(r/r3r7rFr\rcrirtryrrrrr frozensetrrrrrrrrrrrTr]rrQrUrarfrk)ros@r r|sD # /jj"))4E*F!FIc!cegenenoe  * 8J F3 '*!"4`>T/ / $%WNO]   V & %P!bg!!$% 48Sl< >Nr