Skip to content

fix(rebuild): abort when gateway provider is missing - #5831

Merged
cv merged 6 commits into
mainfrom
codex/fix-rebuild-missing-provider-preflight
Jun 26, 2026
Merged

fix(rebuild): abort when gateway provider is missing#5831
cv merged 6 commits into
mainfrom
codex/fix-rebuild-missing-provider-preflight

Conversation

@cv

@cv cv commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

Summary

Stop nemoclaw <name> rebuild before backup/delete when the sandbox registry points at a non-local upstream provider that is missing from the OpenShell gateway, even if the matching host credential environment variable is exported. This preserves the existing Hermes API-key self-registration path and local-provider rebuild behavior.

Related Issue

Fixes #5792

Changes

  • Add a rebuild preflight check for missing non-local, non-Hermes OpenShell provider entries before destructive rebuild steps.
  • Emit a targeted failure explaining that the sandbox is untouched and the provider must be re-registered or onboard rerun.
  • Add a CLI-boundary regression test proving rebuild does not back up, delete, recreate, or reach the late provider self-heal path when nvidia-prod is missing but NVIDIA_INFERENCE_API_KEY is present.
  • Document the day-two rebuild requirement in credential storage docs.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Quality Gates

  • Tests added or updated for changed behavior
  • Existing tests cover changed behavior — justification:
  • Tests not applicable — justification:
  • Docs updated for user-facing behavior changes
  • Docs not applicable — justification: existing credential-storage page was updated; no new docs page required.
  • Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
  • Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: self-review of fail-closed rebuild preflight; targeted regression covers host credential present + gateway provider missing, and existing Hermes/local-provider tests stay green.
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Verification

  • PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
  • Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
    • Commit/push hooks were attempted normally, but the full CLI test hook failed on unrelated existing/environmental failures: test/dcode-wrapper-empty-prompt.test.ts positive wrapper cases and resource-limit tests with fork: Resource temporarily unavailable. The branch was pushed with SKIP=test-cli after targeted checks below passed.
  • Targeted tests pass for changed behavior
    • npm run build:cli
    • npx vitest run test/rebuild-credential-preflight.test.ts
    • npm run typecheck:cli
    • git diff --check
    • SKIP=test-cli npx prek run --files src/lib/actions/sandbox/rebuild.ts test/rebuild-credential-preflight.test.ts docs/security/credential-storage.mdx
  • Full npm test passes (broad runtime changes only)
  • Quality Gates section completed with required justifications or waivers
  • No secrets, API keys, or credentials committed
  • npm run docs builds without warnings (doc changes only)
    • Fern reported 0 errors and 2 existing global warnings.
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

  • Bug Fixes
    • Rebuild preflight now aborts when the upstream gateway provider referenced by a sandbox registry entry is missing in OpenShell, even if the matching credential environment variable is set.
    • Improved failure messaging to name the exact missing provider and clarify that it won’t be recreated; rebuild now leaves the sandbox untouched (no backup/delete/recreate).
  • Documentation
    • Updated credential storage guidance with the new rebuild constraint for non-local upstream providers.
  • Tests
    • Added and updated preflight-abort coverage, including scenarios with NVIDIA inference credentials and revised expectations for detailed provider-registration errors.

@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7bcf6b69-df02-4796-bc85-d4fc72caacdc

📥 Commits

Reviewing files that changed from the base of the PR and between 1733fcb and 11d4996.

📒 Files selected for processing (1)
  • test/rebuild-credential-preflight.test.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/rebuild-credential-preflight.test.ts

📝 Walkthrough

Walkthrough

Rebuild now verifies the sandbox’s upstream provider is registered in OpenShell before proceeding. If the provider is missing, preflight aborts, leaves the sandbox untouched, and the docs and tests reflect the new behavior.

Changes

Rebuild preflight provider validation

Layer / File(s) Summary
Gateway provider gating
src/lib/actions/sandbox/rebuild.ts
Adds the missing-provider failure message and the gateway-provider registration check used by rebuild preflight.
Preflight bailouts
src/lib/actions/sandbox/rebuild.ts
Applies the gateway-provider check in both credential-flow branches and stops rebuild before sandbox destruction when the provider is missing.
Regression test and note
test/rebuild-credential-preflight.test.ts, docs/security/credential-storage.mdx
Adds the missing-provider regression test, updates related assertions, and refreshes the credential-storage note to match the rebuild requirement.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Suggested labels

