yjGdZddlmZddlZddlZddlZddlmZddlm Z dZ dZ dZ d!d Z d"dZd#dZd$dZd%dZd&dZd'dZdd gZdS)(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)Optional positional Optional[str] file_pathreturnc \|r|S|r|dkrtjS t|dS#t $rDt d|d|d|d|d tj tjtYnPt$rD}t d |d |tj tjtYd }~nd }~wwxYwtj s"tj}|r|Sd S) 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. -zutf-8)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:"filezhermes send: cannot read z: N) sysstdinreadr read_textUnicodeDecodeErrorprintstderrexit _USAGE_EXITOSErrorisatty)rr excdatas 9/home/ragecks/.hermes/hermes-agent/hermes_cli/send_cmd.py_read_message_bodyr!)s"   9>>## # " ??,,g,>> >! " " " S SS7@ SS HQ SSGPSSSZ     H[ ! ! ! ! ! " " " @i@@3@@sz R R R R H[ ! ! ! ! ! ! ! ! " 9    y~~  K 4s"AA C) C)%:C$$C)arg_tocZ|r(|r|SdS)zAReturn a cleaned ``--to`` value, or ``None`` when nothing is set.N)strip)r"s r _resolve_targetr%Zs, &,,..||~~ 4 result_jsonstr json_modeboolquietintc |rtj|ni}n#tj$rd|d}YnwxYw|r$ttj|dn|rn|dr%td|dt jno|dr7|d }|rt|n3td n#ttj|d|drtS|d rtS|drtStS) 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.rrsuccessnotesentskipped) jsonloadsJSONDecodeErrorrdumpsgetrr _FAILURE_EXIT _SUCCESS_EXIT)r'r)r+payloadr2s r _emit_resultr=asW-8@$*[)))b  WWWB+VVW 1 dj+++,,,,  1 ;;w   1 4''"2443: F F F F F [[ # # 1;;v&&D d f  $*WQ/// 0 0 0{{7{{9{{9 s 22platform_filterc  ddlm}m}n<#t$r/}t d|t jtcYd}~Sd}~wwxYw |}n<#t$r/}t d|t jtcYd}~Sd}~wwxYwt| dpi} ddl m }|}| D];} t| d t| } | d vr%|| gz!_list_targets..s1KKKTQ!''))s:J:JAq:J:J:Jr&z,hermes send: no targets found for platform 'z'. Configured: z, z(none)r)r0defaultz@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@rA Exceptionrrrr:dictr9gateway.configrCget_connected_platformsgetattrr( setdefaultr$rJitemsjoinsortedr5r8r;)r>r)r@rArr/rBrC gw_configplat plat_namefilteredchannelschrRrUsuffixrNs @r _list_targetsris           EEECJWWWWn  EEECJWWWWSWW[))/R00I  666666'')) 5577 0 0Dgs4yy99I>>>  B / / / /  0       ##%%++--KKKKY__%6%6KKK ! JJJ#yy ):):;;GxJJZ     !   dj+y1!SIIIJJJ  PQQQ RSSS PQQQ  **955666I&&   Y' ooo  2 3 3 3  3 3B66&#&&DffTll=bffY&7&7=2G)0LW__%7%%%%"F 1y114111 2 2 2 2  sJ A$AAA A B $BB B 5A D D#"D#Nonec ddlm}n#t$rd}YnwxYw ddlm}|}n#t$rYdSwxYw|dz }|r|r |t |ddn#t$r ddl}ddl }| }| |j r|t|j d}|||d d n#t$rYnwxYwYnt$rYnwxYwddl}|d z }|sdS dd lm} | |}n#t$rYdSwxYw dd lm} | |}n#t$rYnwxYw ddlm} | t-|t.r|ni}n#t$rYnwxYwt-|t.sdS|D]O\} } t-| t t2t4t6fs.| |jvr8t | |j| <PdS)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.envTz utf-8-sig)overriderzlatin-1)streamrnz config.yaml)read_user_config_raw)_expand_env_vars) managed_scope)dotenvrlrYhermes_cli.configrmexistsr(rcodecsio read_bytes startswithBOM_UTF8lenStringIOdecodeosrprq hermes_clirrapply_managed_overlay isinstancerZr_r,floatr*environ)rlrmhomeenv_pathrvrwr/r~ config_pathrprqrrrNvals r _load_hermes_envrsS(&&&&&&&  555555   f}Hx((  KH { K K K K K!      ))++>>&/226c&/22445C 2;;szz)/D/D#E#EPTUUUUU        D  III&K      ;:::::"";//  666666s##       ,,,,,,11C9N9N2V##TVWW       c4 IIKK##S#S%677   "*   c(( 3 ##s - ;;A66 D%BDD% DD%DD% D%$D%E E('E(,E>> F  F 2G GGargsargparse.Namespacec ttt|ddrEt|dd}t|t|dd}tj|t t|dd}|s4t dtj tjttt|ddt|d d}|| s4t d tj tjtt|d d}|r|d | }ddl m }d||d}||}t|t|ddt|dd}tj|dS)z9Entry point wired into the top-level argparse dispatcher. list_targetsFmessageNr5)r)tozhermes 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)actiontargetrr+)r)r+)rr]rirrr%rrrr!r$lstriptools.send_message_toolrr=) rr> exit_coderrrr tool_argsresults r cmd_sendrHs t^U++"$ 488!/WT6SX=Y=YZZZ   WT466 7 7F    A        i&&fd##Ggmmoo  A    dIt,,G544'.."2"244:99999I  y ) )F$..dGU++I HYr&argparse.ArgumentParserc|ddddtj}|dddd d |d d d d|dddd d |dddd d |dddddd|dd ddd!"|d#ddd$"|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``. rzASend 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.)metavarrPrrrSz4Message text. If omitted, read from --file or stdin.)nargsrPrz-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--listr store_trueFzRList available targets. Optional positional filter: `hermes send --list telegram`.)destrrPrz-qz--quietz,Suppress stdout on success (exit code only).)rrPrz--jsonz6Emit raw JSON result instead of human-readable output.)func) add_parserargparseRawDescriptionHelpFormatter add_argument set_defaultsr) subparsersparsers r register_send_subparserrs " " P < I!<-#F2   #      C    (       E     a    ;   E  X&&& Mr&rr)rr r r r r )r"r r r )r'r(r)r*r+r*r r,)r>r r)r*r r,)r rj)rrr rj)r r)__doc__ __future__rrr5rpathlibrtypingrrr:r;r!r%r=rirrr__all__rIr&r rs&4#"""""    ....b****ZWWWWt]#]#]#]#@CCCCLddddN 0 1r&