The product is the config wizard, not the installer page

Turn OpenClaw setup from config hell into a guided flow

Do not throw JSON, flags, ports, providers, channels, and skills at the user on day one. Ask only what matters, validate it, generate the config, then launch.

Setup progress

One question at a time, not one giant settings screen.

Choose AI provider

Start with the minimum needed. Do not dump the whole config file on the user.

Good onboarding starts with intent, not raw config fields. Template first, details second.

What this site should actually do

1. Ask intent first
2. Collect only relevant config fields
3. Validate each step immediately
4. Generate local config automatically
5. Run health checks and launch

Product truth

The winning UX is not better docs. It is a config compiler wrapped in a wizard.

Users should leave with a working setup, not a deeper understanding of OpenClaw internals.

What to avoid

Huge settings form on one page.

Showing ports, auth, skills, channels, and daemon options to every new user.

Making users copy config snippets from docs and guess what broke.