PL j<dZddlmZddlZddlZddlZddlmZddlm 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 t f$rD}td|d|tjtj tYd}~nd}~wwxYwtj s"tj}|r|SdS)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-8encodingzhermes send: cannot read z: fileN) sysstdinreadr read_textOSErrorUnicodeDecodeErrorprintstderrexit _USAGE_EXITisatty)rr excdatas 7/home/kuhnn/.hermes/hermes-agent/hermes_cli/send_cmd.py_read_message_bodyr!)s"   9>>## # " ??,,g,>> >+, " " " @i@@3@@sz R R R R H[ ! ! ! ! ! ! ! ! " 9    y~~  K 4s"AB$ :BB$arg_tocZ|r(|r|SdS)zAReturn a cleaned ``--to`` value, or ``None`` when nothing is set.N)strip)r"s r _resolve_targetr%Ms, &,,..||~~ 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.z hermes send: rsuccessnotesentskipped) jsonloadsJSONDecodeErrorrdumpsgetrr _FAILURE_EXIT _SUCCESS_EXIT)r'r)r+payloadr2s r _emit_resultr=TsW-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 h ddlm}m}n<#t$r/}t d|t jtcYd}~Sd}~wwxYw |}n<#t$r/}t d|t jtcYd}~Sd}~wwxYwt| dpi}|r| fd| D}|sJt d |d d t|pd t jtS|}|r2t tjd|id t"t$St'|s4t dt dt dt$S|t |t$St|D]}||} t |d| st d.| D]k} | dd} | dp| dpd} | r | | krd| dnd} t d|d| | lt t$S)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: platformscLi|] \}}|k||!S)lower).0kvkeys r z!_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:dictr9r$rEitemsjoinsortedr5r8r(r;anyvalues)r>r)r@rArr/rBfiltered plat_namechannelschrMrPsuffixrIs @r _list_targetsr`s\           EEECJWWWWn  EEECJWWWWSWW[))/R00I ##%%++--KKKKY__%6%6KKK ! JJJ#yy ):):;;GxJJZ     !   dj+y1!SIIIJJJ y!! " " PQQQ RSSS PQQQ **,,---I&&   Y' ooo  2 3 3 3  3 3B66&#&&DffTll=bffY&7&7=2G)0LW__%7%%%%"F 1y114111 2 2 2 2  s7 A$AAA A B $BB B Nonec ddlm}n#t$rd}YnwxYw ddlm}|}n#t$rYdSwxYw|dz }|ry|re |t |ddnH#t$r0 |t |dd n#t$rYnwxYwYnt$rYnwxYwddl}|d z }|sdS ddl }n#t$rYdSwxYw t|d d 5}| |pi}dddn #1swxYwYn#t$rYdSwxYw dd lm } | |}n#t$rYnwxYwt|tsdS|D]O\} } t| t t t"t$fs.| |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.envTr)overriderzlatin-1z config.yamlrr)_expand_env_vars)dotenvrcrThermes_cli.configrdexistsr(rosyamlopen safe_loadrg isinstancerUrVr,floatr*environ) rcrdhomeenv_pathrk config_pathrlfhr/rgrIvals r _load_hermes_envrws(&&&&&&&  555555   f}H x((   KH w G G G G G!     CMMD9MMMMM        D  III&K       +sW 5 5 5 +..$$*C + + + + + + + + + + + + + + +  666666s##       c4 IIKK##S#S%677   "*   c(( 3 ##s - ;;A66 B;BB; B*'B;)B**B;/ B;:B;C## C10C15D7D+ D7+D//D72D/3D77 EE E E('E(argsargparse.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)actiontargetr|r+)r)r+)rwgetattrr`rrr%rrrr!r$lstriptools.send_message_toolrr=) rxr> exit_coderr|r~r tool_argsresults r cmd_sendrs 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 --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.)metavarrKrr|rNz4Message text. If omitted, read from --file or stdin.)nargsrKrz-fz--filePATHz4Read message body from PATH. Use '-' to force stdin.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`.)destrrKrz-qz--quietz,Suppress stdout on success (exit code only).)rrKrz--jsonz6Emit raw JSON result instead of human-readable output.)func) add_parserargparseRawDescriptionHelpFormatter add_argument set_defaultsr) subparsersparsers r register_send_subparserr[s " " P < I!<+#F0   #      C    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 ra)rxryr ra)r r)__doc__ __future__rrr5rpathlibrtypingrrr:r;r!r%r=r`rwrr__all__rDr&r rs&4#"""""    !!!!H****ZBBBBJL#L#L#L#^CCCCL____D 0 1r&