#Onboarding bug

17 messages · Page 1 of 1 (latest)

indigo parrot
#

get this error during onboarding at channel selection if i skip or not:
â—‡ Select channel (QuickStart)
│ Discord (Bot API)
│
â—‡ Discord already configured. What do you want to do?
│ Skip (leave as-is)
TypeError: Cannot read properties of undefined (reading 'trim')

sleek flareBOT
#

That looks like a real onboarding bug, not you messing up Discord config.

The safest workaround for now is:

openclaw onboard --skip-channels

Then if you want to adjust channels after onboarding, run:

openclaw configure --section channels

Can you also paste:

# 
openclaw --version

and, if you have it, the full stack trace after the trim error?

Why I’m leaning bug: that crash is happening in the “already configured” branch, and Cannot read properties of undefined (reading 'trim') strongly suggests the wizard is passing an undefined account/id value through a setup helper instead of cleanly skipping/updating.

CLI docs here too: https://docs.openclaw.ai/cli

If --skip-channels still blows up, that’s definitely GitHub-issue territory and I’ll help you narrow the exact repro.

indigo parrot
#

OpenClaw 2026.4.14 (323493f)

sleek flareBOT
#

I’ve got the version now. I’m checking the verified channel commands so I can give you a cleaner workaround instead of hand-wavy guessing.

#

Thanks, that helps. If you’re on OpenClaw 2026.4.14 (323493f) and still hitting it, then yeah, this is not just an old-version problem, it’s a real bug in that onboarding path.

For now I’d work around it like this:

openclaw onboard --skip-channels

If Discord is already configured, that should let onboarding finish without touching the broken branch.

If you need to add/update Discord afterward, use one of these:

openclaw configure --section channels

or non-interactively:

# 
openclaw channels add --channel discord --token <your-bot-token>

Docs:

This is probably GitHub-issue material now. If you file one, include:

  • OpenClaw 2026.4.14 (323493f)
  • exact repro:
    • openclaw onboard
    • QuickStart
    • select Discord (Bot API)
    • choose either skip or update when it says already configured
    • crash: TypeError: Cannot read properties of undefined (reading 'trim')
#

If you want, paste the full stack trace here too and I’ll help trim it into a solid issue report.

indigo parrot
#

I dont have the full trace. Its not just discord that triggers it. The error throws regardless of what happens in channel section. Seems like right before it moves to the next section it crashes.

sleek flareBOT
#

That’s actually a really useful clue. I’m checking the post-channel handoff now, because that changes the likely bug quite a bit.

#

Ah, that’s a much better clue.

If it blows up no matter which channel path you take, then I don’t think Discord is the real culprit anymore. In the QuickStart flow, the next step after channels is web search setup, then skills, then hooks. So this is probably crashing on the handoff out of channel setup, most likely when it enters search setup.

I’d try this next:

openclaw onboard --skip-search

If that gets past it, we’ve narrowed it down a lot.

If it still crashes, try:

openclaw onboard --skip-search --skip-skills
#

So, updated read: this looks like a post-channel onboarding bug, not a Discord-only bug.

If --skip-search fixes it, that’s enough to turn the GitHub issue into a much sharper repro:

  • OpenClaw 2026.4.14 (323493f)
  • onboarding enters channel section fine
  • crash happens immediately when transitioning to web search / next section
  • TypeError: Cannot read properties of undefined (reading 'trim')

If you want, send back whether --skip-search changes the behavior and I’ll help pin the repro down even tighter.

indigo parrot
#

when i run openclaw configure --section web it finishes as expected, so i think the bug is in channels for sure.

sleek flareBOT
#

That’s good signal, thank you. I’m looking specifically at the end of the channel flow now, not web, so I can stop guessing and give you the narrowest repro/workaround.

#

Yep, that shifts it back toward onboarding’s channel flow, agreed.

If openclaw configure --section web is clean, then the better read is:

  • not “Discord specifically”
  • not “web setup”
  • more likely the QuickStart channel wrapper / shared channel setup helper inside openclaw onboard

The strongest practical workaround is still:

openclaw onboard --skip-channels

then do channels separately with:

# 
openclaw configure --section channels

or

openclaw channels add --channel discord --token <token>

The one check that would narrow it even more is:

openclaw configure --section channels

If that works, then the bug is probably specific to openclaw onboard QuickStart channel handling, not the channel wizard itself.