߲jv^dZddlZddlZddlmZmZddlmZmZmZm Z m Z ddl m Z ddl Z ejdZdZde eeeefdfd efd Z d1de eeeefdfd e eeeffd Zd eeefd e ed e efdZd eeefd e ed eefdZde ede ede ed efdZd eeefd efdZded eefdZd2de ede ed eefdZddde eded e efdZded e efdZd e ed e efd!Zd e ed e efd"Zd#e ed$e ed e efd%Z d&e ed e efd'Z!d(e e eeefd)ed e eefd*Z"d+eed e efd,Z#d-Z$d eeefd eeeffd.Z%d3d/ed e&fd0Z'y)4zgCron job argument normalization, validation and result shaping (re-exported by tools/cronjob_tools.py).N)datetime timedelta)AnyDictListOptionalUnion)effective_job_stateztools.cronjob_tools<schedulereturnch|syt|tr|}n2d}tjt5ddlm}||}dddt|tr|jddk7ry|jd}|sy tjt|jdd }tj}|j|j|j }||z }t!d|cxkxrt!t" kScS#1swYxYw#t$rYywxYw) a True when the job's first fire is close enough that the creating conversation is still alive when it happens. Only near one-shots qualify; recurring jobs and one-shots beyond the horizon outlive the conversation, which is what the synthetic-drop rule protects.FNr)parse_schedulekindoncerun_atZz+00:00)tzinfo)minutes) isinstancedict contextlibsuppress Exception cron.jobsrgetr fromisoformatstrreplace ValueError hermes_timenowrr_THREAD_HORIZON_MINUTES)r parsedrrfire_atr"deltas ;/home/ubuntu/.hermes/hermes-agent/tools/cronjob_job_args.py!_first_fire_within_thread_horizonr(s (D!   + . 0#H-F . fd #vzz&'9V'C ZZ !F ((V)<)N  $ % :;CtI_/$%@AIT #i.C O;0: 6  < !  9  8$$%?@HDW`"#;<D$$=>F$ job user_delivercl|xsdjjdk(ry ddlm}||}|rSddlm}m}|Dcgc]}|jddk(s|}}|r$|d r|sd |dd d |dd dSy ycc}w#t$r|jdrYyY ywxYw)uNotice when a created job won't deliver anywhere: CLI/TUI sessions have no capturable origin, so deliver='origin' (or omitted) saves output but never delivers it. None when the user explicitly asked for ``local`` or the job resolves to a real target. TUI/CLI sessions cannot be captured as a cron ``origin`` (no ``HERMES_SESSION_PLATFORM``/``CHAT_ID`` is set for them), so a ``deliver="origin"`` request — or an omitted ``deliver`` that defaults to origin-or-local — produces a job that runs and saves output to ``last_output`` but is never delivered back into the session. This is by design (there is no live-delivery channel for local sessions), but silently dropping the user's "tell me when it runs" intent is the trap reported in 51568. Surface it at create time so the agent can relay it instead of promising a delivery that never happens. See #51568. localNr)_resolve_delivery_targetsr*_resolved_fromorigin_fallbackr-zpNote: this stateless HTTP API session cannot receive cron delivery, so this job will report to the home channel r5:r6z instead of back here.originuhThis is a local-only cron job: its output is saved (view it with cronjob(action='list')) but will NOT be delivered back into this session — CLI/TUI and stateless HTTP API sessions have no live-delivery channel. To be notified when it runs, recreate or update the job with deliver set to a gateway-connected platform, e.g. deliver='telegram' or deliver='all'.) striplowercron.schedulerrHr;r+r,rr)rCrDrHtargetsr+r,tfallbacks r'_local_delivery_noticerSns !!#))+w6<+C0  Z#*[aaee4D.EIZ.Z[H[O,EFOgOi??G{:?V>WWX#A;y122HJK  RS\  778   RSs)BBB"'BBB32B3cg}|jds|jdr|jd|jdr|jd|xsdjj}|rd|j dvr|jd |j d r|jd |j dD]x}|jj d }t |d k(s1|ddvs9|ds?|dj drT|jd|jd|S|S)zuMode guidance echoed once in the create/update response (not in the schema, which is paid for on every API call).monitor_script monitor_urlusMonitor mode: the source runs first each tick and its output is hashed as exact bytes — unchanged output suppresses the agent run (silent no_change tick), changed output injects a MONITOR CHANGE DETECTED diff into the prompt. The first tick always runs as baseline. The source must emit STABLE output (no timestamps, no random ordering) or every tick will look changed.no_agentuno_agent mode: stdout is delivered verbatim; EMPTY stdout sends nothing at all (watchdog pattern — script should stay quiet when there is nothing to report). Non-zero exit or timeout sends an error alert. prompt/skills are ignored.rFall,udeliver='all' resolves at fire time and never includes bot-chat targets — channels connected later are picked up automatically.z bot-chat:zJTargeting another profile's Bot Chat costs that bot an agent turn per run.rKr)zbot-chatsms#zdeliver target 'uk' has no :thread_id segment — on thread/topic platforms the delivery lands in the main chat, not a topic.)rappendrMrNsplit startswithlen)rCrDnotes_delivertargetpartss r'_mode_guidance_notesrfsGE ww CGGM$:  @ A wwz  6 7 "))+113H HNN3' ' LL! "   { + LLe fnnS) FLLN((-EE a!H$77!Ha++C0 &v||~&67223 L  LrBmonitorrUrVc|||fS|j}|sy|jjdrd|fS|dfS)aResolve the model-facing ``monitor`` field into the stored ``(monitor_script, monitor_url)`` pair. http(s):// is a URL, anything else a script path (a legal script path never starts with a URL scheme). None = unchanged, '' = clear; setting one source clears the other so switching transports never trips mutual exclusion; an explicit ``monitor`` wins over the legacy alias fields.)rFrF)zhttp://zhttps://rF)rMrNr`)rgrUrVvalues r'_split_monitor_argrjsN{** MMOE  {{} 785y "9rBc|jdxsi}|jd|jdd}}|y|dk(r |dk(rdSdS|r|d |S|d S) Nrepeattimes completedrforeverr\rz1/1/z times)r)rCreprmrns r'_repeat_displayrrsq ''(  !rCwww'a)@9E } z"av2U2%.i[% !DugV4DDrBitemscn|gSt|tr|g}d|DDcgc]}|s| c}Scc}w)zMStripped, non-empty ``str(item)`` values from a str-or-iterable (order kept).c3NK|]}t|jywN)rrM).0is r' z"_clean_str_list..s61A 6s#%)rr)rsss r'_clean_str_listr{s8 } %66 .s-LTdjbj-Ls)rrlistrfromkeysr{)r|r}s r'_canonical_skillsrsB ~!%r FC   o-LV-LLM NNrBFstrip_trailing_slashrircl|yt|j}|r|jd}|xsdS)Nrp)rrMrstrip)rirtexts r'_normalize_optional_job_valuers7 } u:   D{{3 <4rBc|yt|ttfrdjt |xsdSt |j xsdS)zCanonical string form of ``deliver``; None for None/empty. MCP clients may pass a list (``["telegram"]``) which the scheduler's ``str(deliver).split(",")`` would mangle.NrY)rrtuplejoinr{rrM)ris r'_normalize_deliver_paramrsK }%$'xx./747 u:    %%rBdeliverc|sy ddlm}ddlm}m}t |jdD]4}||j}|s ||}||r.d|d cSy#t $rYywxYw#t $r d|dcYcSwxYw) aValidate ``bot-chat[:]`` deliver elements at create time: Bot Chat delivery is machine-local, so the profile must exist where the scheduler fires (Desktop rosters may show same-named profiles from other machines). Returns an error string or None.Nr)parse_bot_chat_deliver_token)normalize_profile_nameprofile_existsrYzinvalid bot-chat profile name ''zbot-chat delivery profile 'u' not found on this gateway's machine. Bot Chat delivery is machine-local — use a profile that exists here (hermes profile list), or omit the name (deliver='bot-chat') for the job's own profile.) cron.scheduler_deliveryrhermes_cli.profilesrrrrr_rM)rrrrpart profile_argcanons r'_validate_bot_chat_deliverrs HNG ""3' H24::<@   D*;7Ee$-k];GG H H !  D4[MC C Ds#A% A4% A10A14BBcVddlmddlm}|dds|Sdtffd }||St t |j d Dcgc]}|jd k(r|n| }}d jtj|xsdScc}w) aResolve ``origin`` to a concrete target for creates made FROM a cron run (the creating session is ephemeral, so by fire time there is no origin). Non-cron sessions: unchanged. Cron sessions: ``origin`` (or omitted) becomes the creating run's ``platform:chat_id[:thread]`` from HERMES_CRON_AUTO_DELIVER_*, or ``local`` when it has no concrete target; other elements pass through. Otherwise the scheduler would guess a home channel.r)r,)is_truthy_valueHERMES_CRON_SESSIONrFr cddj}ddj}|r|syddj}|r |d|d|S|d|S)N!HERMES_CRON_AUTO_DELIVER_PLATFORMrF HERMES_CRON_AUTO_DELIVER_CHAT_IDrG"HERMES_CRON_AUTO_DELIVER_THREAD_IDrK)rM)r5r6r8r,s r'_creator_targetz6_resolve_cron_context_deliver.._creator_target(sy"#FKQQS!"DbIOOQw#$H"MSSU 6?(1WIQyk2\zQRSZR[E\\rBNrYrL) r;r,utilsrrr{r_rNrrr)rrrpresolvedr,s @r'_resolve_cron_context_deliverrs 8% ?+@"E F]S]  KZ[^_f[g[m[mnq[rKstaQWWY(%:!AtHt 88DMM(+ , 44us#B&providerbase_urlcRt|d}|syt|}|s y ddlm}m}m}ddlm}ddlm}m } |jd k(ry||rE ||} | r| | xsijd d nd } | r ||| ryd|d|d| xsddS ||} t| tr|j| nd} | | r t| dd nd }|r |||ryd|d|dS#t$r d |d cYSwxYw#t$rd} YwxYw#t$r|} YwxYw)aeReject pairing a named provider's stored credential with an off-host base_url (a prompt-injected job could exfil the key). Allowed: no override; bare 'custom' (pure BYOK, key derived from the base_url); an override whose host matches the named provider's own endpoint. Everything else fails closed. Returns an error string if blocked, else None.TrNzwbase_url override requires an explicit provider. Set provider to a configured custom provider to use a custom endpoint.r)has_named_custom_providerresolve_requested_provider_get_named_custom_provider)PROVIDER_REGISTRY)base_url_host_matchesbase_url_hostnamez2Unable to validate base_url override for provider z ; refused.customrrFz base_url z is not allowed for provider z_. A named custom provider's stored credential may only be sent to its own configured endpoint (unknownz).inference_base_urlz. A named provider's stored credential may only be sent to its own endpoint; use a configured custom provider (provider="custom") for a custom base_url.)rhermes_cli.runtime_providerrrrhermes_cli.authrrrrrrNrrrgetattr)rrbuprovrrrrrrcpcfg_hostrpconfig known_hosts r'_validate_cron_base_urlr7s 'xd KB  ( 2D  C DW ( ( 6B zz|x & +D1BIK$bhB^^J%CDPR -b(;v:4(C$$,$9 #:" > ?-d32.s511779&5srN)r{anyr^rN)rrrefshas_selfrs r'_apply_continuityrsc < (D555H( F H7a1779#677 <48s A!A!rcddlm}|D]D}t|tr"|j j dk(r5||r>d|dcSy)uError string if any non-"self" ref names a missing job ("self" resolves to the job's own id at run time, so it can't be checked — the job doesn't exist yet at create).r)get_jobrzcontext_from job 'z>' not found. Use cronjob(action='list') to see available jobs.N)rrrrrMrN)r_get_jobref_ids r'_validate_context_from_refsrsa.E fc "v||~';';'='G $VH-DD E E rB)rreasoning_effortrUrV monitor_staterWenabled_toolsetsworkdirc  ddlm}tjdxsd}t jdjd}tjdxsd}tjd xs|dd xs|r|dndxs|xsd }id |d |d|r|dndd|d t |dkDr|dddzn|djddjddt tjdxsdjdjddjdxsddtdjdddjddjddjddjddjdjdjd r|d d!d!"njd jd#d!tjd$jd%d&}tD]#}j|s|d'k(rd!n|||<%jd(xsg}t|tr|g}fd) t fd*|Drd!|d+<|D cgc] }  | r | } } | r| |d(<tjd,t rd,|d,<|Scc} w)-Nr)redact_sensitive_textpromptrFr|r}idrname2zcron jobjob_idprompt_previewdz...modelrpinnedrr schedule_display?rlrrG next_run_at last_run_at last_statuslast_delivery_errorlast_delivery_unverifiedlast_fire_error last_errorT)forceredact_url_credentialsenabled paused_at paused_reason)rrrstaterrrWrct|jjdk(xs|jdk(S)Nrr)rrMrNr)rrCs r'z_format_job..s1A ,,.&8NA.s +!71: +srattach_to_session) agent.redactrrrrraboolrMrrr _FORMAT_JOB_OPTIONAL_KEYSrr) rCrrr}rrresultkey stored_refsr external_refsrs ` @r' _format_jobrs@2 "(b )F swww/1B CF +) ,F swwvf&"+fv&)2fRXf\f gD& f$ &  #f+2C&#,.  !  CGGJ' $s3777+1r288:; CGGJ' CGG./63 /#& 3779g. sww}- sww}- sww}-!" sww'<=#$ #CGG,F$G%&77#45WW\ ",  T$ (+ (=779d+$S)WW[)17F:)B 773<"%"3$SF3KB''.)/RK+s#"m NG +{ ++#| +>171:Q>M>!.~#''-.5&)*=&>"# M ?s ? L Lpluralc| ddlm}|}|dur|rdnd}dd|d d Sd|diSd iS#t$rddicYSwxYw) a``gateway_running``/``warning`` payload via the shared CLI helper so CLI and tool agree on "scheduler active". False -> warning (no gateway process), None -> probe failed. Thin adapter over the shared CLI helper ``hermes_cli.cron._builtin_gateway_liveness`` (#87033) so the CLI and this tool can never disagree about what "scheduler active" means. ``plural`` rewords the warning for multi-job results (the ``list`` action). r)_builtin_gateway_livenessgateway_runningNFzthese jobs are savedzthis job is savedu&The Hermes gateway is not running — z but will NOT fire until the gateway is started (hermes gateway install / hermes gateway start). Tell the user the task is scheduled but not active yet.)r warningT)hermes_cli.cronr r)rr _gwsubjects r'_gateway_liveness_noticers|)=') e|,2(8K$8 BJJ   s{t == == )!4(()s + ;;rv)NN)F)(__doc__rloggingrrtypingrrrrr rr r! getLoggerr<r#rrr(rArSrfrrjrrr{rrrrrrrrrrrrrrrBr'rs(33)   0 1 "OCc3h-."O "OL260Cc3h-.0 d38n0f#SS#X#Shsm#SPXY\P]#SL(d38n(HSM(dSVi(V c]SM#$)&Ec3hECE=3=49=OXc]O8C=OTXY\T]OY^#QUbjknbo&C&HSM& (3-858C=5Xc]543Xsm3X'/}3X9A#3Xlx}#6 5d3i01  !$s),  d3i HSM @ 2T#s(^2S#X2j>T>d>rB