openclaw - 💡(How to fix) Fix [Bug]: Setup Wizard - Silent misconfiguration when using LLM proxy (LiteLLM, vLLM, LM Studio) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70048Fetched 2026-04-23 07:30:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

The OpenClaw setup wizard silently misconfigures LLM connectivity for users who route requests through an LLM proxy (LiteLLM, vLLM, LM Studio, OpenRouter, or any OpenAI-compatible proxy endpoint).

Root Cause

The OpenClaw setup wizard silently misconfigures LLM connectivity for users who route requests through an LLM proxy (LiteLLM, vLLM, LM Studio, OpenRouter, or any OpenAI-compatible proxy endpoint).

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The OpenClaw setup wizard silently misconfigures LLM connectivity for users who route requests through an LLM proxy (LiteLLM, vLLM, LM Studio, OpenRouter, or any OpenAI-compatible proxy endpoint).

Steps to reproduce

  1. Run the OpenClaw setup wizard
  2. Use a proxied LLM endpoint (e.g. LiteLLM) instead of a direct provider API key
  3. Either skip or fill in the VLLM_BASE_URL field
  4. Complete setup

Expected behavior

The wizard should explicitly ask:

"Are you routing LLM requests through a proxy? (LiteLLM, vLLM, LM Studio, etc.)"

  • If Yes → prompt for base URL + API key, configure a named profile (e.g. openai:litellm)
  • If No → continue as normal

Actual behavior

  • VLLM_BASE_URL field is scoped to vLLM only — not proxied endpoints in general
  • If skipped, it silently defaults to localhost:8000 with no warning
  • No prompt asks whether the user is using a proxied endpoint
  • LiteLLM users must manually edit ~/.openclaw/openclaw.json post-install

OpenClaw version

2026.03.24

Operating system

Ubuntu 24.04

Install method

docker

Model

Litellm

Provider / routing chain

Litellm

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The OpenClaw setup wizard needs to be updated to handle proxied LLM endpoints correctly, prompting users for the base URL and API key when using a proxy.

Guidance

  • The issue arises from the VLLM_BASE_URL field being specific to vLLM and not accounting for other proxied endpoints, leading to silent misconfiguration.
  • To mitigate this, users can manually edit the ~/.openclaw/openclaw.json file after installation to correctly configure their proxied LLM endpoint.
  • The setup wizard should be modified to include a prompt for users to indicate if they are using a proxied endpoint, and then request the necessary configuration details (base URL and API key) accordingly.
  • The default behavior of silently defaulting to localhost:8000 when the VLLM_BASE_URL field is skipped should be changed to either prompt the user for the correct information or handle the field in a way that does not lead to misconfiguration.

Example

No code example is provided as the issue description does not include specific code snippets that need modification, but the setup wizard's logic for handling proxied LLM endpoints needs adjustment.

Notes

The solution involves updating the OpenClaw setup wizard to properly handle proxied LLM endpoints, which may require changes to the wizard's UI and backend logic to correctly prompt and configure these endpoints.

Recommendation

Apply workaround: Manually editing the ~/.openclaw/openclaw.json file after installation is a temporary solution until the setup wizard is updated to correctly handle proxied LLM endpoints. This is because the current workaround requires manual intervention post-installation, which could be error-prone and less user-friendly than an updated setup wizard that prompts for the necessary information directly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The wizard should explicitly ask:

"Are you routing LLM requests through a proxy? (LiteLLM, vLLM, LM Studio, etc.)"

  • If Yes → prompt for base URL + API key, configure a named profile (e.g. openai:litellm)
  • If No → continue as normal

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Setup Wizard - Silent misconfiguration when using LLM proxy (LiteLLM, vLLM, LM Studio) [1 participants]