area: cli, area: sandbox, bug-fix

Suggested reviewers

  • ericksoa

Poem

A rabbit checked the OpenShell gate,
and paused rebuild before too late.
No sandbox fell, no backup grew,
the burrow stayed the same and true.
🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: aborting rebuild when the gateway provider is missing.
Linked Issues check ✅ Passed The rebuild preflight now bails before destructive steps when the gateway provider is missing, preserving the sandbox and avoiding self-heal.
Out of Scope Changes check ✅ Passed The docs and test updates support the rebuild preflight fix and no unrelated changes are indicated.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/fix-rebuild-missing-provider-preflight

Comment @coderabbitai help to get the list of available commands.

@github-code-quality

github-code-quality Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in the codex/fix-rebuild-mi... branch is 96%. Coverage data for the main branch is not yet available.

Show a code coverage summary of the most covered files.
File main codex/fix-rebuild-mi... 25ed5a2 +/-
nemoclaw/src/se...cret-scanner.ts 100%
nemoclaw/src/commands/slash.ts 100%
nemoclaw/src/li...bprocess-env.ts 100%
nemoclaw/src/bl...eprint/state.ts 98%
nemoclaw/src/onboard/config.ts 98%
nemoclaw/src/bl...int/snapshot.ts 97%
nemoclaw/src/bl...print/runner.ts 95%
nemoclaw/src/co...ration-state.ts 94%
nemoclaw/src/bl...ate-networks.ts 94%
nemoclaw/src/index.ts 94%

TypeScript / code-coverage/cli

The overall coverage in the codex/fix-rebuild-mi... branch is 47%. Coverage data for the main branch is not yet available.

Show a code coverage summary of the most covered files.
File main codex/fix-rebuild-mi... 25ed5a2 +/-
src/lib/state/o...oard-session.ts 91%
src/lib/inference/local.ts 76%
src/lib/actions...dbox/rebuild.ts 73%
src/lib/sandbox/config.ts 72%
src/lib/onboard/preflight.ts 62%
src/lib/actions...licy-channel.ts 60%
src/lib/state/sandbox.ts 56%
src/lib/policy/index.ts 49%
src/lib/onboard...er-gpu-patch.ts 47%
src/lib/onboard.ts 19%

Updated June 26, 2026 02:58 UTC
Code Coverage is in Public Preview. Learn more and provide us with your feedback.

@github-actions

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
src/lib/actions/sandbox/rebuild.ts (1)

520-545: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Prioritize the missing-provider abort over the missing-env fallback.

If hydrateCredentialEnv() returns null and the gateway provider is also missing, this branch falls through to the old missing-credential error instead of the new missing-provider abort. That contradicts the new preflight contract and points users at exporting the env var even though rebuild still cannot continue until the OpenShell provider is re-registered.

