Skip to content

fix(onboard): remove experimental vLLM label on managed platforms - #6655

Merged
cv merged 2 commits into
mainfrom
fix/vllm-experimental-label
Jul 10, 2026
Merged

fix(onboard): remove experimental vLLM label on managed platforms#6655
cv merged 2 commits into
mainfrom
fix/vllm-experimental-label

Conversation

@zyang-dev

@zyang-dev zyang-dev commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Summary

Removes the experimental label from the running Local vLLM provider entry on managed vLLM platforms. DGX Spark and DGX Station now show Local vLLM as supported, while generic and unknown platforms retain the experimental label.

Changes

  • Make the running Local vLLM label platform-aware.
  • Remove [experimental] on DGX Spark and DGX Station.
  • Retain [experimental] on generic and unknown hosts.
  • Add unit coverage for managed and generic platform labels.
  • Update Local vLLM documentation to describe the platform-specific label.

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:
  • 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: This changes only the provider menu label based on the existing managed-platform set; The onboarding flow is unchanged.
  • 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
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification:
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
  • 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)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: zyang-dev 267119621+zyang-dev@users.noreply.github.com

Summary by CodeRabbit

  • Documentation

    • Updated local vLLM setup and tool-calling reliability guidance to clarify when the “experimental” label appears.
    • Clarified that generic hosts may show “Local vLLM [experimental]”, while DGX Spark and DGX Station do not.
  • Bug Fixes

    • Adjusted the onboarding provider menu so “Local vLLM (running…)” is marked experimental only on generic hosts, not on managed DGX platforms.
  • Tests

    • Updated and expanded menu-label coverage for generic vs DGX Spark/DGX Station scenarios.

Signed-off-by: zyang-dev <267119621+zyang-dev@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jul 10, 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: c93d0e4a-ff35-45ce-bc95-b06f11c02d87

📥 Commits

Reviewing files that changed from the base of the PR and between b82fb72 and cebd788.

📒 Files selected for processing (3)
  • docs/inference/local-compatible-inference-setup.mdx
  • docs/inference/tool-calling-reliability.mdx
  • src/lib/onboard/vllm-menu.test.ts
✅ Files skipped from review due to trivial changes (2)
  • docs/inference/local-compatible-inference-setup.mdx
  • docs/inference/tool-calling-reliability.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/lib/onboard/vllm-menu.test.ts

📝 Walkthrough

Walkthrough

Running vLLM onboarding labels now show [experimental] on generic hosts but not on DGX Spark or DGX Station. Tests cover both platform categories, and inference documentation reflects the updated provider label and clarification.

Changes

Platform-aware vLLM labeling

Layer / File(s) Summary
Conditional running-label behavior
src/lib/onboard/vllm-menu.ts, src/lib/onboard/vllm-menu.test.ts
Running vLLM labels include [experimental] on generic hosts and omit it on DGX Spark and DGX Station, with updated tests for both cases.
Documentation label updates
docs/inference/local-compatible-inference-setup.mdx, docs/inference/tool-calling-reliability.mdx
Documentation removes the experimental qualifier and clarifies the platform-specific labeling behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels: provider: vllm, area: onboarding, area: docs, platform: dgx-spark

🚥 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 matches the main change: removing the experimental vLLM label on managed platforms.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ 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 fix/vllm-experimental-label

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

@github-code-quality

github-code-quality Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage remains at 96%, unchanged from the main branch.

TypeScript / code-coverage/cli

The overall coverage in the fix/vllm-experimenta... branch remains at 77%, unchanged from the main branch.

Show a code coverage summary of the most impacted files.
File main fcc121d fix/vllm-experimenta... cebd788 +/-
src/lib/sandbox...rsion-scheme.ts 100% 73% -27%
src/lib/messagi...onfig-parser.ts 77% 62% -15%
src/lib/actions...de-preflight.ts 61% 51% -10%
src/lib/actions...ge-preflight.ts 94% 89% -5%
src/lib/adapters/http/probe.ts 93% 89% -4%
src/lib/trace.ts 90% 87% -3%
src/lib/agent/base-image.ts 85% 83% -2%
src/lib/sandbox...rce-identity.ts 89% 91% +2%
src/lib/security/redact.ts 95% 97% +2%
src/lib/state/config-io.ts 94% 96% +2%

