NemoClaw v0.0.101 is out!

[apurvvkumaria]

NemoClaw v0.0.101 focuses on keeping state, credentials, and recovery decisions correct when users rebuild sandboxes, switch inference providers, or resume interrupted onboarding. Migration and rebuild backups now fail closed when sanitization or cleanup cannot complete, HTTPS Pin Runtime route cleanup uses the running adapter's policy, and CLI diagnostics no longer emit rejected control characters directly to terminals or CI logs.

The release also expands user-facing workflows. OpenClaw gains experimental Google Chat support through a restricted webhook and host-held service-account boundary, Hermes rebuilds preserve approved home-channel assignments, and status output now distinguishes local SSH sessions from broader runtime health while recognizing the managed Hermes gateway entrypoint.

Under the surface, v0.0.101 adds provider-neutral workload replacement, snapshot, clone, and bootstrap contracts without activating a new runtime provider or buildless onboarding. CI and live end-to-end (E2E) coverage now exercise more messaging, Hermes policy, adapter lifecycle, and sandbox resource-limit paths, giving maintainers clearer evidence for future activation work.

Messaging and Runtime Visibility

• #7317 adds experimental Google Chat support for OpenClaw through a Google-Chat-only webhook tunnel and gateway-minted outbound credentials. This keeps the service-account private key on the host and prevents the public webhook from exposing the dashboard or other control paths.
• #7817 preserves approved Hermes home-channel assignments when a sandbox is rebuilt. Users no longer lose /sethome routing when NemoClaw regenerates credentials and the rest of the environment.
• #7820, #7885, and #7870 make runtime output more precise by reporting local SSH-session counts, recognizing the managed hermes.real gateway, and naming the sandbox in host-side command hints. Operators can distinguish an active agent from an open interactive shell and can copy the right recovery command.
• #8140 clarifies that Slack conflict detection is scoped to one OpenShell gateway registry. This helps operators understand when independent gateways can still establish competing Socket Mode connections.

Inference and Onboarding Recovery

• #7889 authenticates HTTPS Pin Runtime route revocation with the policy used by the running adapter, so a provider switch removes the superseded route and its in-memory credentials. #7891 makes negative timeout and polling overrides fall back to configured defaults, preventing invalid values from collapsing readiness budgets to zero.
• #8106 cleans up a failed managed OpenShell gateway service and continues through the existing ownership-gated standalone path. #7715 makes resume and prerequisite repair honor exact durable state and sandbox identity, which reduces ambiguous recovery after an interrupted or agent-switched onboarding run.

Sandbox and Security

• #7847 applies shared recursive credential filtering to migration and rebuild backups and removes incomplete output when sanitization, cleanup, or filesystem identity checks fail. This prevents a failed backup operation from retaining raw configuration or authentication state.
• #7995 writes an explicit absent configuration-hash record before locking Deep Agents Code configuration. Sandboxes whose image did not ship a hash now reach the intended shields posture instead of failing during lock setup.
• #7993 excludes the selected gateway from uninstall's sibling scan. Removing the last sandbox can now clean shared host resources instead of preserving them because the gateway counted itself.
• #8071 escapes and bounds rejected sandbox and agent names in CLI diagnostics, protecting terminal and log output from control-byte injection. #8081 replaces snapshot payload matching with bounded linear Base64 validation, allowing maximum-size valid payloads while malformed, oversized, non-canonical, and invalid UTF-8 content still fails closed.

Managed Runtime Foundations

• #7749 removes the remaining broad runtime dependency cycle and routes orchestration through the policy seam. This narrows ownership boundaries and makes a registered sandbox report its agent-definition error instead of falling back to OpenClaw paths.
• #8001 adds an atomic managed workload replacement transaction that keeps the old workload authoritative until the replacement is ready and rebound. The transaction remains dormant, but it establishes the compare-and-swap boundary needed for future buildless replacement.
• #8031, #8032, #8034, and #8035 add immutable managed snapshot authority, clone handoff, provider-owned clone transactions, and the Hermes broker boundary. These contracts preserve exact provider, workload, route, messaging, and registry authority without wiring a production snapshot caller.
• #8036, #8037, and #8128 define transactional managed bootstrap and Docker rollback primitives with scrubbed helper environments and receipt-bound cleanup. They remain unregistered and do not activate buildless onboarding, Podman, or another supported runtime provider.

CI and Release Confidence

• #8029 adds repository terminology review to PR Review Advisor, giving maintainers evidence when a change introduces or redefines a project term.
• #8070 consolidates sandbox resource-limit validation into the broader sandbox-operations live E2E and replaces a destructive process storm with a bounded runtime probe. This keeps the security signal while reducing test-host disruption.
• #7875 adds Microsoft Teams to the OpenClaw and Hermes channel stop and start matrix, so channel onboarding, policy, rendering, and lifecycle behavior receive live coverage.
• #8088 selects the required Hermes managed-policy live tests, and #8107 adds Hermes adapter lifecycle selectors. Policy and adapter changes now run the agent-specific evidence that matches their risk.
• #8085 lets a narrowly scoped controller approve exact-head workflow runs for eligible same-repository maintainers while external heads remain gated. This prevents trusted restacks from becoming stranded in ACTION_REQUIRED.
• #8090 provisions pinned fd and rg packages before untrusted CLI tests execute. Coverage shards no longer depend on whether a hosted runner happens to contain Pi's search tools.

Documentation and Release Surface

• #8147 completes the durable documentation follow-ups identified after v0.0.100, including inference-route timing, validation reuse boundaries, and replacement-image cleanup. Readers now have the final behavior in the long-lived guides rather than only in PR context.

See the full comparison between v0.0.100 and v0.0.101.

Thank You

Thank you to external contributor @Ayush7614 for the original backup-sanitization work in #7765, which was preserved and completed in #7847 for this release.