feat: make provider/model setup less env-var-driven

[Yeachan-Heo]

Source

Discord #claw-code sweep. Users repeatedly reported that provider/model switching via environment variables is sharp-edged compared with OpenCode-style setup screens.

Related existing work:

• feat(providers,auth,oauth): add provider profiles, welcome auth, and OAuth flows #2977 provider profiles / welcome auth / OAuth flows
• docs: add safe PowerShell provider switching example #2979 safe PowerShell provider switching example

Problem

Users currently have to edit env vars or machine settings and hope the selected provider/model path works. This is error-prone for OpenRouter, local OpenAI-compatible servers, and Windows users.

Suggested scope

Add or refine an official setup/settings surface:

• claw setup / /setup / setup wizard
• named provider profiles
• session-only switch vs persistent profile switch
• explicit confirmation before persisting anything
• never echo API keys
• validate base URL and model id before launch
• smoke test: Reply exactly HELLO before claiming success
• dry-run/no-launch mode for scripts/docs

Acceptance criteria

• A user can add/switch a provider without manually editing multiple env vars.
• Failed setup reports whether auth, base URL, model id, or tool-call support is the likely problem.
• Persistent secrets are not printed back to terminal.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[1716775457damn]

Agreed — env vars are friction for non-technical users. We're moving toward a settings.json + guided setup flow (see #2977 for related work). The config wizard approach should reduce the need to touch .env directly for common providers. --name Add a comment

[Yeachan-Heo]

Closing as part of issue tracker triage. This is tracked in ROADMAP.md, is a known limitation, or is off-topic.