Updated July 10, 2026 22:56 UTC
Code Coverage is in Public Preview. Learn more and provide us with your feedback.

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: onboard-repair, onboard-resume, cloud-onboard
Optional E2E: None

Dispatch hint: onboard-repair,onboard-resume

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • onboard-repair: Required by the deterministic risk plan for lifecycle-state coverage. The changed onboarding runtime code can affect convergence between onboarding choices, sandbox metadata, and live runtime state.
  • onboard-resume: Required by the deterministic risk plan for lifecycle-state coverage. This validates that interrupted or resumed onboarding paths still converge correctly after provider-menu/runtime changes.
  • cloud-onboard (high): Changed onboard, trace timing, scorecard, or E2E workflow code can affect cloud onboard wall-clock behavior and should refresh the trusted cloud-onboard trace timing signal.

Optional E2E

  • None.

New E2E recommendations

  • local-vllm-onboarding (medium): No existing E2E job was found that directly exercises the Local vLLM provider-menu/platform-label behavior or the running-vLLM selection path on generic Linux vs DGX Spark/Station profiles. Unit tests cover the helper, but a live/PTY onboarding check would catch regressions in how this menu is presented and selected in the real wizard.
    • Suggested test: Add a local-vllm-onboard-menu E2E target that drives the onboarding provider picker with a mocked or lightweight localhost vLLM /v1/models endpoint and verifies the Local vLLM label/selection behavior for generic Linux and DGX platform detection.

Dispatch hint

  • Workflow: .github/workflows/e2e.yaml
  • jobs input: onboard-repair,onboard-resume

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

E2E Target Recommendation

Required E2E targets: onboard-repair, onboard-resume
Optional E2E targets: None

Dispatch required E2E targets:

  • gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-repair
  • gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-resume

Workflow run

Full E2E target advisor summary

E2E Target Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E targets

  • onboard-repair: Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime.
    • Dispatch: gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-repair
  • onboard-resume: Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime.
    • Dispatch: gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-resume

Optional E2E targets

  • None.

Relevant changed files

  • src/lib/onboard/vllm-menu.ts

@github-actions

github-actions Bot commented Jul 10, 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 · 4 test follow-ups
Since last review: 0 prior items 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: Runtime validation
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 the `onboard-repair` E2E job for Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime. Matched files: `src/lib/onboard/vllm-menu.ts`.. Deterministic regression risks require live validation: lifecycle-state. Checked-in unit coverage directly covers the changed label behavior, but the deterministic risk plan flags the touched onboarding file for lifecycle-state runtime validation as a floor.
  • PRA-T2 Runtime validation — Run the `onboard-repair` E2E job for the touched onboarding surface to validate that onboarding and sandbox state still converge across persisted metadata, reported status, and the live runtime.. Deterministic regression risks require live validation: lifecycle-state. Checked-in unit coverage directly covers the changed label behavior, but the deterministic risk plan flags the touched onboarding file for lifecycle-state runtime validation as a floor.
  • PRA-T3 Runtime validation — Run the `onboard-resume` E2E job for Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime. Matched files: `src/lib/onboard/vllm-menu.ts`.. Deterministic regression risks require live validation: lifecycle-state. Checked-in unit coverage directly covers the changed label behavior, but the deterministic risk plan flags the touched onboarding file for lifecycle-state runtime validation as a floor.
  • PRA-T4 Runtime validation — Run the `onboard-resume` E2E job for the touched onboarding surface to validate that resume lifecycle behavior remains unchanged after the vLLM menu-label update.. Deterministic regression risks require live validation: lifecycle-state. Checked-in unit coverage directly covers the changed label behavior, but the deterministic risk plan flags the touched onboarding file for lifecycle-state runtime validation as a floor.

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.

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor (Nemotron Ultra) — 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 · 2 test follow-ups
Since last review: 0 prior items 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
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 the `onboard-repair` E2E job for Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime. Matched files: `src/lib/onboard/vllm-menu.ts`.. Deterministic regression risks require live validation: lifecycle-state. 13 unit tests exhaust the full decision matrix for buildVllmMenuEntries (vllmRunning × platform × experimental × vllmProfile × hasVllmImage × NEMOCLAW_PROVIDER). Function is pure with no external boundaries. Risk plan E2E jobs (onboard-repair, onboard-resume) are file-match heuristic artifacts; actual change surface has no I/O, state mutation, or external boundaries requiring live validation.
  • PRA-T2 Runtime validation — Run the `onboard-resume` E2E job for Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime. Matched files: `src/lib/onboard/vllm-menu.ts`.. Deterministic regression risks require live validation: lifecycle-state. 13 unit tests exhaust the full decision matrix for buildVllmMenuEntries (vllmRunning × platform × experimental × vllmProfile × hasVllmImage × NEMOCLAW_PROVIDER). Function is pure with no external boundaries. Risk plan E2E jobs (onboard-repair, onboard-resume) are file-match heuristic artifacts; actual change surface has no I/O, state mutation, or external boundaries requiring live validation.

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.

