Skip to content

docs: split starter prompt platform instructions - #7061

Merged
apurvvkumaria merged 19 commits into
mainfrom
codex/split-starter-prompt-assets
Jul 17, 2026
Merged

docs: split starter prompt platform instructions#7061
apurvvkumaria merged 19 commits into
mainfrom
codex/split-starter-prompt-assets

Conversation

@miyoungc

@miyoungc miyoungc commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

Move platform-specific Express install guidance out of the general starter prompt so non-DGX users do not receive irrelevant DGX instructions. The starter prompt now loads focused raw Markdown assets only after detecting DGX Spark, DGX Station, or Windows WSL.

Changes

  • Add focused prompt assets for DGX Spark, DGX Station, and Windows WSL Express installation.
  • Replace inline platform instructions in the canonical starter prompt with conditional raw Markdown links.
  • Preserve platform-specific provider, model, policy, approval, storage, and validation safeguards in the matching assets.
  • Document the prompt-asset ownership convention and update contract tests to prevent platform details from returning to the general prompt.

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: Manual review confirmed the split preserves Express policy, approval, model, storage, and validation safeguards; focused contract tests protect the routing and required instructions.
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Verification

  • PR description includes a Signed-off-by: line 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 — npx vitest run test/starter-prompt-docs.test.ts (15 passed)
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — not applicable to this focused documentation change
  • 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) — build passed; Fern reported two existing warnings
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only) — raw prompt assets include SPDX headers and intentionally are not Fern pages

Signed-off-by: Miyoung Choi miyoungc@nvidia.com

Summary by CodeRabbit

  • New Features
    • Added platform-specific “Express” guidance for DGX Spark, DGX Station, and Windows WSL, with preset runtime/model setup and a streamlined confirmation flow.
    • Express-mode now follows revision-pinned platform instruction assets and treats acceptance as final approval to reduce additional permission prompts.
  • Documentation
    • Expanded contribution guidelines for structuring, pinning, and referencing conditional platform prompt assets.
    • Updated the starter prompt’s onboarding and routing to improve platform detection and load the correct platform instructions.
  • Tests
    • Added end-to-end checks for pinned asset integrity, correct asset routing, and Express installer behavior.

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
@miyoungc miyoungc added the area: docs Documentation, examples, guides, or docs build label Jul 17, 2026
@miyoungc miyoungc self-assigned this Jul 17, 2026
@copy-pr-bot

copy-pr-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

The starter prompt now routes platform-specific Express instructions through dedicated DGX Spark, DGX Station, and Windows WSL Markdown assets. Platform detection, provider and policy handling, contribution guidance, and tests were updated to validate asset loading and installer defaults.

Changes

Platform Express asset routing

