Repository navigation
NemoClaw v0.0.142 is out! #14282
rsliter
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
NemoClaw v0.0.142 is out
NemoClaw v0.0.142 fixes native inference onboarding and tightens managed vLLM network exposure.
OpenClaw Model Router setup now attaches a sandbox-scoped provider, and GPU readiness checks follow the selected native endpoint.
New managed single-host vLLM containers publish their port only on loopback and the private OpenShell Docker bridge.
Sandbox recovery preserves more of the state you need to keep working.
Registered Hermes NVIDIA sandboxes can recover credential references damaged by an earlier migration, and rebuild completes cleanup before a late CLI failure exits.
Deep Agents Code keeps its managed route identity separate from saved native preferences.
Installation handles unsafe executable directories more carefully and gives clearer Ollama download recovery guidance.
WSL GPU detection finds the driver-provided executable when it is missing from
PATH.The release also improves resource sizing, qualification diagnostics, and the documentation used to operate these paths.
Native Inference and Network Boundaries
Resume restores the recorded attachment after revalidating sandbox identity, keeping the selected route bound to its sandbox.
The attached profile owns its network boundary; the unchanged bundled NVIDIA grant does not remain as a second grant.
Operator-owned policy still has to pass admission checks.
Local NIM and retained shared routes continue to use shared inference.
Missing curl produces a warning and skips this reachability check.
Existing containers retain their bindings until recreated; managed route recovery rejects owned bearerless containers with unsafe bindings.
Sandbox Recovery and Diagnostics
[STRIPPED_BY_MIGRATION].Recovery validates sandbox identity and provider binding, installs a fresh scoped reference, and preserves unrelated settings and user state.
Partial or ambiguous damage remains a refusal.
Cleanup failures remain visible so operators can reconcile retained sources and recovery files.
Thanks to @simoneschiavoi for identifying the failure and documenting its cause in #12959; the replacement was implemented independently.
Rebuild restores saved model and endpoint preferences while retaining the managed identity needed by status and health checks.
Installation, WSL, and Resource Sizing
0002umask.It preserves existing modes and rejects unsafe paths before publishing a binary or shim.
This carries forward @PicoNVIDIA's original contribution in #12497.
Recovery guidance covers blocked outbound access, while fixed diagnostic text avoids exposing proxy credentials from raw stderr.
nvidia-smipath when the command onPATHreports no GPU.Host assessment can recognize an available GPU without requiring a manual
PATHrepair.Equivalent capacity values now produce the same request instead of falling back to total host memory.
Qualification and CI Maintenance
It also reduces unrelated hook downloads and repeated compatibility builds in CI fixtures.
Correlated audit records establish that the plugin tool ran without weakening the web-search guard.
Bounded, redacted diagnostics distinguish preparation failures from growth-check failures.
The default runtime identity and audit policy remain unchanged.
v1installer-action updates that the organization does not allow.Other action updates and
mainretain their existing update behavior.v1GB300 SSH connectivity smoke test.The registration is inert on
mainand does not establish application qualification.Documentation
The provider guides describe the running-container and valid model-list conditions that onboarding already enforces.
Thank You
Thank you to @PansulBhatt for the allocatable-memory sizing fix in #14232.
Thank you to @PicoNVIDIA for the original Ubuntu directory-permission contribution in #12497, carried into this release through #13856.
Thank you to @simoneschiavoi for identifying and documenting the rebuild cleanup failure in #12959.
All reactions