|+j2(dZddlmZddlZddlmZddlmZmZm Z ej e Z dZ dZdZd Zd!d Zd!dZd"dZd"dZd"dZd#d$dZd%dZd"dZd&dZd'dZd(dZgd ZdS))u Contextual first-touch onboarding hints. Instead of blocking first-run questionnaires, show a one-time hint the *first* time a user hits a behavior fork — message-while-running, first long-running tool, etc. Each hint is shown once per install (tracked in ``config.yaml`` under ``onboarding.seen.``) and then never again. Keep this module tiny and dependency-free so both the CLI and gateway can import it without pulling in heavy modules. ) annotationsN)Path)AnyMappingOptionalbusy_input_prompttool_progress_promptopenclaw_residue_cleanupprofile_build_offeredmodestrreturnc,|dkr dS|dkr dS dS)uHint shown the first time a user messages while the agent is busy. ``mode`` is the effective busy_input_mode that was just applied, so the message matches reality ("I just interrupted…" vs "I just queued…"). queueu💡 First-time tip — I queued your message instead of interrupting. Send `/busy interrupt` to make new messages stop the current task immediately, or `/busy status` to check. This notice won't appear again.steeru💡 First-time tip — I steered your message into the current run; it will arrive after the next tool call instead of interrupting. Send `/busy interrupt` or `/busy queue` to change this, or `/busy status` to check. This notice won't appear again.u 💡 First-time tip — I just interrupted my current task to answer you. Send `/busy queue` to queue follow-ups for after the current task instead, `/busy steer` to inject them mid-run without interrupting, or `/busy status` to check. This notice won't appear again.r s //usr/local/lib/hermes-agent/agent/onboarding.pybusy_input_hint_gatewayr$sH  w W   w G   Cc,|dkr dS|dkr dS dS)z=CLI version of the busy-input hint (plain text, no markdown).rz(tip) Your message was queued for the next turn. Use /busy interrupt to make Enter stop the current run instead, or /busy steer to inject mid-run. This tip only shows once.rz(tip) Your message was steered into the current run; it arrives after the next tool call. Use /busy interrupt or /busy queue to change this. This tip only shows once.z(tip) Your message interrupted the current run. Use /busy queue to queue messages for the next turn instead, or /busy steer to inject mid-run. This tip only shows once.rrs rbusy_input_hint_clir?sE w J   w 5   Frc dS)Nu💡 First-time tip — that tool took a while and I'm streaming every step. If the progress messages feel noisy, send `/verbose` to cycle modes (all → new → off). This notice won't appear again.rrrrtool_progress_hint_gatewayrTs Arc dS)Nz(tip) That tool ran for a while. Use /verbose to cycle tool-progress display modes (all -> new -> off -> verbose). This tip only shows once.rrrrtool_progress_hint_clir\s Rrc dS)uwBanner shown the first time Hermes starts and finds ``~/.openclaw/``. Points users at ``hermes claw migrate`` (non-destructive port of config, memory, and skills) first. ``hermes claw cleanup`` is mentioned as the follow-up step for users who have already migrated and want to archive the old directory — with a warning that archiving breaks OpenClaw. uWA legacy OpenClaw directory was detected at ~/.openclaw/. To port your config, memory, and skills over to Hermes, run `hermes claw migrate`. If you've already migrated and want to archive the old directory, run `hermes claw cleanup` (renames it to ~/.openclaw.pre-migration — OpenClaw will stop working after this). This tip only shows once.rrrropenclaw_residue_hint_clircs $rhomeOptional[Path]boolc~|ptj} |dz S#t$rYdSwxYw)uReturn True if an OpenClaw workspace directory is present in ``$HOME``. Pure filesystem check — no side effects. ``home`` override exists for tests. z .openclawF)rris_dirOSError)rbases rdetect_openclaw_residuer&vsR  49;;D{"**,,, uus . <<configMapping[str, Any]c8t|tsdS|d}t|tsdS|d}t|tr,|dkrdSdS)uResolve the onboarding profile-build mode from config. Returns one of: ``"ask"`` — on first contact, OFFER to build a profile (default). ``"off"`` — never offer; the first-message note stays a plain intro. Read from ``config.onboarding.profile_build``. Unknown / missing values fall back to ``"ask"`` so the default experience offers the flow. Any network/account lookups inside the flow are separately consented to in conversation — this setting only governs whether the offer is made. ask onboarding profile_buildoff) isinstancergetr striplower)r'r+r s rprofile_build_moder2s fg & &uL))J j' * *u >>/ * *D$!3!3!5!5!>!>u 5rc dS)uSystem-note directive appended to the very first message ever. Instructs the agent to run a short, opt-in, consent-gated profile-build flow and persist confirmed facts to the user-profile memory store (``memory`` tool, ``target="user"``). Phrased so the agent ASKS before any lookup and never silently reads connected accounts — directly addressing the privacy concern that reading email/accounts unprompted feels invasive. u [System note: This is the user's very first message ever. After a one-sentence introduction (mention /help shows commands), OFFER — do not assume — to build a short profile of them so you can be more useful, and explain they can decline or do it later. If and ONLY IF they accept: 1. Ask for whatever they're comfortable sharing (name, what they do, how they like you to work). Volunteered facts come first. 2. Before ANY external lookup, say what you intend to look up and get explicit consent for that step. Never read their connected accounts (email, calendar, etc.) silently — ask each time. 3. With consent, you may use web_search to confirm public details (e.g. employer, public profiles) from the data points they gave. 4. Save each confirmed, durable fact with the memory tool using target="user" — keep entries compact and high-signal. If they decline at any point, stop immediately and continue normally. Keep the whole exchange light and conversational, not an interrogation.]rrrrprofile_build_directiver4s Srct|tr|dnd}t|tsiS|d}t|tr|niS)Nr+seen)r.rr/)r'r+r6s r_get_seen_dictr7sh-7-H-HRL)))dJ j' * * >>& ! !DdG,, 444"4rflagc`tt||S)zEReturn True if the user has already been shown this first-touch hint.)r!r7r/)r'r8s ris_seenr:s& v&&**400 1 11r config_pathrc ddl}ddlm}n3#t$r&}td|Yd}~dSd}~wwxYw i}|r@t|d5}||pi}dddn #1swxYwYt| dtsi|d<|d d }t|ts i}||dd <| |d urd Sd ||<|||d S#t$r'}td ||Yd}~dSd}~wwxYw) u Persist ``onboarding.seen. = True`` to ``config_path``. Uses the atomic YAML writer so a concurrent process can't observe a partially-written file. Returns True on success, False on any error (including the config file being absent — onboarding is best-effort). rN)atomic_yaml_writez+onboarding: failed to import yaml/utils: %sFzutf-8)encodingr+r6Tz&onboarding: failed to mark flag %s: %s) yamlutilsr= Exceptionloggerdebugexistsopen safe_loadr.r/dict)r;r8r?r=ecfgfr6s r mark_seenrKs +++++++  BAFFFuuuuu      .kG444 .nnQ''-2 . . . . . . . . . . . . . . .#'',//66 # "C < $$V,,$%% -D(,C f % 88D>>T ! !4T +s+++t  =tQGGGuuuuusS =8='D-(B  D- BD-BBD-D-- E7EE)BUSY_INPUT_FLAGTOOL_PROGRESS_FLAGOPENCLAW_RESIDUE_FLAGPROFILE_BUILD_FLAGrrrrrr&r2r4r:rK)r r rr )rr )N)rr rr!)r'r(rr )r'r(rr()r'r(r8r rr!)r;rr8r rr!)__doc__ __future__rloggingpathlibrtypingrrr getLogger__name__rBrLrMrNrOrrrrrr&r2r4r7r:rK__all__rrrrXs  #"""""))))))))))  8 $ $&+2,6*&      .B55552222    F   r