@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.

Actionable comments posted: 2

Caution

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

⚠️ Outside diff range comments (1)
src/lib/onboard/vllm-menu.test.ts (1)

23-36: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Add coverage for an explicit unknown platform.

The generic test omits platform, so it verifies the undefined case but not an unknown non-managed value. Add a case using the existing "linux" fixture and assert that the running label includes [experimental].

This is based on the PR objective and the existing non-managed "linux" platform fixture in this test file.

Also applies to: 38-58

🤖 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/onboard/vllm-menu.test.ts` around lines 23 - 36, Add a test case for
buildVllmMenuEntries using the existing "linux" platform fixture, with
vllmRunning true and the same generic-host settings, then assert the running
entry label includes "[experimental]" alongside "running".
🤖 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.

Inline comments:
In `@docs/inference/local-compatible-inference-setup.mdx`:
- Line 223: Split the two sentences in the vLLM onboarding text into separate
MDX source lines, and rewrite the second sentence to address the reader directly
using “you” language while preserving its meaning.

In `@docs/inference/tool-calling-reliability.mdx`:
- Line 107: Update the paragraph near the NemoClaw/vLLM guidance so each
sentence occupies its own MDX source line, and rewrite the second sentence using
direct second-person language (for example, instructing the reader what to
select) instead of third-person wording.

---

Outside diff comments:
In `@src/lib/onboard/vllm-menu.test.ts`:
- Around line 23-36: Add a test case for buildVllmMenuEntries using the existing
"linux" platform fixture, with vllmRunning true and the same generic-host
settings, then assert the running entry label includes "[experimental]"
alongside "running".
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 942ccfbc-1f8b-433b-bfcf-9bc5793ad848

📥 Commits

Reviewing files that changed from the base of the PR and between d643898 and b82fb72.

📒 Files selected for processing (4)
  • docs/inference/local-compatible-inference-setup.mdx
  • docs/inference/tool-calling-reliability.mdx
  • src/lib/onboard/vllm-menu.test.ts
  • src/lib/onboard/vllm-menu.ts

Comment thread docs/inference/local-compatible-inference-setup.mdx Outdated
Comment thread docs/inference/tool-calling-reliability.mdx Outdated
Signed-off-by: zyang-dev <267119621+zyang-dev@users.noreply.github.com>
@zyang-dev zyang-dev added v0.0.80 platform: dgx-spark Affects DGX Spark hardware or workflows platform: dgx-station Affects DGX Station hardware or workflows labels Jul 10, 2026
@prekshivyas prekshivyas self-assigned this Jul 10, 2026

@prekshivyas prekshivyas left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approving. Code is correct: buildVllmMenuEntries drops the [experimental] label on managed platforms (spark/station via MANAGED_VLLM_DEFAULT_PLATFORMS) only, consistent with the existing install-entry gating; pure function with unit tests covering the full decision matrix, and docs updated to match.

All CI green and both PR review advisors return merge_as_is with no blocking findings. Required E2E (onboard-repair, onboard-resume, cloud-onboard) dispatched: https://github.com/NVIDIA/NemoClaw/actions/runs/29129597200 — please let those go green before merge.

@github-actions

Copy link
Copy Markdown
Contributor

E2E Target Results — ✅ All requested jobs passed

Run: 29129597200
Workflow ref: fix/vllm-experimental-label
Requested targets: (default — all supported)
Requested jobs: onboard-repair,onboard-resume,cloud-onboard
Summary: 3 passed, 0 failed, 0 cancelled, 0 skipped

Job Result
cloud-onboard ✅ success
onboard-repair ✅ success
onboard-resume ✅ success

@cv
cv merged commit 32f6b8a into main Jul 10, 2026
123 of 126 checks passed
@cv
cv deleted the fix/vllm-experimental-label branch July 10, 2026 23:29
cv pushed a commit that referenced this pull request Jul 11, 2026
## Summary

Release-prep documentation for **v0.0.80**. Adds the `## v0.0.80`
section to `docs/about/release-notes.mdx` summarizing user-facing
changes since v0.0.79, each bullet linking to the relevant deeper page.

