`gjJAdZddlmZddlZddlZddlZddlmZddlm Z dZ dZ dZ ddZ dd Z dd Zdd Zdd Zdd ZddZddgZy)u CLI subcommand: ``hermes send`` — pipe text from shell scripts to any configured messaging platform (Telegram, Discord, Slack, Signal, SMS, etc.). This is a thin wrapper around ``tools.send_message_tool.send_message_tool`` that exposes its functionality as a standalone CLI entry point so ops scripts, cron jobs, CI hooks, and monitoring daemons can reuse the gateway's already-configured credentials without having to reimplement each platform's REST API client. Design notes: * No LLM, no agent loop — the subcommand just resolves arguments, reads the message body, calls the shared tool function, and prints/returns the result. It is intentionally fast, cheap, and side-effect-only. * For platforms that send via bot token (Telegram, Discord, Slack, Signal, SMS, WhatsApp-CloudAPI, …) no running gateway is required. The tool talks directly to each platform's REST endpoint. For platforms that rely on a persistent adapter connection (plugin platforms, Matrix in some modes, …) a live gateway is needed; the underlying tool surfaces that error to the caller. * Exit codes follow the classic Unix convention: 0 — delivery (or list) succeeded 1 — delivery failed at the platform level 2 — usage / argument / config error (argparse already uses 2) ) annotationsN)Path)Optionalc D|r|S|r?|dk(rtjjS t|j dStjjs"tjj}|r|Sy #t $rDt d|d|d|d|d tj tjtYt$rD}t d |d |tj tjtYd }~d }~wwxYw) u8Resolve the message body from (in order): 1. An explicit positional message argument. 2. ``--file PATH`` or ``--file -`` (where ``-`` means stdin). 3. Piped stdin when it is not attached to a TTY. Returns ``None`` when nothing is available — callers must treat that as a usage error. -utf-8encoding 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:"filezhermes send: cannot read z: N) sysstdinreadr read_textUnicodeDecodeErrorprintstderrexit _USAGE_EXITOSErrorisatty) positional file_pathexcdatas F/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/send_cmd.py_read_message_bodyr!)s   99>># # " ?,,g,> >* 99   yy~~ K 3" "  {+67@[AGGPkRFFO[PQSZZ  HH[ ! " -i[3%@szz R HH[ ! ! "sBA DD:DDcH|r |jr|jSy)zAReturn a cleaned ``--to`` value, or ``None`` when nothing is set.N)strip)arg_tos r _resolve_targetr%Zs &,,.||~ ct |rtj|ni}|r!ttj|dn|rn|j dr"td|dt jn\|j dr+|j d }|r t|n,td n ttj|d|j drtS|j d rtS|j drtStS#tj$r d|d}YwxYw) zPrint the tool result in the requested format and return the exit code. The underlying ``send_message_tool`` always returns a JSON string. We parse it, decide success/failure, and format accordingly. z#invalid JSON from send_message_tool)errorrawr)indentr(r rsuccessnotesentskipped) jsonloadsJSONDecodeErrorrdumpsgetrr _FAILURE_EXIT _SUCCESS_EXIT) result_json json_modequietpayloadr,s r _emit_resultr:asW-8$**[)b  djj+,  ;;w  M''"2!343:: F [[ #;;v&Dd f  $**WQ/ 0{{7{{9{{9 ;   WB+VWsDD76D7c  ddlm}m} |}t|jdxsi}|r|jj}|jD cic]\}} |j|k(s|| } }} | sCt d|d d jt|xsd t j tS| }|r-t tj d|id t" t$St'|j)s't dt dt dt$S|t |t$St|D]} || } t | d| s t d$| D]^} | jdd}| jdxs| jdxsd}|r ||k7rd|dnd}t d| d||`t t$S#t$r.}t d|t j tcYd}~Sd}~wwxYw#t$r.}t d|t j tcYd}~Sd}~wwxYwcc} }w)u4Print the channel directory (all configured targets across platforms). Uses ``load_directory()`` for structured JSON output and ``format_directory_for_display()`` for the human-readable rendering that the send_message tool itself shows to the model — keeps the two surfaces identical. r)format_directory_for_displayload_directoryz/hermes send: failed to load channel directory: rNz/hermes send: failed to read channel directory: platformsz,hermes send: no targets found for platform 'z'. Configured: z, z(none)r)r*defaultz@No messaging platforms configured or no channels discovered yet.zBSet one up with `hermes gateway setup`, or run the gateway once soz@channel discovery can populate ~/.hermes/channel_directory.json.:z (no channels discovered yet)name?idchat_idz []z )gateway.channel_directoryr<r= Exceptionrrrr4dictr3r#loweritemsjoinsortedr/r2strr5anyvalues)platform_filterr7r<r=rr)r>keykvfiltered plat_namechannelschrArDsuffixs r _list_targetsrZsR  SWW[)/R0I##%++-%.__%6KTQ!'')s:JAqDKK >>OP#yy ):;GxHJZZ  !   djj+y1!SIJ y! " PQ RS PQ *,-I&  Y'  1o 2 3  3B66&#&DffTl=bffY&7=2G)0W_s7)1%"F Byk4&1 2  3   k  ?uECJJW  ?uECJJWLsFG9H3#I-?I-9 H0#H+%H0+H03 I*<#I%I*%I*c ddlm} ddlm}|}|dz }|r%|j r |t |ddddl}|d z }|j sy ddl } t|d d 5}|j|xsi}ddd dd lm } | } ddl m} | jt!t"r|ni}t!t"sy|j%D]M\} } t!| t t&t(t*fs'| |j,vr6t | |j,| <Oy#t$rd}Y?wxYw#t$rYywxYw#t$r) |t |dd n#t$rYnwxYwYIt$rYTwxYw#t$rYywxYw#1swY%xYw#t$rYywxYw#t$rY4wxYw#t$rYwxYw)uPopulate ``os.environ`` from ``~/.hermes/.env`` AND bridge top-level ``config.yaml`` keys into the environment so the underlying gateway config loader sees platform credentials and home channel IDs. ``send_message_tool`` reads tokens and home-channel IDs via ``os.getenv(...)`` on each call. The gateway process does two things at startup that ``hermes send`` must replicate when invoked standalone: 1. ``load_dotenv(~/.hermes/.env)`` — brings bot tokens into the env. 2. Bridge top-level simple values from ``~/.hermes/config.yaml`` into ``os.environ`` (without overriding existing env vars). This is where ``TELEGRAM_HOME_CHANNEL`` and friends live when the user saved them via ``hermes config set``. See ``gateway/run.py`` for the canonical version of this bridge — we intentionally reimplement the minimum needed here so ``hermes send`` doesn't pull in the full gateway module just to resolve a home channel. r) load_dotenvN)get_hermes_homez.envTr )overrider zlatin-1z config.yamlrr )_expand_env_vars) managed_scope)dotenvr\rHhermes_cli.configr]existsrNrosyamlopen safe_loadr` hermes_cliraapply_managed_overlay isinstancerIrKintfloatboolenviron) r\r]homeenv_pathre config_pathrffhr)r`rarRvals r _load_hermes_envrus(&5 f}Hx(  H w G&K     +sW 5 +..$*C +  6s#  ,11C9N#TVW c4 IIK#S#S%67  "**  c( 3 #s   "  CMD9M       + +         sD9 E EF"F60F)F6G)G9 EE EE F$E98F9 FFFF FF F&%F&)F3.F66 GG GG G"!G"c tt|ddr:t|dd}t|t|dd}tj|t t|dd}|s4t dtj tjttt|ddt|d d}||js4t d tj tjtt|d d}|r|d |j}ddl m }d||d}||}t|t|ddt|dd}tj|y)z9Entry point wired into the top-level argparse dispatcher. list_targetsFmessageNr/)r7tozhermes 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 targetsrrznhermes send: no message provided. Pass text as a positional argument, use --file PATH, or pipe data via stdin.subjectz r)send_message_toolsend)actiontargetrxr8)r7r8)rugetattrrZrrr%rrrr!r#lstriptools.send_message_toolr{r:) argsrQ exit_coder~rxrzr{ tool_argsresults r cmd_sendr*sZ t^U+"$ 48!/WT6SX=YZ   WT46 7F   A     i&fd#Ggmmo  A dIt,GIT'.."2!34:I y )F$.dGU+I HHYr&c|jddddtj}|jdddd d |jd d d d|jdddd d |jdddd d |jdddddd|jdd ddd!"|jd#ddd$"|j t %|S)&zCreate the ``send`` subparser and return it. Kept as a standalone function so the top-level parser builder can wire it in next to the other messaging subcommands without cluttering ``_parser.py`` or ``main.py``. r|zASend a message to a configured platform (scripts, cron jobs, CI).u!Pipe text from any shell script to any messaging platform Hermes is already configured for. Reuses the gateway's platform credentials (~/.hermes/.env + ~/.hermes/config.yaml) — no LLM, no agent loop, no running gateway required for bot-token platforms like Telegram/Discord/Slack/Signal.aExamples: hermes send --to telegram "deploy finished" echo "RAM 92%" | hermes send --to telegram:-1001234567890 hermes send --to discord:#ops --file /tmp/report.md hermes send --to slack:#eng --subject "[CI]" --file build.log hermes send --to telegram "MEDIA:/tmp/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.)help descriptionepilogformatter_classz-tz--toTARGETNzDelivery 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.)metavarr?rrxrBz4Message text. If omitted, read from --file or stdin.)nargsr?rz-fz--filePATHzRead 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.z-sz --subjectLINEz6Prepend a subject/header line before the message body.z-lz--listrw store_trueFzRList available targets. Optional positional filter: `hermes send --list telegram`.)destr}r?rz-qz--quietz,Suppress stdout on success (exit code only).)r}r?rz--jsonz6Emit raw JSON result instead of human-readable output.)func) add_parserargparseRawDescriptionHelpFormatter add_argument set_defaultsr) subparsersparsers r register_send_subparserrpsJ " " P < I!<<-#F2   #    C    (     E     a    ;   E  X& Mr&rr)r Optional[str]rrreturnr)r$rrr)r6rNr7rnr8rnrrl)rQrr7rnrrl)rNone)rzargparse.Namespacerr)rzargparse.ArgumentParser)__doc__ __future__rrr/rpathlibrtypingrrr4r5r!r%r:rZrurr__all__r&r rs4#    ....b***  *  *ZBJT#nCLdN 0 1r&