+ Wjm:Rt^RIHt^RIt^RIt^RIt^RIHt^RIH t ^t ^t ^t R.RRllt RRltR R ltR R ltR RltRRltRRltR/]!RRRR73R0]!RRRR73R1]!RRRR73R2]!RRRR73R3]!RRRRR R!73R4]!R"R#R$R%R&73R5]!R#R$R'R(73R6]!R#R$R)R(733tR*R+ltR,R-.tR#)7uCLI subcommand: ``hermes send`` — pipe text from shell scripts to any configured messaging platform (Telegram, Discord, Slack, Signal, SMS, etc.). ) annotationsN)Path)Optionalc$V^8dQhRRRRRR/#)msgstr exit_codez int | Nonereturnint)formats"GC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_cli\send_cmd.py __annotate__rs!szScx\V\PR7Ve\P!V4\#)z[Print ``msg`` to stderr; exit with ``exit_code`` when given, else return ``_FAILURE_EXIT``.file)printsysstderrexit _FAILURE_EXIT)rr s&&r_failrs( #CJJ  rc$V^8dQhRRRRRR/#)r positional Optional[str] file_pathr r )r s"rrrs&JJ=J]J}Jrc V'dV#V'dBVR8Xd\PP4#\V4P RR7#\PP4'g)\PP4;'gR #R # \ d!\ RT RT RT RT R2 \4Lx\d!p\ R T R T 2\4R p?LR p?ii;i) zResolve the message body: positional arg, then ``--file PATH`` / ``--file -`` (stdin), then piped stdin when not attached to a TTY. ``None`` when nothing is available (a usage error).-z utf-8-sig)encoding hermes send: z is not a text file. --file reads the message *body* (logs, reports, markdown). To send an image/document/audio file as a native attachment, reference it with MEDIA: in the message text instead: hermes send --to telegram "MEDIA:z6" hermes send --to telegram "optional caption MEDIA:zv" Add [[as_document]] to deliver an image as an uncompressed file: hermes send --to telegram "[[as_document]] MEDIA:"zhermes send: cannot read z: N) rstdinreadr read_textUnicodeDecodeErrorr _USAGE_EXITOSErrorisatty)rrexcs&& r_read_message_bodyr+s  99>># # O ?,,k,B B .1YY-=-=-?-?CIINN  $ $ITI"   {+67@[AGGPkRFFO[PQS  O -i[3%@+ N N Os#B""(C6 C6C6C11C6c V^8dQhRRRR/#)rmentionsz list[str]r r )r s"rrr7s\\\y\rcZ^RIHpVUu.uFq!!V4'dKVNK up#uupi)zBReturn mention values that cannot identify a WhatsApp participant.)normalize_whatsapp_mention_jid)gateway.whatsapp_identityr/)r-r/mentions& r_invalid_whatsapp_mentionsr27s(H#+ [83QRY3ZGG8 [[ [s((c(V^8dQhRRRRRRRR/#)r result_jsonr json_modeboolquietr r r )r s"rrr>s(cdsrcV'd\P!V4M/pV'd#\\P!V^R74MV'gVP R4'd'\RVR, 2\ PR7M]VP R4'd&\VP R4;'gR 4M!\\P!V^R74VP R4'g5VP R 4'gVP R4'd\#\# \Pd RRRT/pEL;i;i) zPrint the ``send_message_tool`` JSON result in the requested format; return the exit code. Unknown / unexpected shapes are failures so scripts notice.errorz#invalid JSON from send_message_toolraw)indentr!rsuccessnotesentskipped) jsonloadsJSONDecodeErrorrdumpsgetrr _SUCCESS_EXITr)r4r5r7payloads&$$ r _emit_resultrG>sW-8$**[)b djj+,  ;;w   M''"2!343:: F [[ # # '++f%// 0 $**WQ/ 0 ;;w  W[[%;%;w{{9?U?U    WA5+VWsD?D??EEc$V^8dQhRRRRRR/#)rplatform_filterrr5r6r r r )r s"rrrTs!<<=<<<rc ^RIHpHpT!4p\ TP R4;'g/4p^RIHpT!4P4F4p\TR\T44p T R!9gK"TPT .4K6 T'dTP4P4p TP4U U u/uFwrT P4T 8XgKYbK p p p T 'g4\ RT R R P!\#T44;'gR 24#T pT'd/\%\&P(!RT/^\R 74\*#T'g\%R 4\%R4^RIHpHpHpT!4T!4pp\%RTR, R24T!T4T!T48wd:TR, P54'd\%RT RTR, RT R24\*#Tf\%T!T44\*#\#T4Fp \%T R24Yi,'g\%R4K,Yi,FvpTP RR4pTP R4;'gTP R4;'gRp\%RT RT 2T'dTT8wdRT R 2MR,4Kx \%4K \*# \dp\ RT 24uRp?#Rp?ii;i \dp\ RT 24uRp?#Rp?ii;i \dELi;iuup p i)"zPrint the channel directory (all configured targets across platforms), reusing the ``format_directory_for_display`` rendering the send_message tool shows the model.)format_directory_for_displayload_directoryz/hermes send: failed to load channel directory: Nz/hermes send: failed to read channel directory: platforms)load_gateway_configvaluez,hermes send: no targets found for platform 'z'. Configured: , z(none))r;defaultz@No messaging platforms configured or no channels discovered yet.zBSet one up with `hermes gateway setup`, or run the gateway once so)get_default_hermes_rootget_hermes_homehermes_home_keyzchannel discovery can populate zchannel_directory.json.zA gateway running from z already has z'; this shell is scoped to profile home z, which has none.:z (no channels discovered yet)name?idchat_idz z [])local api_serverwebhook)gateway.channel_directoryrKrL ExceptionrdictrDgateway.configrNget_connected_platformsgetattrr setdefaultstriploweritemsjoinsortedrr@rCrEhermes_constantsrRrSrTexists)rIr5rKrLr*r:rMrNplat plat_namekeykvfilteredrRrSrThomerootchrWrZs&$ r _list_targetsrwTsNZNSWW[)//R0I 6')AACDgs4y9I BB$$Y3D ##%++-%.__%6K%6TQ!'')s:JDAD%6K>>OP#yy ):;GGxHJK K  djj+y1!SIJ  PQ RS^^$&(?(Ad /7O0O/PPQRS 4 OD$9 9tF^?^>f>f>h>h +D6tF^?^>_`::>?PR S *956I&   1o## 2 3 &&B66&#&DffTl==bffY&7==2G Byk4&)WX\_s7)1-=bde f' ' o NFseLMMN NFseLMMN    Ls]K#L 8L/4L/M!M# L. L;LL L, L'!L,'L,/ L>=L>cV^8dQhRR/#)rr Noner )r s"rrrs,#,#$,#rc^RIp^RIHpV!4p^RIHpHpT!4'dT!4MRp\T\4'dTpM/.env`` AND bridge top-level ``config.yaml`` keys into it so the gateway config loader sees platform credentials and home channels. The target is ``os.environ`` for the standalone CLI. Inside a multi-profile host (dashboard console running ``send`` for profile B under its secret scope) it is the installed scope mapping: writing B's ``.env`` into the shared process env would hand every other profile's later reads B's tokens (``gateway.config._getenv`` reads the scope first, so the loader sees the same values either way). The installed scope is already ``build_profile_secret_scope``'s composition — user ``.env``, then the profile's external secret sources over it — so it is authoritative as-is; replaying raw ``.env`` over it would let a stale user value beat the secret-manager one for this request. NrS)current_secret_scopeis_multiplex_active.env)_load_dotenv_with_fallbackT)override config.yaml)load_user_config_effective)oshermes_cli.configrSraagent.secret_scoper|r} isinstancerbenvironrmhermes_cli.env_loaderrhermes_cli.config_effectiverrirr floatr6)rrSrtr|r}scopetargetenv_pathr config_pathrcfgrpvals r_load_hermes_envrs5 M&9&;&; "E%&= ??   L*8dC &K     J(5IIK cCeT2 3 38Ic(FK 5    s5 D6D (D1 DD D.-D.1 E?Ec V^8dQhRRRR/#)rargszargparse.Namespacer ryr )r s"rrrs.p.p%.p$.prc \4\VRR4'd:\\VRR4\VRR4R7p\P!V4\VRR4;'gRP 4pV'g\ R \4\\VR R4;'g.4pV'dKVPR ^4^,P 4P4R 8wd\ R \4\V4pV'd$\ RRPV4 R2\4\\VRR4\VRR44pVeVP 4'g\ R\4\VRR4pV'dV RVP4 2p^RIHpRRRVRV/pV'dW8R &V!V4p \P!\#V \VRR4\VRR4R74R#)z9Entry point wired into the top-level argparse dispatcher. list_targetsFmessageNr@)r5tor[zhermes send: --to PLATFORM[:channel[:thread]] is required Examples: hermes send --to telegram "hello" hermes send --to discord:#ops --file report.md hermes send --list # list available targetsr-rVwhatsappz>hermes send: --mention is only supported for WhatsApp targets.z)hermes send: invalid --mention value(s): rPz(. Use a phone number or participant JID.rznhermes send: no message provided. Pass text as a positional argument, use --file PATH, or pipe data via stdin.subjectz )send_message_toolactionsendrr7)r5r7)rrerwrrrgrr'listsplitrhr2rjr+lstriptools.send_message_toolrrG) rr rr-invalid_mentionsrrr tool_argsresults & rcmd_sendrst^U++!'$ 4"@GTXZ`bgLhi  dD$'--2 4 4 6F   A   GD*d399r:HFLLa(+11399;zI NP[\1(; 7yy)*++S U  !y$!?vW[A\]Ggmmoo  A   dIt,GIT'.."2!34:68VYHI (* y )FHH\&GD&%,HPWX\^eglPm norTARGETzDelivery target. Format: 'platform' (home channel), 'platform:chat_id', 'platform:chat_id:thread_id', or 'platform:#channel-name'. Examples: telegram, telegram:-1001234567890:17585, discord:#ops, slack:C0123ABCD, signal:+15551234567.)metavarrQhelprXz4Message text. If omitted, read from --file or stdin.)nargsrQrPATHzRead message body from PATH (text only). Use '-' to force stdin. To send an image/document as an attachment, use MEDIA: in the message text instead.LINEz6Prepend a subject/header line before the message body.r-append PHONE_OR_JIDzWhatsApp only: add a native participant mention. Repeat for multiple recipients; bare phone numbers are normalized to JIDs. Include each matching @ near the start of the message text.)destrrQrrr store_trueFzRList available targets. Optional positional filter: `hermes send --list telegram`.)rrrQrz,Suppress stdout on success (exit code only).)rrQrz6Emit raw JSON result instead of human-readable output.cV^8dQhRR/#)rr zargparse.ArgumentParserr )r s"rrr s  +B rc ^RIHpV!4pVPRRRVR, RVR, R2R \PR 7p\ FwrEVP !V/VBK VP\R 7V#) z,Create the ``send`` subparser and return it.r{rzASend a message to a configured platform (scripts, cron jobs, CI).zPipe text from any shell script to any messaging platform Hermes is already configured for. Reuses the gateway's platform credentials (r~z + rut) — no LLM, no agent loop, no running gateway required for bot-token platforms like Telegram/Discord/Slack/Signal.a1Examples: hermes send --to telegram "deploy finished" echo "RAM 92%" | hermes send --to telegram:-1001234567890 hermes send --to discord:#ops --file ./report.md hermes send --to slack:#eng --subject "[CI]" --file build.log hermes send --to whatsapp:GROUP@g.us --mention 15551234567 "@15551234567 hello" hermes send --to telegram "MEDIA:./chart.png" # send a media attachment hermes send --list # all platforms hermes send --list telegram # filter by platform Exit codes: 0 ok, 1 delivery/backend error, 2 usage error.)r descriptionepilogformatter_class)func) rlrS add_parserargparseRawDescriptionHelpFormatter_SEND_ARGUMENTS add_argument set_defaultsr) subparsersrS hermes_homeparserflagskwargss& rregister_send_subparserr s0!#K  " " P '&01]*+,< < I!<<1#>F2) U-f-) X& Mrrr)N)z-tz--to)r)z-fz--file)z-sz --subject)z --mention)z-lz--list)z-qz--quiet)z--json)__doc__ __future__rrr@rpathlibrtypingrr'rrErr+r2rGrwrrrbrr__all__r rrrs2#    J8\,<~,#^.pfT(D ]_` 4c46lmntFD dfg$vtBz{|Tz(DR` y{|t e!uwxL%Ftuv$lE@xyz#* F 0 1r