[Bug]: Windows setup wizard crashes when selecting LM Studio provider: Cannot read properties of undefined (reading 'prompt')

[askasjeremy]

Description

The OpenClaw Windows native app setup wizard crashes when I try to configure LM Studio as a local model provider.

During the model/provider selection step, I choose:

1. Other
2. LMStudio / LM Studio

Immediately after selecting LM Studio, the setup wizard shows this error:

TypeError: Cannot read properties of undefined (reading 'prompt')

<img width="883" height="953" alt="Image" src="https://github.com/user-attachments/assets/b96ac3f0-80cb-4825-a3b4-66b03aa2d88f" />

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 11, 2026, 2:18 AM ET / 06:18 UTC.

Summary
Codex review failed: codex execution failed.

Reproducibility: unclear. The review failed before ClawSweeper could establish a reproduction path.

Ways to help us reproduce this

• Add expected vs actual behavior.

Next step
Review did not complete, so no work-lane recommendation was made.

Review details

Best possible solution:

Retry the Codex review after fixing the execution failure.

Do we have a high-confidence way to reproduce the issue?

Unclear. The review failed before ClawSweeper could establish a reproduction path.

Is this the best way to solve the issue?

Unclear. Retry the review first so ClawSweeper can evaluate the actual issue and fix direction.

AGENTS.md: unclear because the file could not be read completely.

Remaining risk / open question:

• No close action taken because the review did not complete.

Codex review notes: model internal, reasoning high; reviewed against 3fdfbfad837f.

Label changes

Label changes:

• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:needs-info: Current issue advisory state selects this label.
• remove P2: Current review triage priority is none.
• remove clawsweeper:no-new-fix-pr: Current issue advisory state no longer selects this label.
• remove clawsweeper:needs-maintainer-review: Current issue advisory state no longer selects this label.
• remove issue-rating: 🐚 platinum hermit: Current issue advisory state no longer selects this label.
• remove clawsweeper:needs-live-repro: Current issue advisory state no longer selects this label.
• remove impact:auth-provider: Current review selected no impact labels.

Evidence reviewed

What I checked:

• failure reason: codex execution failed.
• codex failure detail: Codex review failed for this issue with exit 1.
• codex stdout: Per-item Codex failure; continuing with the rest of the shard.

Likely related people:

• unknown: Codex failed before it could trace repository history. (role: review did not complete; confidence: low)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[askasjeremy]

Thanks for the review and for keeping the issue open.

I’m attaching a short screen recording showing the reproduction of the error.

In the recording, the flow is:

1. Open the OpenClaw Windows setup wizard
2. Reach the Gateway setup / model provider selection step
3. Select Other
4. Select LMStudio / LM Studio
5. The wizard immediately shows:

TypeError: Cannot read properties of undefined (reading 'prompt')

The error happens before I get a chance to enter or confirm any LM Studio URL or model configuration.

Expected behavior

After selecting LM Studio, I expected the wizard to continue to the LM Studio provider setup step, where I could configure something like:

http://192.168.188.4:1234/v1

or:

http://127.0.0.1:1234/v1

Actual behavior

The wizard stops immediately and shows:

TypeError: Cannot read properties of undefined (reading 'prompt')

LM Studio status

LM Studio is running correctly on my machine.

From the LM Studio window:

• LM Studio version: 0.4.15
• Server status: Running
• Port: 1234
• Reachable at:

http://192.168.188.4:1234

The LM Studio logs also show the OpenAI-compatible endpoints are available, including:

GET  /v1/models
POST /v1/responses
POST /v1/chat/completions
POST /v1/completions
POST /v1/embeddings

Laptop / system specs

• Laptop model: Acer Nitro ANV15-51
• OS: Windows 11 Enterprise 64-bit
• CPU: 13th Gen Intel Core i7-13620H
• RAM: 32 GB
• GPU: NVIDIA GeForce RTX 4050 Laptop GPU
• Storage: 954 GB
• OpenClaw app: Windows native app from openclaw-windows-node

Additional note

In the wizard, I noticed the provider appears as LMStudio / possibly LMStudo depending on the UI text. I’m not sure if that provider key/name is related, but the crash happens immediately after selecting that option.

Please let me know if there are specific gateway logs, WSL logs, or config files I should collect and attach.

LMStudio.Selection.Error.-.OpenClaw.Windows.Node.mp4

[christineyan4]

I was able to reproduce this locally, but the root cause is in the gateway-side LM Studio provider setup, not the Windows UI. The LM Studio setup code extracted wizard prompter methods and called them unbound, which breaks the gateway wizard’s class-method prompter.

Upstream gateway fix PR is open here: openclaw/openclaw#90429

I also locally patched the installed gateway with the same fix and verified the Windows wizard now advances to the LM Studio base URL step instead of the TypeError. However Windows follow-up remains pending until the gateway fix lands and maintainers choose the fixed gateway release/LKG version that openclaw-windows-node should consume.

[askasjeremy]

Thanks @christineyan4 for reproducing the issue and submitting the fix.

From the PR notes, it looks like the patched gateway now correctly advances to the “LM Studio base URL” step instead of crashing with TypeError: Cannot read properties of undefined (reading 'prompt'), which matches the issue I reported.

I understand that Windows app consumption of an official fixed gateway release/LKG has not been tested yet, so I will wait for the PR to be merged and for the fixed gateway version to be included in the Windows setup flow before confirming the issue as fully resolved from my side.

Thanks again for the quick work on this.

[github-actions]

🤖 This is an automated response from Repo Assist.

Thanks for the detailed report and screen recording — this is a clear reproduction.

Based on the investigation by @christineyan4 above, the root cause is in the gateway-side LM Studio wizard, not in the Windows tray app:

• The LM Studio setup code called gateway wizard prompter methods as unbound functions, breaking the class-method resolution when this context wasn't captured.
• An upstream gateway fix PR is open at openclaw/openclaw#90429.
• @christineyan4 locally verified the fix resolves the crash and the wizard correctly advances to the LM Studio base URL step.

Since the crash originates in the gateway's Node.js setup wizard rather than in this Windows openclaw-windows-node codebase, there isn't a patch we can apply here. The fix needs to come from the upstream gateway PR being merged and then picked up in the gateway version pinned by this repo.

For users hitting this today: You can work around it by setting up LM Studio in the gateway config directly (not through the Windows wizard) until the upstream fix lands.

Generated by 🌈 Repo Assist, see workflow run. Learn more.

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@97143ac59cb3a13ef2a77581f929f06719c7402a