Suggested fix
-  if (credentialValue) {
-    if (shouldVerifyGatewayProvider && !gatewayProviderExists()) {
-      printMissingRebuildGatewayProvider(rebuildProvider, rebuildCredentialEnv);
-      bail(`Missing gateway provider: ${rebuildProvider}`);
-      return false;
-    }
-    return true;
-  }
-  if (shouldVerifyGatewayProvider && gatewayProviderExists()) {
+  if (shouldVerifyGatewayProvider && !gatewayProviderExists()) {
+    printMissingRebuildGatewayProvider(rebuildProvider, rebuildCredentialEnv);
+    bail(`Missing gateway provider: ${rebuildProvider}`);
+    return false;
+  }
+  if (credentialValue) {
+    return true;
+  }
+  if (shouldVerifyGatewayProvider) {
     log(
       `Preflight credential check: provider '${rebuildProvider}' registered in gateway — skipping env check for ${rebuildCredentialEnv}`,
     );
     return true;
   }
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/lib/actions/sandbox/rebuild.ts` around lines 520 - 545, The preflight
logic in `hydrateCredentialEnv()`/`rebuild` is letting the missing-env fallback
run when both the credential and gateway provider are absent, instead of
aborting on the missing provider first. Reorder the checks so the
`shouldVerifyGatewayProvider && !gatewayProviderExists()` path is handled before
any env-based fallback, and make sure the
`bail()`/`printMissingRebuildGatewayProvider()` flow is the first exit when the
provider is not registered.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@src/lib/actions/sandbox/rebuild.ts`:
- Around line 520-545: The preflight logic in `hydrateCredentialEnv()`/`rebuild`
is letting the missing-env fallback run when both the credential and gateway
provider are absent, instead of aborting on the missing provider first. Reorder
the checks so the `shouldVerifyGatewayProvider && !gatewayProviderExists()` path
is handled before any env-based fallback, and make sure the
`bail()`/`printMissingRebuildGatewayProvider()` flow is the first exit when the
provider is not registered.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 992dc251-ea90-4c52-a0b4-0736784ecbe4

📥 Commits

Reviewing files that changed from the base of the PR and between ababaad and fe18311.

📒 Files selected for processing (3)
  • docs/security/credential-storage.mdx
  • src/lib/actions/sandbox/rebuild.ts
  • test/rebuild-credential-preflight.test.ts

@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: rebuild-openclaw-e2e, rebuild-hermes-e2e, channels-add-remove-e2e
Optional E2E: credential-migration-e2e, sandbox-operations-e2e

Dispatch hint: rebuild-openclaw-e2e,rebuild-hermes-e2e,channels-add-remove-e2e

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • rebuild-openclaw-e2e (high): Directly exercises the OpenClaw sandbox rebuild lifecycle against a real OpenShell gateway, including provider/credential chain integrity after rebuild and backup safety. This is the primary runtime path touched by the new rebuild provider preflight.
  • rebuild-hermes-e2e (high): Covers the Hermes rebuild path through the same shared rebuildSandbox credential preflight and verifies messaging placeholders, provider-backed credentials, backup safety, and post-rebuild inference chain behavior.
  • channels-add-remove-e2e (high): This job contains the existing gateway-credential-reuse regression gate for rebuild with NVIDIA_INFERENCE_API_KEY unset while the provider is registered in OpenShell. The PR changes that exact gateway-provider preflight decision path, so this should be merge-blocking.

Optional E2E

  • credential-migration-e2e (medium): Adjacent confidence for credential storage and OpenShell gateway registration semantics. The PR does not change legacy migration code directly, so this is useful but not required.
  • sandbox-operations-e2e (high): Broad sandbox lifecycle smoke for real sandbox commands and registry/gateway state. It is less targeted than the rebuild-specific jobs but could catch unexpected lifecycle regressions.

New E2E recommendations

  • rebuild credential preflight / missing OpenShell provider (high): Existing rebuild E2Es primarily validate successful rebuild when the provider is present, and channels-add-remove validates gateway credential reuse when env is absent. This PR introduces a negative boundary: if the registry points to a non-local provider missing from OpenShell, rebuild must abort before backup/delete even when the matching host credential env var is exported. That specific destructive-safety path appears covered only by unit tests in this PR.
    • Suggested test: Add a live rebuild E2E phase or dedicated job that onboards a sandbox, deletes the inference provider from OpenShell, exports the credential env var, runs nemoclaw <name> rebuild --yes, and asserts non-zero exit, missing-provider message, no backup/delete/recreate, and registry/sandbox still intact.

Dispatch hint

  • Workflow: nightly-e2e.yaml
  • jobs input: rebuild-openclaw-e2e,rebuild-hermes-e2e,channels-add-remove-e2e

@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Vitest E2E Scenario Recommendation

Required Vitest E2E scenarios: rebuild-openclaw-vitest
Optional Vitest E2E scenarios: sandbox-rebuild-vitest, rebuild-hermes-vitest

Dispatch required Vitest E2E scenarios:

  • gh workflow run e2e-vitest-scenarios.yaml --ref <pr-head-ref> --field jobs=rebuild-openclaw-vitest

Workflow run

Full Vitest E2E advisor summary

Vitest E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required Vitest E2E scenarios

  • rebuild-openclaw-vitest: The PR changes shared sandbox rebuild credential/provider preflight logic for non-local upstream providers. The OpenClaw rebuild live Vitest job runs the real nemoclaw <sandbox> rebuild --yes path with a registered NVIDIA/OpenShell provider and validates rebuild state preservation and credential hygiene.
    • Dispatch: gh workflow run e2e-vitest-scenarios.yaml --ref <pr-head-ref> --field jobs=rebuild-openclaw-vitest

Optional Vitest E2E scenarios

  • sandbox-rebuild-vitest: Adjacent rebuild coverage using a normally onboarded OpenClaw sandbox; useful to confirm the updated provider preflight still passes the standard day-two rebuild path.
    • Dispatch: gh workflow run e2e-vitest-scenarios.yaml --ref <pr-head-ref> --field jobs=sandbox-rebuild-vitest
  • rebuild-hermes-vitest: Adjacent rebuild coverage for the Hermes agent path, including curated registry/session rebuild metadata and provider-backed sandbox recreation; useful because the changed preflight is shared across rebuild implementations.
    • Dispatch: gh workflow run e2e-vitest-scenarios.yaml --ref <pr-head-ref> --field jobs=rebuild-hermes-vitest

Relevant changed files

  • src/lib/actions/sandbox/rebuild-provider-preflight.ts
  • src/lib/actions/sandbox/rebuild.ts

@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: Add or justify PRA-T1 and any related test follow-ups.
Open items: 0 required · 0 warnings · 0 suggestions · 6 test follow-ups
Since last review: 1 prior item resolved · 0 still apply · 0 new items found

Action checklist

  • PRA-T1 Add or justify test follow-up: Runtime validation
  • PRA-T2 Add or justify test follow-up: Runtime validation
  • PRA-T3 Add or justify test follow-up: Runtime validation
  • PRA-T4 Add or justify test follow-up: Acceptance clause
  • PRA-T5 Add or justify test follow-up: Acceptance clause
  • PRA-T6 Add or justify test follow-up: Acceptance clause
Test follow-ups to resolve or justify

If these cover changed behavior, prefer adding them in this PR; otherwise state why existing coverage is enough or link the follow-up.

  • PRA-T1 Runtime validation — Run or add a targeted runtime/integration scenario where deleting `nvidia-prod` before `nemoclaw <name> rebuild --yes` exits non-zero and leaves the original sandbox/container/image identity unchanged.. CLI-boundary fixture coverage is strong for the changed branch, but the linked bug involves real OpenShell sandbox identity, backup directory creation, and lifecycle logs that the fake OpenShell fixture approximates.
  • PRA-T2 Runtime validation — Run or add runtime validation that a missing `nvidia-prod` with exported `NVIDIA_INFERENCE_API_KEY` creates no new `rebuild-backups` entry and does not invoke `openshell sandbox delete`, image build, or resume-provider self-heal.. CLI-boundary fixture coverage is strong for the changed branch, but the linked bug involves real OpenShell sandbox identity, backup directory creation, and lifecycle logs that the fake OpenShell fixture approximates.
  • PRA-T3 Runtime validation — Run or add post-abort validation that `nemoclaw <name> status` still reports the original sandbox usable after the missing-provider rebuild attempt.. CLI-boundary fixture coverage is strong for the changed branch, but the linked bug involves real OpenShell sandbox identity, backup directory creation, and lifecycle logs that the fake OpenShell fixture approximates.
  • PRA-T4 Acceptance clause — nemoclaw onboard --agent langchain-deepagents-code --name dcode-rebuild-pf — add test evidence or identify existing coverage. The test fixture creates the sandbox registry and onboard session directly instead of running a real `onboard`; this is adequate for the changed rebuild preflight branch because the code under review consumes registry/session state.
  • PRA-T5 Acceptance clause — nemoclaw dcode-rebuild-pf exec -- dcode -n "PRE" # confirm baseline — add test evidence or identify existing coverage. The changed tests do not execute a real agent command, but they establish the pre-existing sandbox entry and verify the rebuild abort leaves that registry entry present.
  • PRA-T6 Acceptance clause — nemoclaw dcode-rebuild-pf status — add test evidence or identify existing coverage. The changed tests do not run a follow-up `status`, but they assert the registry entry remains and that delete/recreate output is absent. Runtime status validation remains a useful follow-up.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

@cv cv added the v0.0.69 label Jun 26, 2026
cv added 3 commits June 25, 2026 19:04
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv
cv merged commit 5a71b2f into main Jun 26, 2026
41 checks passed
@cv
cv deleted the codex/fix-rebuild-missing-provider-preflight branch June 26, 2026 03:05
Hadar301 pushed a commit to Hadar301/NemoClaw-OpenShift that referenced this pull request Jul 12, 2026
## Summary
Stop `nemoclaw <name> rebuild` before backup/delete when the sandbox
registry points at a non-local upstream provider that is missing from
the OpenShell gateway, even if the matching host credential environment
variable is exported. This preserves the existing Hermes API-key
self-registration path and local-provider rebuild behavior.

## Related Issue
Fixes NVIDIA#5792

## Changes
- Add a rebuild preflight check for missing non-local, non-Hermes
OpenShell provider entries before destructive rebuild steps.
- Emit a targeted failure explaining that the sandbox is untouched and
the provider must be re-registered or onboard rerun.
- Add a CLI-boundary regression test proving rebuild does not back up,
delete, recreate, or reach the late provider self-heal path when
`nvidia-prod` is missing but `NVIDIA_INFERENCE_API_KEY` is present.
- Document the day-two rebuild requirement in credential storage docs.

## Type of Change

- [ ] Code change (feature, bug fix, or refactor)
- [x] Code change with doc updates
- [ ] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)