Produced via `nemoclaw-contributor-update-docs` (pre-tag path): scanned
`v0.0.79..HEAD`, applied the docs skip list (no violations), and
confirmed the 8 commits that already shipped in-PR docs are complete. No
new pages needed.

## Source summary

- #6507 -> `docs/about/release-notes.mdx`: Hermes v0.18 + Slack Block
Kit (rich rendering, digest-pinned base image).
- #6584 / #6616 -> `docs/about/release-notes.mdx`: host-local OpenRouter
runtime attribution adapter (port `11437`,
`NEMOCLAW_OPENROUTER_RUNTIME_ADAPTER_PORT`) and native Deep Agents
`openrouter` provider.
- #6210 / #6292 -> `docs/about/release-notes.mdx`: host corporate proxy
CA import into sandbox trust (`NEMOCLAW_CORPORATE_CA_BUNDLE`,
`NEMOCLAW_CORPORATE_CA_IMPORT`).
- #6624 / #6623 / #6656 -> `docs/about/release-notes.mdx`:
release-matched base-image selection, surfaced cluster-image build
diagnostics, preserved Nemotron profile registration.
- #6629 / #6637 -> `docs/about/release-notes.mdx`: bare `connect`
default-sandbox behavior and route-probe hardening.
- #6634 / #6626 / #6596 / #5569 / #6610 / #6655 ->
`docs/about/release-notes.mdx`: onboarding/recovery preservation,
stale-gateway-PID fix, installer backup message, vLLM label on managed
platforms.
- #6578 / #5670 -> `docs/about/release-notes.mdx`: automatic Hermes
light terminal skin and non-interactive `npx` MCP server startup.

## Verification

`npm run docs`: 0 errors, all internal links resolve (2 pre-existing
hidden-page warnings). `_build/` variants for OpenClaw, Hermes, and Deep
Agents all regenerate with the v0.0.80 section.

Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>

