NemoClaw v0.0.46 is out #3851
ericksoa
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.46
In v0.0.46, NemoClaw takes another careful step from capable instrument toward more widely inhabited world. The release widens the doorway for people arriving from Windows WSL, macOS, DGX Spark, local Ollama, Model Router, and hosted uninstall flows, replacing a little more ritual knowledge with visible paths and recoverable choices. What matters here is not merely that more platforms are named; it is that their first contact with the system is less mysterious.
The messaging universe also becomes more richly populated. WhatsApp joins the channel set with in-sandbox QR pairing, WeChat becomes faster and more durable across sandbox rebuilds, Slack mention safety is repaired, and Hermes gains the managed-tool gateway broker and startup-marker recovery work needed for a steadier integration path. These are small instruments, but together they let the sandbox speak through more channels without dissolving the policy boundary that makes it trustworthy.
Beneath that visible surface, v0.0.46 sharpens the machinery of confidence. The CLI moves closer to a coherent public grammar, non-interactive sandbox execution becomes first-class, provider tool catalogs become dramatically leaner, and the E2E framework learns to describe expected failures instead of treating every negative scenario as folklore. A release is a map of accumulated attention; this one draws attention toward the places users enter, connect, automate, and ask whether the system is healthy.
Installation, Onboarding, and Platform Reach
The release broadens the paved road for Windows WSL, local model setup, hosted uninstall, and provider bootstrap paths.
bash -s --form for passing uninstall flags throughcurl | bash.Messaging, Channels, and Agent Integrations
Messaging support moved from scattered special cases toward durable, policy-aware channel behavior across WhatsApp, WeChat, Slack, and Hermes.
Inference, Runtime, and Sandbox Performance
The runtime became faster and less brittle where provider discovery, sandbox execution, and model-facing tool surfaces meet.
CLI, Policy, and Operator Experience
The command surface is closer to a coherent public grammar: easier to discover, easier to automate, and less dependent on migration-era shims.
nemoclaw <name> execfor non-interactive in-sandbox commands Issues: #3564, #3570, #3616: Adds a direct exec path for automation that needs to run commands inside a sandbox.Test, CI, and Release Reliability
The release also invests in the machinery that tells us when a sandbox is honestly healthy, honestly broken, or honestly expected to fail.
Beta Was this translation helpful? Give feedback.
All reactions