Skip to content

docs: clarify quickstart non-interactive setup #6514

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
cv merged 5 commits into from
Jul 9, 2026
Merged

docs: clarify quickstart non-interactive setup #6514

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e5fa52d
docs: clarify quickstart non-interactive setup
miyoungc Jul 9, 2026
b6697ee
docs: point quickstart to provider section
miyoungc Jul 9, 2026
e0d1a46
Merge branch 'main' into codex/resolve-5631-quickstart-docs
miyoungc Jul 9, 2026
4c6b443
test: remove quickstart docs regression test
miyoungc Jul 9, 2026
c630433
Merge branch 'main' into codex/resolve-5631-quickstart-docs
miyoungc Jul 9, 2026
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
2 changes: 1 addition & 1 deletion docs/get-started/quickstart.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ curl -fsSL https://www.nvidia.com/nemoclaw.sh | \
bash
```

The example above uses the NVIDIA Endpoints path. Set `NEMOCLAW_PROVIDER` and the matching API key variable for your chosen path (see the provider table above), and set `NEMOCLAW_SANDBOX_NAME` so the run does not depend on a default left behind by a previous, possibly interrupted, onboard session.
The example above uses the NVIDIA Endpoints path. Set `NEMOCLAW_PROVIDER` and the matching API key variable for your chosen path (see [Choose an Inference Provider](#choose-an-inference-provider)), and set `NEMOCLAW_SANDBOX_NAME` so the run does not depend on a default left behind by a previous, possibly interrupted, onboard session.

If a scripted installer rerun finds a failed onboarding session, choose whether to discard the saved state with `--fresh` or retry it with `nemoclaw onboard --resume`.
For the recovery commands, refer to [Previous onboarding session failed](../reference/troubleshooting#previous-onboarding-session-failed).
Expand Down
Loading