🤖 Generated with [Claude Code](https://claude.com/claude-code)


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

* **Documentation**
  * Added release notes for v0.0.80.
  * Documented Hermes upgrades, including Slack Block Kit rendering.
  * Added details on OpenRouter traffic routing and attribution headers.
* Documented improved proxy certificate handling and sandbox
reliability.
* Highlighted enhanced connection defaults, route-probing safeguards,
onboarding recovery, and terminal/MCP startup behavior.
  * Added references to relevant user-guide documentation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Hadar301 pushed a commit to Hadar301/NemoClaw-OpenShift that referenced this pull request Jul 12, 2026
…IDIA#6655)

<!-- markdownlint-disable MD041 -->
## Summary
<!-- 1-3 sentences: what this PR does and why. -->
Removes the experimental label from the running Local vLLM provider
entry on managed vLLM platforms. DGX Spark and DGX Station now show
Local vLLM as supported, while generic and unknown platforms retain the
experimental label.


## Changes
<!-- Bullet list of key changes. -->
- Make the running Local vLLM label platform-aware.
- Remove `[experimental]` on DGX Spark and DGX Station.
- Retain `[experimental]` on generic and unknown hosts.
- Add unit coverage for managed and generic platform labels.
- Update Local vLLM documentation to describe the platform-specific
label.

## 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
<!-- Check exactly one tests line and one docs line. Check other lines
when applicable. Add every requested justification or approval
reference. -->
- [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
- [ ] Docs not applicable — justification:
- [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: This changes only the
provider menu label based on the existing managed-platform set; The
onboarding flow is unchanged.
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Verification
<!-- Check each applicable item only when supported by the requested
evidence. Run targeted tests once per relevant change set and rerun
after later edits or hook autofixes that can affect the tested behavior.
Do not rerun hook-covered checks. -->
- [x] PR description includes the DCO sign-off declaration and every
commit appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run check:diff` passed when hooks were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — command/result or justification:
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result:
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only)
- [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)

---
<!-- DCO sign-off is required in this PR description, and every commit
must appear as Verified in GitHub. Run: git config user.name && git
config user.email -->
Signed-off-by: zyang-dev <267119621+zyang-dev@users.noreply.github.com>


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

* **Documentation**
* Updated local vLLM setup and tool-calling reliability guidance to
clarify when the “experimental” label appears.
* Clarified that generic hosts may show “Local vLLM [experimental]”,
while DGX Spark and DGX Station do not.

* **Bug Fixes**
* Adjusted the onboarding provider menu so “Local vLLM (running…)” is
marked experimental only on generic hosts, not on managed DGX platforms.

* **Tests**
* Updated and expanded menu-label coverage for generic vs DGX Spark/DGX
Station scenarios.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: zyang-dev <267119621+zyang-dev@users.noreply.github.com>
Hadar301 pushed a commit to Hadar301/NemoClaw-OpenShift that referenced this pull request Jul 12, 2026
## Summary

Release-prep documentation for **v0.0.80**. Adds the `## v0.0.80`
section to `docs/about/release-notes.mdx` summarizing user-facing
changes since v0.0.79, each bullet linking to the relevant deeper page.

Produced via `nemoclaw-contributor-update-docs` (pre-tag path): scanned
`v0.0.79..HEAD`, applied the docs skip list (no violations), and
confirmed the 8 commits that already shipped in-PR docs are complete. No
new pages needed.

## Source summary

- NVIDIA#6507 -> `docs/about/release-notes.mdx`: Hermes v0.18 + Slack Block
Kit (rich rendering, digest-pinned base image).
- NVIDIA#6584 / NVIDIA#6616 -> `docs/about/release-notes.mdx`: host-local OpenRouter
runtime attribution adapter (port `11437`,
`NEMOCLAW_OPENROUTER_RUNTIME_ADAPTER_PORT`) and native Deep Agents
`openrouter` provider.
- NVIDIA#6210 / NVIDIA#6292 -> `docs/about/release-notes.mdx`: host corporate proxy
CA import into sandbox trust (`NEMOCLAW_CORPORATE_CA_BUNDLE`,
`NEMOCLAW_CORPORATE_CA_IMPORT`).
- NVIDIA#6624 / NVIDIA#6623 / NVIDIA#6656 -> `docs/about/release-notes.mdx`:
release-matched base-image selection, surfaced cluster-image build
diagnostics, preserved Nemotron profile registration.
- NVIDIA#6629 / NVIDIA#6637 -> `docs/about/release-notes.mdx`: bare `connect`
default-sandbox behavior and route-probe hardening.
- NVIDIA#6634 / NVIDIA#6626 / NVIDIA#6596 / NVIDIA#5569 / NVIDIA#6610 / NVIDIA#6655 ->
`docs/about/release-notes.mdx`: onboarding/recovery preservation,
stale-gateway-PID fix, installer backup message, vLLM label on managed
platforms.
- NVIDIA#6578 / NVIDIA#5670 -> `docs/about/release-notes.mdx`: automatic Hermes
light terminal skin and non-interactive `npx` MCP server startup.

## Verification

`npm run docs`: 0 errors, all internal links resolve (2 pre-existing
hidden-page warnings). `_build/` variants for OpenClaw, Hermes, and Deep
Agents all regenerate with the v0.0.80 section.

Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>

🤖 Generated with [Claude Code](https://claude.com/claude-code)


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

* **Documentation**
  * Added release notes for v0.0.80.
  * Documented Hermes upgrades, including Slack Block Kit rendering.
  * Added details on OpenRouter traffic routing and attribution headers.
* Documented improved proxy certificate handling and sandbox
reliability.
* Highlighted enhanced connection defaults, route-probing safeguards,
onboarding recovery, and terminal/MCP startup behavior.
  * Added references to relevant user-guide documentation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

platform: dgx-spark Affects DGX Spark hardware or workflows platform: dgx-station Affects DGX Station hardware or workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants