A genuinely user-facing batch this time — four changes you'll notice on the CLI. No new version tag landed (NemoClaw stays at v0.0.67):
- New
nemoclaw use <name>command (#5930): a first-class command that promotes a registered sandbox to the default. Until now, the only way to change the default after onboarding was hand-editing~/.nemoclaw/sandboxes.json. It classifies the outcome (set,already-default,not-found) and lands betweenlistand<name> connectinnemoclaw --help. If you juggle multiple sandboxes, this is the new way to switch which one is default. - Fuzzy sandbox-name suggestions (#5964): mistype a registered sandbox name (e.g.
my-assitantvsmy-assistant) and you now get a Levenshtein-basedDid you mean: nemoclaw <suggestion> <action>?hint instead of having to scan the full registered list. It fires on both the sandbox-not-found and bare-unknown-command paths. - Reasoning-compatible endpoint support (#5948): custom OpenAI-compatible providers can opt into reasoning-mode validation through a new
NEMOCLAW_REASONINGsetting (with alias normalization, persisted through provider handoff and resume). Onboarding then skips the Responses-API, tool-call, and streaming probes that reasoning-only endpoints reject, and retries length-limitedreasoning_content/reasoningsmoke responses with a larger output budget. Useful if you've been blocked connecting a reasoning-only inference endpoint to NemoClaw. - Hardened Windows WSL bootstrap (#5950): the Windows installer now runs
wsl --statusto verify the runtime before attempting to install or run the Ubuntu distro. When WSL is unavailable it attempts awsl --install --no-distributionrepair, requests a reboot only when the output says one is required, and prints offline/manual MSI install guidance (with Microsoft docs + latest WSL release links) when automatic repair is blocked. Distro install output is preserved for troubleshooting. Windows users who hit a broken WSL setup during install should get actionable guidance instead of a hard failure now. - Policy-preset registry fix (#5856): disabling a messaging channel and rebuilding used to leave the disabled channel's preset stale in the registry (the gateway state was pruned, but
policy-liststill showed it). The rebuild now writes back the effective applied set, sopolicy-listreflects the live policy state. - Internal hardening (no user-facing behavior change): bounded retries for transient onboarding inference smoke failures and Docker Desktop host-gateway bridge probes (#5932, #5934, #5754); Hermes final-image stale
.openclaw/.hermes-datastate cleanup and base-digest advance (#5882, #5949); maintainer-workflow policy alignment (#5953); behavior-preserving refactors of messaging-channel collections, registry projections, onboarding/connect phase handoff, and spawn exit-code normalization (#5946, #5945, #5941, #5942, #5939); and E2E/CI restoration of the Anthropic inference-switch variants and Vitest sandbox-operations coverage (#5947, #5926).