NemoClaw v0.0.96 is out! #7656
cv
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.96 gives operators tighter control over sandbox egress and custom inference. Baseline policy exclusions now survive rebuilds and snapshot restores, while DNS-backed HTTPS endpoints use host-pinned connections and route-scoped sandbox credentials.
The release also improves runtime recovery and diagnostics. Supported hosts can manage the default OpenShell gateway as a service, rebuilds can recover managed MCP state after sandbox exec loss, and opt-in MCP discovery lists advertised tool names without invoking them.
Image and release controls now verify more of the deployed boundary. OpenClaw uses one reviewed production lock, managed images share fixed package inventories, and exact-SHA E2E contracts reduce ambiguity in release evidence.
Network policy and inference boundaries
policy excludeandpolicy restorefor exact baseline entries. Reviewed exclusions persist across rebuilds and snapshot restores without allowing another policy source to reintroduce the excluded key.Gateway, onboarding, and recovery
8080gateway to a validated host service on supported Linux and Apple Silicon macOS hosts. Custom ports and declared external supervisors keep their existing ownership models.config setEOF from writing a new key.MCP, Hermes, and local inference
mcp status <server> --tools. The bounded, authenticated diagnostic lists advertised tool names without invoking a tool or adding another policy path.nemohermes onboard --fromselects the managed Dockerfile. The build now receives every required source path.NEMOCLAW_REASONING. Operators can now see which setting won.Backups, Shields, and managed images
backup-allsandbox its own bounded Shields-down window and restores lockdown before the next sandbox. The batch stops when lockdown restoration fails.2026.7.1production lock authoritative for both image paths. Image assembly verifies lock bytes, registry integrity, installed packages, and lifecycle completion.CI and release confidence
Thank you
Thank you to the external contributors whose work shipped in this release:
See every merged change in the v0.0.95...v0.0.96 comparison.
All reactions