Why only 1 option when setting openclaw onboard? | Friends of the Crustacean 🦞🤝 | Page 1

modest mountainBOT Mar 16, 2026, 3:25 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

dapper hawkBOT Mar 16, 2026, 3:29 PM

#

That output is what the wizard looks like when it’s effectively in QuickStart defaults: it will “prompt”, but only offer the default path (QuickStart → OpenAI → Codex OAuth), so you won’t see the big provider list you saw in videos.

Two things to try:

Force the full/advanced flow via flag (bypasses the menu entirely):

openclaw onboard --flow manual

(“manual” = “advanced”, shows all prompts + providers)

If it still always picks the first option, it’s usually the terminal not handling the interactive selector properly. In that case:

try Windows Terminal (instead of classic cmd), and
make sure you’re not running in a non-interactive environment (no output redirection, no weird CI env vars)

Also: please paste the output of:

#

openclaw --version
openclaw onboard --help

Docs for reference:

Wizard overview: https://docs.openclaw.ai/start/wizard
openclaw onboard flags (incl --flow manual): https://docs.openclaw.ai/cli/onboard

alpine moth Mar 16, 2026, 4:45 PM

#

the issue still happens with openclaw onboard --flow manual. then i tried to download windows terminal but i fail to install it and i tried many times. my laptop is win10 and i did download from mircosoft.com but failed to install....

dapper hawkBOT Mar 16, 2026, 4:47 PM

#

If --flow manual still behaves the same, this isn’t “QuickStart hiding options” anymore — it’s almost certainly that your terminal isn’t handling the interactive arrow-key select UI properly (I’ve seen this happen in locked-down Windows environments like Windows Sandbox).

1) Quick workaround: run onboarding non-interactive (no menus)

Pick the provider you actually want via flags.

Example: OpenAI API key (PowerShell)

$env:OPENAI_API_KEY="paste_your_key_here"
openclaw onboard --non-interactive --accept-risk `
  --auth-choice openai-api-key `
  --mode local `
  --skip-search --skip-skills --skip-channels

After that, open the UI:

#

openclaw dashboard

(If you want a different provider, tell me which one, and I’ll paste the exact command for it.)

2) Windows Terminal install in Windows Sandbox (no Microsoft Store)

If you want to fix the interactive menus properly, Sandbox often can’t install from Store. Two alternatives:

A) If winget exists:

winget install --id Microsoft.WindowsTerminal -e

B) If winget is missing: you’ll need the .msixbundle from the official GitHub releases and install via Add-AppxPackage (tell me what error you got when you “fail to install” and I’ll tailor the exact steps).

3) I need 2 outputs to confirm what’s going on

#

Please paste:

openclaw --version

and (PowerShell):

node -e "console.log({inTTY:process.stdin.isTTY,outTTY:process.stdout.isTTY,TERM:process.env.TERM,CI:process.env.CI})"

Those two lines usually make it obvious whether the wizard is seeing a “real TTY” (required for the multi-option selector).

alpine moth Mar 16, 2026, 4:56 PM

#

i get error for winget:

PS C:\Program Files\Sandboxie-Plus> winget install --id Microsoft.WindowsTerminal -e
'winget.exe' 程式無法執行: 用戶端沒有這項特殊權限。位於線路:1 字元:1

winget install --id Microsoft.WindowsTerminal -e

位於線路:1 字元:1

winget install --id Microsoft.WindowsTerminal -e

  + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
  + FullyQualifiedErrorId : NativeCommandFailed

dapper hawkBOT Mar 16, 2026, 4:58 PM

#

That winget.exe ... 用戶端沒有這項特殊權限 error usually means winget/App Installer is blocked by policy / missing privileges in that sandbox environment (very common with Sandboxie / hardened sandboxes). So Windows Terminal install via winget just won’t work there.

Good news: you don’t need Windows Terminal to finish setup if you use the non-interactive path.

Do this instead (no menus, works even in restricted consoles)

If you have a Moonshot key:

openclaw onboard --non-interactive --accept-risk `
  --auth-choice moonshot-api-key `
  --moonshot-api-key "sk-PASTE_KEY" `
  --skip-search --skip-skills --skip-channels
openclaw models set moonshot/kimi-k2.5
openclaw models status

If you meant OpenRouter:

#

openclaw onboard --non-interactive --accept-risk `
  --auth-choice openrouter-api-key `
  --openrouter-api-key "sk-PASTE_KEY"
openclaw models set openrouter/moonshotai/kimi-k2.5
openclaw models status

Quick check (so we can explain why your menus only show 1 option)

Are you running this inside Sandboxie-Plus specifically? (your prompt shows C:\Program Files\Sandboxie-Plus>)

If yes: Sandboxie often breaks the “raw TTY” input mode that arrow-key menus need — which matches your symptom exactly.

If you paste:

openclaw --version

#

node -e "console.log({inTTY:process.stdin.isTTY,outTTY:process.stdout.isTTY})"

…I can confirm that’s what’s happening.

alpine moth Mar 16, 2026, 5:00 PM

#

Yes i am using sandboxie plus.

C:\Program Files\Sandboxie-Plus>openclaw --version
OpenClaw 2026.3.13 (61d171a)

C:\Program Files\Sandboxie-Plus>node -e "console.log({inTTY:process.stdin.isTTY,outTTY:process.stdout.isTTY})"
{ inTTY: true, outTTY: true }

dapper hawkBOT Mar 16, 2026, 5:02 PM

#

Yep — that basically confirms it’s Sandboxie’s console/keyboard hooking, not an OpenClaw version problem.

Even though Node reports inTTY/outTTY: true, the onboarding wizard’s menu UI needs raw keyboard input + ANSI cursor control (arrow keys, redraw, etc). Sandboxie-Plus often interferes with that, so the selector can’t move and you “only get the first option”.

Practical fix (works inside Sandboxie): use non-interactive setup

Since you want Kimi K2.5, run Moonshot non-interactive:

openclaw onboard --non-interactive --accept-risk `
  --auth-choice moonshot-api-key `
  --moonshot-api-key "sk-PASTE_YOUR_MOONSHOT_KEY" `
  --skip-search --skip-skills --skip-channels

Then set the model explicitly:

#

openclaw models set moonshot/kimi-k2.5
openclaw models status

(Your string moonshotai/kimi-k2.5 is the vendor/model name you might see elsewhere; in OpenClaw the provider prefix is moonshot/....)

If you really want the interactive menus back

You’ll need to run onboarding outside Sandboxie (or adjust Sandboxie settings to stop interfering with console raw input). I don’t want to guess which Sandboxie checkbox is safe to flip, because it can weaken the sandbox.

If the commands above work for you, you’re done — and you can keep running OpenClaw in Sandboxie without ever needing the arrow-key menus.

If it works, please mark the solution (right-click message → Apps → ✅ Mark Solution) so Answer Overflow indexes it.

#Why only 1 option when setting openclaw onboard?