## Quality Gates
- [x] Tests added or updated for changed behavior
- [ ] Existing tests cover changed behavior — justification:
- [ ] Tests not applicable — justification:
- [x] Docs updated for user-facing behavior changes
- [x] Docs not applicable — justification: existing credential-storage
page was updated; no new docs page required.
- [x] Sensitive paths changed (security, policy, credentials, preflight,
onboarding, inference, runner, sandbox, or messaging)
- [x] Sensitive-path review completed or maintainer-approved waiver
recorded — reviewer/approval link/justification: self-review of
fail-closed rebuild preflight; targeted regression covers host
credential present + gateway provider missing, and existing
Hermes/local-provider tests stay green.
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Verification
- [x] PR description includes the DCO sign-off declaration and every
commit appears as `Verified` in GitHub
- [ ] Git hooks passed during commit and push, or `npx prek run
--from-ref main --to-ref HEAD` passes
- Commit/push hooks were attempted normally, but the full CLI test hook
failed on unrelated existing/environmental failures:
`test/dcode-wrapper-empty-prompt.test.ts` positive wrapper cases and
resource-limit tests with `fork: Resource temporarily unavailable`. The
branch was pushed with `SKIP=test-cli` after targeted checks below
passed.
- [x] Targeted tests pass for changed behavior
  - `npm run build:cli`
  - `npx vitest run test/rebuild-credential-preflight.test.ts`
  - `npm run typecheck:cli`
  - `git diff --check`
