Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: openclaw.cmd onboard freezes and fails to write API Key to openclaw.json [1 comments, 2 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#72207•Fetched 2026-04-27 05:33:15
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
xinhanliu0216-droidxinhanliu0216-droid
Participants
clawsweeper[bot]clawsweeper[bot]xinhanliu0216-droidxinhanliu0216-droid
Timeline (top)
labeled ×2closed ×1commented ×1

When running the openclaw.cmd onboard command, the process experiences severe lag/freezing. Furthermore, after completing the onboarding steps (specifically configuring the MiniMax provider), the API Key is not successfully written to the openclaw.json configuration file. The apiKey field remains empty or missing in the auth.profiles section.

Root Cause

When running the openclaw.cmd onboard command, the process experiences severe lag/freezing. Furthermore, after completing the onboarding steps (specifically configuring the MiniMax provider), the API Key is not successfully written to the openclaw.json configuration file. The apiKey field remains empty or missing in the auth.profiles section.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

Yes

Summary

When running the openclaw.cmd onboard command, the process experiences severe lag/freezing. Furthermore, after completing the onboarding steps (specifically configuring the MiniMax provider), the API Key is not successfully written to the openclaw.json configuration file. The apiKey field remains empty or missing in the auth.profiles section.

Steps to reproduce

Run openclaw.cmd onboard in the Windows command prompt.

Observe the severe lag/freezing during the wizard execution.

Attempt to configure the API key for minimax:cn.

Finish the wizard and open the generated config file.

Notice that the API key was not saved in the JSON file.

Expected behavior

The openclaw.cmd onboard process should run smoothly without freezing, and the inputted API Key should be successfully saved to the openclaw.json file under the respective provider's profile.

Actual behavior

The CLI wizard hangs/freezes, and the user must manually edit the JSON file to insert the missing API key.

OpenClaw version

2026.4.24

Operating system

Windows11

Install method

npm global

Model

minimax

Provider / routing chain

CLI -> Local Gateway -> Browser

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 issue can be mitigated by investigating the cause of the severe lag/freezing during the openclaw.cmd onboard process and ensuring the API key is correctly written to the openclaw.json configuration file.

Guidance

  • Investigate the source of the lag/freezing during the openclaw.cmd onboard process to determine if it's related to the API key writing issue.
  • Verify that the openclaw.json file has the correct permissions and is not being overwritten or modified unexpectedly after the onboarding process.
  • Check the minimax provider configuration to ensure it is correctly set up to write the API key to the openclaw.json file.
  • Consider adding logging or debugging statements to the openclaw.cmd script to help identify where the issue is occurring.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be related to a bug in the openclaw.cmd script or the minimax provider configuration. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Manually editing the openclaw.json file to insert the missing API key is a temporary solution, but a more permanent fix is needed to address the underlying issue.

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 openclaw.cmd onboard process should run smoothly without freezing, and the inputted API Key should be successfully saved to the openclaw.json file under the respective provider's profile.

#api#task chaining#parallel task#integration issue#index setup

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]: openclaw.cmd onboard freezes and fails to write API Key to openclaw.json [1 comments, 2 participants]