v0.0.68
NemoClaw v0.0.68 improves onboarding recovery, messaging setup, agent-specific CLI behavior, local inference defaults, and release validation:
- Installer and onboarding paths now stop on real setup failures and recover more cleanly after interrupted runs. Scripted installs propagate onboarding exit codes, interrupted installer runs start fresh when no sandbox exists to resume, and resume behavior stays tied to onboarding sessions with a real sandbox. For more information, refer to NemoClaw Quickstart with OpenClaw and Troubleshooting.
- Messaging setup adds experimental Microsoft Teams channel onboarding for OpenClaw and Hermes, including Bot Framework credentials, webhook forwarding, the
teamsnetwork policy preset, and local webhook port conflict checks. NemoClaw also derives channel availability from each channel manifest’ssupportedAgentsdeclaration and rejectschannels addbefore policy, provider, registry, credential, or rebuild mutations when no channel manifest supports the selected agent. LangChain Deep Agents Code therefore fails closed for messaging until a real channel bridge and matching manifest support land. For more information, refer to Choose Messaging Channels and Platform Support and Launch Claims. - Agent-specific CLI commands now route more accurately and fail earlier with clearer local guidance.
sessions exportroutes by sandbox agent kind, Hermesgateway-tokenpoints users todashboard-url, bare OpenClawagentinvocations print wrapper help locally, and omitted extra-agentworkspaceandagentDirfields use canonical OpenClaw paths. For more information, refer to NemoClaw CLI Commands Reference. - LangChain Deep Agents Code sandboxes now stay alive with a stable entrypoint, use their own product branding, reject unsupported messaging mutations, and preserve the hosted-compatible default model ID without doubling the provider namespace. For more information, refer to Quickstart with LangChain Deep Agents Code, Choose an Inference Provider, and Platform Support and Launch Claims.
- DGX Spark express install now selects managed local vLLM by default, while hosted NVIDIA inference setup preserves the provider, namespace, and model ID shape used by the compatible endpoint path. For more information, refer to NemoClaw Quickstart with OpenClaw, Choose an Inference Provider, and Platform Support and Launch Claims.
- Platform-support docs now rely on the canonical support matrix, so users and agents see one source of truth for supported platforms, inference providers, agents, messaging integrations, deployment paths, capabilities, and out-of-scope items. For more information, refer to Platform Support and Launch Claims.