#Onboarding

1 messages · Page 1 of 1 (latest)

zinc plover
#

Hooks ?

#

Ok

#

Should i eneble hooks ?

polar bearBOT
#

“Hooks” in OpenClaw = event-driven automations that run on things like gateway startup or commands (/new, /reset, etc.).

Quick way to explore them:

openclaw hooks list
openclaw hooks info <name>
openclaw hooks enable <name>
openclaw hooks install <path-or-npm-spec>

Docs:

If you meant Discord webhooks (Discord’s feature), that’s a different thing—tell me which one you’re asking about and what you want to trigger (on message? on schedule? on startup?) and I’ll point you at the right approach.

zinc plover
#

Im starting my openclaw onboarding

#

Wondering if i should enable all these hooks

polar bearBOT
#

If you’re just onboarding: you don’t need to enable hooks unless you specifically want what a hook does.

What I’d recommend:

  • Optional / good first hook: session-memory
    It saves session context to memory when you run /new, which can make future sessions more consistent.

Enable it:

openclaw hooks enable session-memory
# then restart the gateway so hooks reload

Before enabling anything else, run:

# 
openclaw hooks list --verbose

and only enable hooks whose behavior you actually want (don’t “enable all” blindly—some are more advanced / behavior-changing, like startup hooks).

zinc plover
#

Ok i will enable the memory

#

Ok new question

polar bearBOT
#

Nice — the quickest “day 0” path is:

  1. Check version (helps immediately if anything’s weird):
openclaw --version
  1. Run the onboarding wizard (CLI):
openclaw onboard --install-daemon
  1. Verify the gateway is up:
openclaw gateway status
zinc plover
#

How to hatch the boot

#

I am doing via CLI on ubuntu

#

Brand new setup just started

polar bearBOT
#

I wouldn’t enable all hooks by default.

Hooks are “code that runs on events” (startup, /new, etc.), so enabling everything can mean extra side effects (writing files, logging, running stuff on startup) that you might not want yet.

What I’d do for a fresh onboarding:

  • Enable: session-memory (useful, low drama; helps carry context when you /new)
  • Maybe enable: command-logger (only if you want an audit log of command events)
  • Leave off until you know you need it: boot-md (runs on gateway startup) and bootstrap-extra-files (more advanced bootstrap behavior)

If you paste the output of:

openclaw hooks list --verbose

I can tell you hook-by-hook which ones are “safe defaults” vs “advanced / behavior-changing” for your setup.

zinc plover
#

i am already on the next question now

#

Hatch in the Tui or Open the Web Ui

polar bearBOT
#

To enable it:

openclaw hooks enable session-memory

Then restart the gateway so it reloads hooks:

  • If you’re running the service: openclaw gateway restart
  • Or just restart the macOS app / gateway process you started

You can confirm it’s on with:

openclaw hooks list
#

What’s the new question?

If it involves an error/setup issue, paste:

  • openclaw --version
  • the exact command you ran
  • the full error output (copy/paste)
#

“Hatch the boot” can mean two different things in OpenClaw:

1) “My onboarding says Wake up, my friend! / won’t hatch”

That usually means the Gateway/agent never actually started.

Try (from the gateway host):

openclaw gateway restart
openclaw status
openclaw models status
openclaw logs --follow

If it’s still stuck:

#

Which one are you seeing: the “Wake up, my friend!” screen, or are you trying to run a BOOT.md checklist on startup?

#

On Ubuntu via CLI, “hatching” (the first-run bootstrapping ritual) basically means: get the Gateway running + open the dashboard + send the first message. Bootstrapping then runs automatically on that first agent run.

Minimal checklist:

openclaw --version
openclaw onboard --install-daemon
openclaw gateway status
openclaw dashboard

Then in the dashboard, start a chat — you should see the one-question-at-a-time bootstrapping prompts (and it will remove BOOTSTRAP.md when done).

If you’re seeing “Wake up, my friend!” but it never replies, run:

# 
openclaw gateway restart
openclaw status
openclaw models status
openclaw logs --follow
openclaw doctor

Tell me where you’re stuck (which step/output), and paste openclaw --version + the last ~30 lines of openclaw logs --follow when it hangs.

#

Cool — for a brand new setup, the next “sanity check” after the wizard finishes is:

openclaw gateway status
openclaw dashboard

Then send a first message in the dashboard chat (that’s what triggers the initial bootstrapping Q&A).

If anything looks stuck (no replies / tokens stay at 0), paste the output of:

openclaw status
openclaw models status
openclaw logs --follow
#

Perfect — that’s the bootstrapping flow. Just keep answering the questions one at a time.

After it finishes, it writes those answers into your workspace files (like IDENTITY.md / USER.md), and you can always tweak them later in ~/.openclaw/workspace/ if you want.

zinc plover
#

ok wait, i will let you know if i need more help

polar bearBOT
#

Either works — they’re just two different “clients” talking to the same Gateway.

Recommendation for first hatch (brand new setup)

Open the Web UI — it’s the easiest way to confirm the Gateway is up and you’re authenticated:

openclaw dashboard

If you prefer staying in the terminal (or you’re SSH’d into a server)

Use the TUI:

openclaw tui

In the TUI you can run /status to sanity-check the connection.