openclaw - 💡(How to fix) Fix [Bug]: Sandbox created with kimi model but OpenClaw session runs nemotron-3-super-120b-a12b [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#52805Fetched 2026-04-08 01:19:07
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2closed ×1locked ×1

When creating a new NemoClaw sandbox I selected the kimi model in the wizard, but after connecting, openclaw status shows the active session is running nvidia/nemotron-3-super-120b-a12b instead of kimi.

Root Cause

When creating a new NemoClaw sandbox I selected the kimi model in the wizard, but after connecting, openclaw status shows the active session is running nvidia/nemotron-3-super-120b-a12b instead of kimi.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

When creating a new NemoClaw sandbox I selected the kimi model in the wizard, but after connecting, openclaw status shows the active session is running nvidia/nemotron-3-super-120b-a12b instead of kimi.

Steps to reproduce

Step 1: On macOS, install and initialize NemoClaw with Step 2: Create a new sandbox (e.g. e2e-cloud-experimental) and, in the creation flow, explicitly select the kimi model as the base model. Step 3: After creation completes, run nemoclaw e2e-cloud-experimental connect and inside the sandbox run

<img width="2100" height="1332" alt="Image" src="https://github.com/user-attachments/assets/798f2f0e-0756-440a-846d-160fdc3d05f9" /> <img width="1608" height="588" alt="Image" src="https://github.com/user-attachments/assets/db405808-3bbc-4ca6-9541-af8799d2bf62" />

Expected behavior

The active session model shown in openclaw status should match the model selected during sandbox creation

Actual behavior

openclaw status shows the session model as nvidia/nemotron-3-super-120b-a12b, even though kimi was selected at creation time

OpenClaw version

2026.3.11 (29dc654)

Operating system

macOS 26.1 (Apple M4, arm64)

Install method

curl

Model

kimi

Provider / routing chain

nemoclaw setup-> openclaw config

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue of the active session model not matching the selected model during sandbox creation, we need to update the openclaw configuration to use the correct model.

Here are the steps:

  • Check the openclaw configuration file for the e2e-cloud-experimental sandbox and verify that the model field is set to kimi.
  • If the model field is not set to kimi, update the configuration file to use the correct model.
  • Restart the openclaw service to apply the changes.

Example configuration update:

# openclaw-config.yaml
model: kimi

Alternatively, you can use the openclaw command-line interface to update the model:

openclaw config set model kimi

Verification

To verify that the fix worked, run the following command:

openclaw status

The output should show the active session model as kimi.

Extra Tips

Make sure to check the openclaw version and update to the latest version if necessary. Additionally, verify that the kimi model is compatible with the e2e-cloud-experimental sandbox and the nemoclaw setup.

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 active session model shown in openclaw status should match the model selected during sandbox creation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING