+ iHjE+nRt^RIHt^RIt^RIHt^RIHtHtH t ^RI H t ]P!] 4tRtRtRtR tR R R R RR/tRtR RR RRR/tRtRRltRRltRRltRRltRRltR2RR lltR!R"ltR#R$ltR%tR&],R',t R(R)/R*R+llt!R,R-lt"R.R/lt#R0R1lt$.R3Ot%R#)4aSContextual first-touch onboarding hints, and the entry points of desktop first-run onboarding. Each hint is shown once per install the *first* time a user hits a behavior fork, tracked in ``config.yaml`` under ``onboarding.seen.``. Kept tiny and dependency-free so both the CLI and gateway can import it. First-run onboarding (one chat in the default profile, driven by ``setup_beat``) lives in the siblings: ``onboarding_flow`` (beats and the run record, pure), ``onboarding_text`` (the words), ``onboarding_facts`` (the safe facts) and ``onboarding_record`` (where the run is stored). ) annotationsN)Path)AnyMappingOptional)observe_tool_resultbusy_input_prompttool_progress_promptopenclaw_residue_cleanupprofile_build_offeredqueueu💡 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.redirectu💡 First-time tip — I redirected the current run using your message. Completed work stays in context, and `/stop` still cancels the task. Send `/busy queue` to wait for a separate turn, 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.z(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.z(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 correction redirected the current run without discarding completed work. Use /stop to cancel or /busy queue to wait for a separate turn. 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.c V^8dQhRRRR/#modestrreturn)formats"5/home/ubuntu/.hermes/hermes-agent/agent/onboarding.py __annotate__rJsQQ#Q#Qc6\PV\4#)zMHint shown the first time a user messages while the agent is busy (markdown).)_BUSY_INPUT_HINTS_GATEWAYget _BUSY_INPUT_HINT_GATEWAY_DEFAULTrs&rbusy_input_hint_gatewayrJs $ ( (/O PPrc V^8dQhRRRR/#rr)rs"rrrOsIIcIcIrc6\PV\4#)z=CLI version of the busy-input hint (plain text, no markdown).)_BUSY_INPUT_HINTS_CLIr_BUSY_INPUT_HINT_CLI_DEFAULTrs&rbusy_input_hint_clir$Os $ $T+G HHrcV^8dQhRR/#rrrr)rs"rrrTsqqCqrcR#)u💡 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_gatewayr(Ts prcV^8dQhRR/#r&r)rs"rrrYsWWWrcR#)z(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+Ys VrcV^8dQhRR/#r&r)rs"rrr^s  3 rcR#)zpBanner shown the first time Hermes finds ``~/.openclaw/``: migrate first, cleanup (which breaks OpenClaw) after.uA legacy OpenClaw directory was detected at ~/.openclaw/. To port your config, memory, and skills over to Hermes, run `hermes import-agent openclaw` (from the agent-importers plugin: `hermes plugins install agent-importers`). 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_clir.^s  $rc V^8dQhRRRR/#)rhomezOptional[Path]rboolr)rs"rrrjs.DrcT;'g\P!4R, P4# \dR#i;i)zITrue if ``$HOME/.openclaw`` is a directory (``home`` override for tests).z .openclawF)rr0is_dirOSError)r0s&rdetect_openclaw_residuer5js;$$ 3;;== s6*6 AAc V^8dQhRRRR/#)rconfigMapping[str, Any]rr)rs"rrrrs AA 1A6GArc\V\4'dVPR4MRp\V\4'dV#/#) onboardingN) isinstancerr)r7r:s& r_onboarding_sectionr<rs5-7-H-HL)dJ#J88:@b@rc V^8dQhRRRR/#)rr7r8rrr)rs"rrrwsWW0WSWrc\V4PR4p\V\4'd&VP 4P 4R8XdR#R#)z``config.onboarding.profile_build``: ``"off"`` never offers; anything else -> ``"ask"``. Only governs whether the offer is made; lookups inside the flow are consented to separately in conversation. profile_buildoffask)r<rr;rstriplower)r7rs& rprofile_build_moderDwsG v & * *? ;DtS))djjl.@.@.Be.K5VQVVraIf this message is itself a real request or task, DO THE TASK FIRST -- call whatever tools it needs -- and only then, in the closing sentences of that same reply, do what this note asks. Never let this note replace or skip work the user actually asked for. z:[System note: This is the user's very first message ever. zzWhat this note asks: briefly introduce yourself and mention that /help shows available commands, in one or two sentences.]onboarding_run_activeFc 0V^8dQhRRRRRRRRRRR R /#) rr7r8 config_pathrsession_history_emptyr1install_has_prior_sessionsrErz Optional[str]r)rs"rrrsD      !%     rcHV'dV'g V'dR#\V4R8Xd?\V\4'g)\V\4\ 4P 4#\ # \d'p\PRT4\ uRp?#Rp?ii;i)aReturn a one-shot sidecar note for the install's first-ever message. Matches the gateway first-contact path: when ``profile_build`` is ``ask`` and the offer has not been latched yet, return the opt-in profile-build directive and persist ``onboarding.seen.profile_build_offered``. Otherwise return the plain intro note. Returns ``None`` when this is not the first contact (non-empty session history or prior sessions exist on the install). ``onboarding_run_active``: the chat is running first-run onboarding, whose opening replaces this note. NrAz5first_contact_turn_note failed, using plain intro: %s) rDis_seenPROFILE_BUILD_FLAG mark_seenprofile_build_directiverBPLAIN_INTRO_NOTE Exceptionloggerdebug)r7rGrHrIrEes&&$$$ rfirst_contact_turn_noterTsx" !$>BW  v &% /F$677 k#5 6*,224 4   LaP s$A A0*A00 B!;BB!B!cV^8dQhRR/#r&r)rs"rrrsrc*R\,R,#)zSystem-note directive appended to the very first message ever. Short opt-in profile-build flow persisting to the user-profile memory store; phrased so the agent ASKS before any lookup and never silently reads connected accounts. z< [System note: This is the user's very first message ever. uWhat this note asks: 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.])TASK_FIRST_CLAUSErrrrNrNs  EGX Y 1 1rc$V^8dQhRRRRRR/#)rr7r8flagrrr1r)rs"rrrs'HH%HSHTHrc\V4PR4p\V\4'd\ VPV44#R#)z>True if the user has already been shown this first-touch hint.seenF)r<rr;rr1)r7rYr[s&& rrKrKs; v & * *6 2D#-dG#<#<4 G%Grc$V^8dQhRRRRRR/#)rrGrrYrrr1r)rs"rrrs!4strc^RIHpHpT!T4p\ TPR4\4'g/TR&TR,PR4p\ T\4'g/;qeR,R&TPT4RJd RYa&T!Y4R# \d"p\P RT4Rp?R#Rp?ii;i \d"p\P RY4Rp?R#Rp?ii;i) zWPersist ``onboarding.seen. = True`` atomically; False on any error (best-effort).)atomic_config_writeread_user_config_rawz/onboarding: failed to import config helpers: %sNFr:r[Tz&onboarding: failed to mark flag %s: %s) hermes_cli.configr^r_rPrQrRr;rdict)rGrYr^r_rScfgr[s&& rrMrMsO (5#'',/66 "C < $$V,$%%/1 1D|$V, 88D> %DJ  1  FJ  =tGs/BBC  C&CC C6C11C6)N)BUSY_INPUT_FLAGOPENCLAW_RESIDUE_FLAGrOrLTOOL_PROGRESS_FLAGr$rr5rTrKrMrr.rNrDr+r()&__doc__ __future__rloggingpathlibrtypingrrragent.onboarding_recordr getLogger__name__rQrcrerdrLrrr"r#rr$r(r+r.r5r<rDrWrOrTrNrKrM__all__rrrros* #))7   8 $&+2,   i  < C"P!  S  M W K Q I q W A WA44 #(  @4H . r