Skip to content

docs: update v0.0.96 release entry #7607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
prekshivyas merged 1 commit into from
Jul 27, 2026
Merged

docs: update v0.0.96 release entry #7607

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/changelog/2026-07-25.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,13 @@ It also hardens blueprint identifier validation, improves onboarding and recover
`doctor` reports incomplete lifecycle metadata without exposing stored values.
An explicit forced rebuild can preserve managed MCP configuration after the old sandbox loses exec access, with exact gateway, policy, and provider proofs before deletion.
Rebuild rechecks the canonical sandbox and recorded gateway at the delete edge, restores MCP state if that target drifts, and keeps shields unlocked when an accepted deletion remains unconfirmed.
When shields lock state before an OpenClaw agent first boots, NemoClaw creates the missing writable `agents/<id>/sessions/` carveout with existing containment checks.
This prevents the sessions-directory `EACCES` failure on that first boot.
Shields failures return exit code `1` without a Node.js traceback, and policy picker EOF returns nonzero.
A `config set` confirmation that reaches EOF exits nonzero without writing.
The error repeats the `--config-accept-new-path` and `NEMOCLAW_CONFIG_ACCEPT_NEW_PATH=1` guidance.
Messaging mutation guards print the exact host command.
For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), [About Managed MCP Servers](/user-guide/openclaw/manage-sandboxes/mcp-servers/about-managed-mcp-servers), and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), [About Managed MCP Servers](/user-guide/openclaw/manage-sandboxes/mcp-servers/about-managed-mcp-servers), [Security Best Practices](/user-guide/openclaw/security/best-practices), and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
Comment thread
coderabbitai[bot] marked this conversation as resolved.
- `nemoclaw <sandbox> mcp status <server> --tools` now requests the configured server's current advertised tool names without invoking any tool.
Discovery is opt-in and sends authenticated traffic through the existing managed OpenShell credential provider and network policy.
The shared client returns names only, bounds time, requests, response bytes, pages, tool count, cursors, and name length, and redacts failure details.
Expand Down
Loading