Layer / File(s) Summary
Platform Express instruction assets
docs/CONTRIBUTING.md, docs/resources/prompt-assets/*
Adds focused platform assets defining Express prompts, environment variables, approval flows, and fallback provider behavior, with pinned-asset workflow guidance.
Starter prompt detection and asset routing
docs/resources/starter-prompt.md
Tightens environment and hardware detection, loads one matching platform asset, delegates local-runtime guidance, and updates provider and policy handling.
Asset mapping and behavior validation
test/starter-prompt-docs.test.ts
Maps assets to local paths and revision-pinned raw URLs, and tests digests, routing, content constraints, and Express installer defaults.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Environment
  participant StarterPrompt
  participant PlatformAsset
  participant Installer
  Environment->>StarterPrompt: detect OS, WSL, and hardware
  StarterPrompt->>PlatformAsset: load one matching asset
  PlatformAsset->>Installer: apply accepted platform settings
  PlatformAsset-->>StarterPrompt: continue with fallback providers if declined
Loading

Suggested labels: platform: dgx-station

🚥 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: splitting platform-specific instructions out of the starter prompt into separate docs.
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 unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/split-starter-prompt-assets

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

@github-actions

Copy link
Copy Markdown
Contributor

@github-code-quality

github-code-quality Bot commented Jul 17, 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 codex/split-starter-... branch remains at 80%, unchanged from the main branch.

Show a code coverage summary of the most impacted files.
File main bbf335d codex/split-starter-... d496ee0 +/-
src/lib/sandbox...rce-identity.ts 91% 91% 0%
src/lib/inferen...er-lifecycle.ts 65% 71% +6%
src/lib/inferen...lama/process.ts 50% 100% +50%

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

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — Informational

Advisor assessment: Informational / high confidence
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions
Status: No actionable findings remain in the canonical review ledger.

Model lanes

  • GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Model comparison: normalized findings match; normalized E2E selections differ; severity counts match.

Nemotron output stays in workflow artifacts and does not change the assessment above.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: None

1 optional E2E recommendation
  • docs-validation

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

@miyoungc miyoungc added the area: onboarding Onboarding FSM, provider setup, sandbox launch, or first-run flow label Jul 17, 2026
@sandl99
sandl99 marked this pull request as ready for review July 17, 2026 04:10

@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: 4

Caution

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

⚠️ Outside diff range comments (1)
docs/resources/starter-prompt.md (1)

218-223: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Do not re-request final approval for Express.

The loaded platform assets treat the Express confirmation as approval and explicitly skip the later final-permission prompt, but Line 222 unconditionally asks for final permission. This can produce duplicate consent prompts and break the non-interactive Express contract. Scope the summary and final-permission rule to non-Express flows, or explicitly exempt Express here.

🤖 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 `@docs/resources/starter-prompt.md` around lines 218 - 223, Update the
installation approval flow around the final-permission step to skip that prompt
for Express selections, since Express confirmation already constitutes approval.
Keep the summary and final-permission request for non-Express installations, and
preserve setting NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE and NEMOCLAW_YES only
after the applicable approval.
🤖 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/CONTRIBUTING.md`:
- Around line 134-135: Document in docs/CONTRIBUTING.md that all platform asset
links use one shared immutable commit SHA or release tag, and specify who
updates the revision and how related assets are updated together. In
docs/resources/starter-prompt.md, replace the mutable main references with the
same pinned revision used by the starter prompt.

In `@docs/resources/prompt-assets/dgx-station.md`:
- Around line 10-14: Add the established third-party-software disclosure used by
the other platform assets before the Express confirmation question in the DGX
Station prompt. Preserve the existing Express defaults and choices, and add a
regression assertion verifying the disclosure appears before acceptance and
before setting NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE.

In `@test/starter-prompt-docs.test.ts`:
- Around line 676-689: Extend the assertions in the expressAssets loop to
require NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 in every asset source. Also add
behavioral coverage that verifies Express proceeds with third-party software
approval rather than pausing or failing at that prompt.
- Around line 24-37: Update the promptAssets validation and its corresponding
assertions in the starter prompt test so each configured URL is explicitly
associated with the asset loaded from its matching path. Verify the observable
routing result for every platform entry, rather than independently checking that
paths and URLs appear in the prompt, preventing swapped platform mappings from
passing.

---

Outside diff comments:
In `@docs/resources/starter-prompt.md`:
- Around line 218-223: Update the installation approval flow around the
final-permission step to skip that prompt for Express selections, since Express
confirmation already constitutes approval. Keep the summary and final-permission
request for non-Express installations, and preserve setting
NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE and NEMOCLAW_YES only after the applicable
approval.
🪄 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: 4484b9a8-2c64-427a-bb46-1c2aff29becb

📥 Commits

Reviewing files that changed from the base of the PR and between ff5877b and 143b050.

📒 Files selected for processing (6)
  • docs/CONTRIBUTING.md
  • docs/resources/prompt-assets/dgx-spark.md
  • docs/resources/prompt-assets/dgx-station.md
  • docs/resources/prompt-assets/windows-wsl.md
  • docs/resources/starter-prompt.md
  • test/starter-prompt-docs.test.ts

Comment thread docs/CONTRIBUTING.md
Comment thread docs/resources/prompt-assets/dgx-station.md Outdated
Comment thread test/starter-prompt-docs.test.ts
Comment thread test/starter-prompt-docs.test.ts Outdated
@sandl99 sandl99 added area: install Install, setup, prerequisites, or uninstall flow v0.0.86 labels Jul 17, 2026
@sandl99 sandl99 self-assigned this Jul 17, 2026
@apurvvkumaria apurvvkumaria self-assigned this Jul 17, 2026

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

Requesting changes at exact head 7953cac5cbeeb8c2ac5f882e72085caad292b03c.

  1. The DGX Station asset currently labels a provider-preseeded DeepSeek path as Express, but that path skips Station Express host preparation. docs/resources/prompt-assets/dgx-station.md sets NEMOCLAW_PROVIDER=install-vllm before invoking the installer. In scripts/install.sh, a preselected provider bypasses maybe_offer_express_install, so activate_express_install never records the Station platform and ensure_station_express_host does not run the pinned driver, Docker, NVIDIA Container Toolkit, CDI, or reboot/resume preparation. A fresh Station can therefore follow these instructions, bypass required preparation, and still be told it selected the maintained Express flow. Please either route unprepared hosts through the official --station-deepseek Express entry point, or explicitly scope this provider-preseeded path to an already-prepared host and fail closed when the documented readiness prerequisites are absent. It should not be described as the general Station Express path while host automation is disabled.

  2. The final confirmation omits security-relevant host effects. This asset makes its first confirmation final and suppresses the later summary, but the prompt currently discloses only the model/container, storage, and Deferred status. Before Choices:, disclose every applicable host mutation, possible reboot/resume behavior, and that Docker-group membership grants root-equivalent control. If the path is changed to prepared-host-only, disclose that host automation will not run and require the readiness checks before accepting. Add regression assertions that these disclosures precede both the choice and the non-interactive acceptance variables.

Also tighten the immutable-asset contract: document the atomic shared-revision update procedure and make CI prove each local platform asset still matches the content at its pinned revision. The current tests validate URL shape and local prose independently, so a future local edit can silently drift from what the starter prompt actually downloads.

The automated checks are green, but they did not cross-check this prompt against the installer's control flow; these are release-blocking documentation and safety issues.

apurvvkumaria and others added 4 commits July 17, 2026 04:00
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>

@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: 1

🤖 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/resources/prompt-assets/dgx-station.md`:
- Around line 20-22: Update the documentation around the --check and --verify
modes to call them “non-repairing” rather than “read-only.” Explicitly disclose
that --verify starts GPU test containers through CDI and Docker, which may
create Docker state, consume GPU and storage resources, and produce logs, before
requesting permission; preserve the existing pinned-image and no-pull behavior.
🪄 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: 0978104f-ab22-4a4d-ac50-86fafde4d5a1

📥 Commits

Reviewing files that changed from the base of the PR and between 7953cac and 96daed6.

📒 Files selected for processing (4)
  • docs/CONTRIBUTING.md
  • docs/resources/prompt-assets/dgx-station.md
  • docs/resources/starter-prompt.md
  • test/starter-prompt-docs.test.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/resources/starter-prompt.md

Comment thread docs/resources/prompt-assets/dgx-station.md Outdated
apurvvkumaria and others added 5 commits July 17, 2026 04:58
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
@ericksoa
ericksoa requested a review from apurvvkumaria July 17, 2026 17:40
@apurvvkumaria
apurvvkumaria enabled auto-merge (squash) July 17, 2026 17:44
@apurvvkumaria
apurvvkumaria merged commit 522ad1e into main Jul 17, 2026
54 checks passed
@apurvvkumaria
apurvvkumaria deleted the codex/split-starter-prompt-assets branch July 17, 2026 17:49
miyoungc added a commit that referenced this pull request Jul 20, 2026
<!-- markdownlint-disable MD041 -->
## Summary

Align the DGX Station coding-agent instructions with the versioned
installer. The ordinary Station Express path now remains authoritative
for its Nemotron Ultra default, while DeepSeek remains available only
through the installer’s explicit `--station-deepseek` override.

## Changes

- [#7061](#7061) ->
`docs/resources/prompt-assets/dgx-station.md`: Replace the DeepSeek-only
provider-preseeded path with the installer’s Ultra-default and
DeepSeek-override contract.
- Delegate Station qualification, host preparation, third-party notice,
Express summary, and reboot or login resume to the selected maintained
release’s installer.
- Stop the coding-agent path from pre-setting provider, model,
non-interactive, approval, or Express-skip variables, and stop it from
running the Station preparation helper separately.
- Preserve Ultra’s approximately 352 GB disclosure, shared Station
host-safety boundaries, the temporary metadata override guard, and
Deferred support status.
- Pin every starter-prompt platform asset URL to the immutable asset
commit and update its SHA-256 contract.
- Update focused tests to require both installer-supported Station model
outcomes and reject the former DeepSeek-only path.

## Type of Change

- [ ] Code change (feature, bug fix, or refactor)
- [ ] Code change with doc updates
- [x] 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
- [ ] 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:
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## DGX Station Hardware Evidence

- [ ] Tested on DGX Station
- Tested commit: Not applicable; this PR does not change
`scripts/prepare-dgx-station-host.sh` or runtime behavior.
- Station profile/scenario: Not applicable.
- Result: Not applicable.
- Supporting evidence: Installer behavior is covered by the focused
automated Express tests below.

## Verification

- [x] PR description includes a `Signed-off-by:` line 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 — `npx vitest run
test/starter-prompt-docs.test.ts test/install-express-prompt.test.ts`
(88 passed, 1 skipped)
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result: Not run; this is a focused
documentation contract change.
- [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) — passed
with 0 errors and 1 Fern warning
- [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: Miyoung Choi <miyoungc@nvidia.com>


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

## Summary by CodeRabbit

* **Documentation**
* Updated DGX Station guidance to use the official Station Express
installer after hardware detection.
* Added support for Nemotron Ultra by default and DeepSeek V4 Flash as
an explicit option.
* Clarified installer consent, interactive prompts, reboot/resume
behavior, and fallback provider selection.
* Refreshed platform instruction links and clarified installer-specific
prompt handling.

* **Tests**
* Updated validation for revised Station Express instructions, consent
messaging, and asset revisions.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation, examples, guides, or docs build area: install Install, setup, prerequisites, or uninstall flow area: onboarding Onboarding FSM, provider setup, sandbox launch, or first-run flow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants