Bug type
Behavior bug (incorrect output/state without crash)
Summary
Custom Provider doesn't work after Onbording with error: No API key found for provider
Steps to reproduce
- Run install: curl -fsSL https://openclaw.ai/install.sh | bash
- Competed onboarding with custom provider OpenAI compatible left API key blank (not need)
- OpenClaw TUI launched with error message: Agent failed before reply: No API key found for provider "custom-127-0-0-1-8080".
Expected behavior
Expected no error. Not sure what actualy should happen I'm using OpenClaw for the first time.
Actual behavior
OpenClaw TUI launched with error message: Agent failed before reply: No API key found for provider "custom-127-0-0-1-8080".
OpenClaw version
Latest as of 2026-03-11
Operating system
Ubuntu 24.0.4 Server
Install method
curl -fsSL https://openclaw.ai/install.sh | bash
Model
Qwen 3.5
Provider / routing chain
Local llama.cpp OpenAI compatible
Config file / key location
No response
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Critical
Additional information
No response
Bug type
Behavior bug (incorrect output/state without crash)
Summary
Custom Provider doesn't work after Onbording with error: No API key found for provider
Steps to reproduce
Expected behavior
Expected no error. Not sure what actualy should happen I'm using OpenClaw for the first time.
Actual behavior
OpenClaw TUI launched with error message: Agent failed before reply: No API key found for provider "custom-127-0-0-1-8080".
OpenClaw version
Latest as of 2026-03-11
Operating system
Ubuntu 24.0.4 Server
Install method
curl -fsSL https://openclaw.ai/install.sh | bash
Model
Qwen 3.5
Provider / routing chain
Local llama.cpp OpenAI compatible
Config file / key location
No response
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Critical
Additional information
No response