Skip to content

docs: update onboarding quickstarts#4451

Merged
miyoungc merged 1 commit into
mainfrom
docs/fix-bugs
May 28, 2026
Merged

docs: update onboarding quickstarts#4451
miyoungc merged 1 commit into
mainfrom
docs/fix-bugs

Conversation

@miyoungc

@miyoungc miyoungc commented May 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

Update the onboarding docs for the current v0.0.53 flow so users see the correct installer, quickstart, and Hermes setup guidance.

Related Issue

Fixes #4418
Fixes #4417
Fixes #4413
Fixes #4412

Changes

  • Added nemoclaw onboard --resume and --fresh guidance to the command reference.
  • Updated the OpenClaw quickstart for non-TTY installer acceptance and the current review, web search, messaging, sandbox, and policy ordering.
  • Added Hermes Docker prerequisite notes and headless CHAT_UI_URL guidance for exposing the Hermes API on port 8642.

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)

Verification

  • npx prek run --all-files passes
  • npm test passes
  • Tests added or updated for new or changed behavior
  • No secrets, API keys, or credentials committed
  • Docs updated for user-facing behavior changes
  • 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)

Notes:

  • Commit and push hooks passed for the staged doc changes.
  • npm run docs completed with 0 errors and 1 existing Fern theme contrast warning.
  • npx prek run --all-files failed in unrelated existing CLI/e2e tests: two test timeouts and one sandbox connect assertion.

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

Summary by CodeRabbit

  • Documentation
    • Enhanced Hermes quickstart with Docker prerequisites, including Linux and macOS setup steps
    • Added headless/remote access guidance for exposing the Hermes API externally
    • Clarified third-party software acceptance process for piped installer in TTY and non-TTY environments
    • Documented --resume and --fresh flags for resumable and fresh onboarding runs
    • Updated onboarding wizard flow descriptions for improved clarity

Review Change Stack

@miyoungc miyoungc self-assigned this May 28, 2026
@coderabbitai

coderabbitai Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request updates NemoClaw's onboarding documentation across three files to address gaps in Hermes prerequisites, non-TTY installation guidance, and wizard flow descriptions. Changes add Docker setup requirements for Hermes, remote access configuration via CHAT_UI_URL, clarify third-party acceptance for piped installs, synchronize wizard flow across docs, and document previously undocumented CLI flags.

Changes

NemoClaw Onboarding Documentation Updates

Layer / File(s) Summary
Hermes Docker prerequisites and remote access guidance
docs/get-started/quickstart-hermes.mdx
Adds Docker as a prerequisite with Linux (service, docker group, newgrp) and macOS (Docker Desktop/Colima) setup steps; introduces CHAT_UI_URL configuration for headless/remote browser scenarios, explaining port 8642 forwarding, /v1 path handling, SSH port forwarding alternatives, and Hermes-specific bearer token authentication (not OpenClaw dashboard tokens).
Hermes wizard flow and review description
docs/get-started/quickstart-hermes.mdx
Updates wizard flow descriptions to clarify that inference provider, model, credentials, and sandbox name are collected before the review summary, and adjusts post-selection review wording to align with the provider/model confirmation step.
Third-party software acceptance for non-TTY installs
docs/get-started/quickstart.mdx
Expands guidance on third-party software notice acceptance when using the piped nvidia.com/nemoclaw.sh installer in non-TTY environments (SSH, CI/CD); documents NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 environment variable and bash -s -- --yes-i-accept-third-party-software syntax with multiple copy-pastable curl variants and environment variable placement cautions.
Onboarding wizard flow documentation synchronization
docs/get-started/quickstart.mdx, docs/reference/commands.mdx
Synchronizes descriptions across quickstart and commands reference to consistently describe the wizard flow: provider/model collection → review summary → OpenShell inference registration → optional web search/messaging (ordered before policy selection) → sandbox build/start → OpenClaw setup → network policy tier/presets. Updates the sample Review configuration output to reflect "API key: configured for OpenShell gateway registration" wording instead of the prior staged COMPATIBLE_API_KEY line.
CLI documentation for --resume and --fresh flags
docs/reference/commands.mdx
Documents nemoclaw onboard's --resume and --fresh flags, explaining that onboarding records resumable progress, how conflicts with recovery-time flags are handled, installer forwarding behavior, and mutual exclusivity between the two options.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • ericksoa
  • cv

