/initiate-setup is a prompt built-in in the /plan shape on the CLI, the TUI,
the desktop app and the messaging gateway (/initiate_setup on Telegram). It
sends one normal user turn: a fixed "[/initiate-setup]" header, the
optional-skills initiate-setup SKILL.md read in place, and a JSON fact block
with the SKILL.md key names (surface, tools_present, primary_profile,
guest_free_tier, plus the host_facts.py collect() output at top level). Each
surface resolves the tools present without a live agent, the same way /tools
does, and builds under the session's profile scope.
The first-contact note no longer carries the profile-build directive (memory
tool, web lookups). With onboarding.profile_build "ask" it asks for a short
intro that ends with one line offering /initiate-setup, latched once as
before. The note is skipped when the first message is the rendered
/initiate-setup prompt. The classic CLI now stages the same note.
Placement: the gateway and CLI handlers live in gateway/slash_commands.py and
hermes_cli/cli_chat_turn_mixin.py because run_inbound.py and
cli_commands_mixin.py are already over the 2000-line gate. Gateway dispatch
maps "-" to "_" in the _hm_cmd_ lookup. The prompt builder now runs off the
event loop (asyncio.to_thread), because this builder reads files and probes
the host.
9c4eecb53d