- `SKIP=test-cli npx prek run --files src/lib/actions/sandbox/rebuild.ts
test/rebuild-credential-preflight.test.ts
docs/security/credential-storage.mdx`
- [ ] Full `npm test` passes (broad runtime changes only)
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [x] `npm run docs` builds without warnings (doc changes only)
  - Fern reported 0 errors and 2 existing global warnings.
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)

---
Signed-off-by: Carlos Villela <cvillela@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* Rebuild preflight now aborts when the upstream gateway provider
referenced by a sandbox registry entry is missing in OpenShell, even if
the matching credential environment variable is set.
* Improved failure messaging to name the exact missing provider and
clarify that it won’t be recreated; rebuild now leaves the sandbox
untouched (no backup/delete/recreate).
* **Documentation**
* Updated credential storage guidance with the new rebuild constraint
for non-local upstream providers.
* **Tests**
* Added and updated preflight-abort coverage, including scenarios with
NVIDIA inference credentials and revised expectations for detailed
provider-registration errors.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@wscurran wscurran added area: cli Command line interface, flags, terminal UX, or output bug-fix PR fixes a bug or regression labels Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: cli Command line interface, flags, terminal UX, or output bug-fix PR fixes a bug or regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[All Platforms][CLI&UX] nemoclaw rebuild does not abort when upstream provider is missing — destroys and recreates sandbox with EXIT:0

2 participants