Poem

🐰 A rabbit hops through docs so clear,
Docker prerequisites, headless cheer!
Third-party notes for pipes and SSH,
Wizard flows sync—no more thrash!
Flags documented, onboard complete,
Fresh and resume make guidance neat!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: update onboarding quickstarts' clearly summarizes the main change—updating multiple documentation files for onboarding guidance.
Linked Issues check ✅ Passed All code requirements from linked issues are addressed: #4418 adds --fresh documentation, #4417 addresses quickstart sync issues, #4413 adds Docker prerequisite and CHAT_UI_URL guidance, #4412 documents non-TTY NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE usage.
Out of Scope Changes check ✅ Passed All changes in the PR remain within scope—updates to three documentation files (quickstart.mdx, quickstart-hermes.mdx, commands.mdx) directly address the four linked issues without introducing unrelated modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/fix-bugs

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


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

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. No E2E is recommended because this PR changes documentation only and cannot alter runtime installer/onboarding behavior, sandbox lifecycle, credentials, security boundaries, network policy enforcement, inference routing, deployment, or assistant user flows. Existing PR docs checks such as Docs / Link Check and Docs / CLI Parity are the appropriate coverage for these files.

Optional E2E

  • None.

New E2E recommendations

  • None.

@github-actions

Copy link
Copy Markdown
Contributor

E2E Scenario Advisor Recommendation

Required scenario E2E: None
Optional scenario E2E: None

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

  • None. No scenario workflow, scenario metadata, scenario runtime, or validation-suite files changed.

Optional scenario E2E

  • None.

Relevant changed files

  • None.

@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

🧹 Nitpick comments (2)
docs/get-started/quickstart-hermes.mdx (1)

23-23: ⚡ Quick win

Use active voice and direct second-person phrasing in reader instructions.

Line 23 uses passive construction, and Line 39 addresses “a headless host” instead of directly addressing the reader. Please rewrite both lines in active voice with “you.”

As per coding guidelines, "Active voice required." and "Second person ('you') when addressing the reader."

Also applies to: 39-39

