Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 3 additions & 0 deletions docs/changelog/2026-10-20.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -34,3 +34,6 @@ It also improves uninstall recovery, managed image security, policy recovery, ag
Existing sandboxes retain their prior images until rebuilt; after updating NemoClaw, run `nemoclaw upgrade-sandboxes` to inspect or rebuild them.
A selected Podman runtime no longer triggers Docker host setup, Docker preflight checks, or Docker-only NIM cleanup.
Related change: [PR #13513](https://github.com/NVIDIA/NemoClaw/pull/13513).
- Native local provider attachment now retains the expected OpenShell profile verified during inspection so NemoClaw can check it again after attachment.
A changed profile, failed export, or timeout warns the gateway operator without rolling back a successful attachment.
Related change: [PR #13564](https://github.com/NVIDIA/NemoClaw/pull/13564).
6 changes: 6 additions & 0 deletions docs/inference/understand-provider-validation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,12 @@ The `nvapi-` prefix check applies only to `NVIDIA_INFERENCE_API_KEY`.
OpenRouter keys must be non-empty and begin with `sk-or-`.
Other provider keys use provider-aware validation during the retry flow.

## Native Local Provider Profile Verification

During native local endpoint onboarding, NemoClaw retains the expected OpenShell provider profile after a successful inspection and checks it again after attaching the provider.
If the profile changed or the follow-up export fails or times out, NemoClaw warns the gateway operator without rolling back the attachment.
Ask the gateway operator to inspect the profile before you rely on its credential boundary.

## Provider Requests

NemoClaw sends a provider-specific request that exercises the API surface intended for the route.
Expand Down
Loading