Repository navigation
NemoClaw v0.0.141 is out! #14165
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.141 is out
NemoClaw v0.0.141 tightens sandbox recovery and network boundaries.
Interrupted rebuilds refuse to restore an older backup over a surviving sandbox, and auxiliary agent forwards bind to loopback when created or successfully migrated.
Tavily Search removal now verifies that the sandbox can no longer use the removed grants.
Hermes gains adaptive routing configuration for efficient and capable models.
Provider credential attachment remains a separate dependency, so this release does not establish working production routing.
Local inference health checks reject invalid model-server responses, Discord enrollment verifies credentials, and OpenClaw reports when web research is unavailable.
Eligible installer and CLI telemetry now goes to the Production receiver by default.
Set
NEMOCLAW_DISABLE_TELEMETRY=1to opt out.The release also improves recovery guidance, dependency remediation, and the checks used to qualify managed runtimes.
Hermes and Inference
nemohermes onboard --switchyard-config <file>for managed Hermes adaptive routing configuration.Efficient and capable model targets share a classifier based on the capable target.
Provider credential attachment remains tracked in #13863.
Routing changes require sandbox recreation; ordinary inference changes are refused while routing is active.
NIM also checks that its recorded container is running.
This rejects error pages and responses without a JSON model list.
It carries forward @ericcurtin's contribution in #12552.
Conflicting IP pins stop the operation and preserve the inference selection.
Explicit refusal or unreachability is accepted, while accessible responses outside policy denial fail the check.
Ordinary local work and retrieval from user-supplied sources keep their tools.
Sandbox Recovery and Platform Behavior
This protects conversations and configuration written after the retained backup;
--yesand--forcedo not bypass the refusal.It reserves the replacement route after the pre-delete backup succeeds.
Raw credentials remain filtered.
This prevents new damage; it does not repair references already stripped from an older archive.
connectsessions in sandbox status and lifecycle warnings.Operators can see which sessions a destructive operation would interrupt.
The default recovery window is 120 seconds.
connecttimes out, replacing a misleading suggestion to wait longer.Security and Messaging
127.0.0.1, independently of remote dashboard access.If migration cannot prove ownership and the gateway endpoint, it preserves the existing listener, which can remain remotely reachable.
Shared credentials, other sandboxes, and unrelated operator rules are preserved.
Rejected or inconclusive verification leaves new enrollments inactive; failed replacement preserves the existing sandbox.
It does not grant GPU device access.
Telemetry and Version Reporting
Existing delivery conditions and the
NEMOCLAW_DISABLE_TELEMETRY=1opt-out remain in place.0.0.0for Classic builds without Git-derived or stamped version metadata, preventing the fallback from being mistaken for v1.Tagged releases retain their release version.
This includes @rithullkallat-ctrl's package and installer contribution from #14050.
Diagnostics and Documentation
Refused exports publish no YAML.
backup-all.Strict pre-upgrade backup still reports an unreachable running sandbox as a failure.
providers_v2setting on its own line, so onboarding recovery instructions can be copied correctly.The guide preserves that uncertainty and gives trust configuration and verification steps.
Qualification and Contributor Workflows
Correlated execution records establish that the tools ran.
Authenticated qualification remains a separate manual operation.
Thank You
Thank you to @ericcurtin for local inference health checks, clearer container diagnostics, and the vLLM documentation correction.
Thank you to @rithullkallat-ctrl for the Classic version fallback contribution carried into this release.
All reactions