🤖 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/get-started/quickstart-hermes.mdx` at line 23, Rewrite the two passive
sentences to active second-person phrasing: change "Docker must be installed,
running, and reachable from the current shell before Hermes onboarding can build
the sandbox image." to something like "You must install Docker, start it, and
ensure it’s reachable from your shell before Hermes onboarding builds the
sandbox image." Also replace the "a headless host" phrasing (the sentence around
Line 39) with direct "you" addressing (e.g., "If you are on a headless host,
...") so both sentences use active voice and second person.
docs/reference/commands.mdx (1)

103-103: ⚡ Quick win

Remove unnecessary bold emphasis on routine prose.

**policy tier** reads as emphasis rather than a UI label or warning; use plain text here to match docs style consistency.

As per coding guidelines, “Unnecessary bold on routine instructions … Bold is reserved for UI labels, parameter names, and genuine warnings.”

🤖 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/reference/commands.mdx` at line 103, Remove the unnecessary bold markup
around the phrase "**policy tier**" in the documentation sentence so it reads as
plain text "policy tier"; locate the string "**policy tier**" in the
docs/reference/commands.mdx content and replace the bolded markup with
unformatted text to match the project's style guidelines for routine
instructions and UI label usage.
🤖 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/get-started/quickstart-hermes.mdx`:
- Around line 43-47: Update the command-only fenced block in
quickstart-hermes.mdx to be a copyable shell snippet: replace the
triple-backtick "console" fence with "bash" (or "sh"), remove leading "$" prompt
markers from each line so the three lines are plain commands, and ensure the
closing triple-backticks remain; locate the block containing NEMOCLAW_AGENT,
CHAT_UI_URL, and the curl command to apply this change.

---

Nitpick comments:
In `@docs/get-started/quickstart-hermes.mdx`:
- Line 23: Rewrite the two passive sentences to active second-person phrasing:
change "Docker must be installed, running, and reachable from the current shell
before Hermes onboarding can build the sandbox image." to something like "You
must install Docker, start it, and ensure it’s reachable from your shell before
Hermes onboarding builds the sandbox image." Also replace the "a headless host"
phrasing (the sentence around Line 39) with direct "you" addressing (e.g., "If
you are on a headless host, ...") so both sentences use active voice and second
person.

In `@docs/reference/commands.mdx`:
- Line 103: Remove the unnecessary bold markup around the phrase "**policy
tier**" in the documentation sentence so it reads as plain text "policy tier";
locate the string "**policy tier**" in the docs/reference/commands.mdx content
and replace the bolded markup with unformatted text to match the project's style
guidelines for routine instructions and UI label usage.
🪄 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: a9c9da09-267c-4939-88ce-6ed5ce705508

📥 Commits

Reviewing files that changed from the base of the PR and between d3590c9 and e415087.

📒 Files selected for processing (3)
  • docs/get-started/quickstart-hermes.mdx
  • docs/get-started/quickstart.mdx
  • docs/reference/commands.mdx

Comment on lines +43 to +47
```console
$ export NEMOCLAW_AGENT=hermes
$ export CHAT_UI_URL="https://hermes.example.com:8642"
$ curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
```

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.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use a copyable shell code block format for command-only examples.

This block is copyable commands, so it should be tagged bash/sh and omit $ prompt markers instead of using console.

Suggested diff
-```console
-$ export NEMOCLAW_AGENT=hermes
-$ export CHAT_UI_URL="https://hermes.example.com:8642"
-$ curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
-```
+```bash
+export NEMOCLAW_AGENT=hermes
+export CHAT_UI_URL="https://hermes.example.com:8642"
+curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
+```

As per coding guidelines, "Copyable CLI code blocks must use language-specific tags such as bash, sh, or powershell, and must not include prompt markers such as $."

🤖 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/get-started/quickstart-hermes.mdx` around lines 43 - 47, Update the
command-only fenced block in quickstart-hermes.mdx to be a copyable shell
snippet: replace the triple-backtick "console" fence with "bash" (or "sh"),
remove leading "$" prompt markers from each line so the three lines are plain
commands, and ensure the closing triple-backticks remain; locate the block
containing NEMOCLAW_AGENT, CHAT_UI_URL, and the curl command to apply this
change.

@github-actions

Copy link
Copy Markdown
Contributor

PR Review Advisor

Findings: 1 needs attention, 1 worth checking, 0 nice ideas
Top item: Update quickstart.mdx for #4417’s model list and Local Ollama suffix

Review findings

🛠️ Needs attention

🔎 Worth checking

  • Remote Hermes CHAT_UI_URL guidance should warn about exposing the bearer-protected API (docs/get-started/quickstart-hermes.mdx:39): The new Hermes headless-host guidance tells users to set a non-loopback `CHAT_UI_URL` and notes that NemoClaw binds the forward for remote access. Existing code intentionally uses a non-loopback URL to bind the forward on `0.0.0.0:<port>`, so this can expose the Hermes OpenAI-compatible API beyond localhost. The docs mention bearer-token authentication but do not explicitly warn users to protect the endpoint and token.
    • Recommendation: Add a warning similar to the remote-dashboard docs: only expose the Hermes API through trusted/TLS-protected tunnels or access-controlled networks, keep the bearer token secret, and avoid internet/shared-network exposure unless the endpoint is intentionally protected.
    • Evidence: `docs/get-started/quickstart-hermes.mdx` adds `CHAT_UI_URL="https://hermes.example.com:8642"\` and says NemoClaw binds the forward for remote access. `src/lib/dashboard/contract.ts` sets the forward target to `0.0.0.0:<port>` for non-loopback `CHAT_UI_URL`; `agents/hermes/manifest.yaml` declares bearer-token API auth on port 8642.

🌱 Nice ideas

  • None.

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.

@miyoungc miyoungc merged commit 2c826d9 into main May 28, 2026
33 checks passed
@miyoungc miyoungc deleted the docs/fix-bugs branch May 28, 2026 18:33
@wscurran wscurran added area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance and removed documentation labels Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment