Merged
Conversation
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Contributor
📝 WalkthroughWalkthroughRefines several docs: updates inference credential validation flow, ties OpenClaw pairing disablement to non-loopback Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/reference/commands.md (1)
351-375:⚠️ Potential issue | 🟡 MinorDocument
--from-fileand--from-direxclusivity and batch-failure behavior.The new flags are documented, but the page does not mention that combining both flags is invalid, and
--from-dirstops on the first failing preset. Adding this avoids confusing failures in automation.Proposed doc addition
| `--from-file <path>` | Apply a custom preset YAML file instead of a built-in preset | | `--from-dir <path>` | Apply every custom preset YAML file in a directory in lexicographic order | | `--yes`, `--force` | Skip the confirmation prompt (requires a preset name, `--from-file`, or `--from-dir`) | | `--dry-run` | Preview the endpoints a preset would open without applying changes | +`--from-file` and `--from-dir` are mutually exclusive. +`--from-dir` reads only `.yaml` and `.yml` files and aborts on the first failed preset.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/reference/commands.md` around lines 351 - 375, Update the policy-add CLI docs to state that the flags `--from-file` and `--from-dir` are mutually exclusive (cannot be used together) and to document the batch-failure behavior of `--from-dir` (it stops processing on the first failing preset), referencing the `policy-add` command and the flags `--from-file`, `--from-dir`, and `--yes`/`--force` so readers know the limitation and that automation should handle failure/ordering accordingly.
🧹 Nitpick comments (1)
docs/reference/troubleshooting.md (1)
499-499: Formatgit cloneas inline code in the heading.Line 499 uses a CLI command phrase in prose form. Use inline code formatting for command names in headings too for consistency.
As per coding guidelines, "CLI commands, file paths, flags, parameter names, and values must use inline
codeformatting."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/reference/troubleshooting.md` at line 499, Update the heading "### Git clone fails with a certificate verification error" to format the CLI command as inline code by changing it to "### `git clone` fails with a certificate verification error"; locate the heading text in the docs (search for the exact string) and replace it so that the command `git clone` uses inline backticks to comply with the guideline that CLI commands, file paths, flags and parameters use code formatting.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/reference/troubleshooting.md`:
- Around line 503-509: The verification command omits GIT_SSL_CAPATH even though
the text mentions it; update the env check used in the troubleshooting doc (the
grep pattern used in the `env | grep -E '...'` line) to include GIT_SSL_CAPATH
alongside SSL_CERT_FILE, GIT_SSL_CAINFO, CURL_CA_BUNDLE, and REQUESTS_CA_BUNDLE
so the command actually verifies all listed CA-related variables.
---
Outside diff comments:
In `@docs/reference/commands.md`:
- Around line 351-375: Update the policy-add CLI docs to state that the flags
`--from-file` and `--from-dir` are mutually exclusive (cannot be used together)
and to document the batch-failure behavior of `--from-dir` (it stops processing
on the first failing preset), referencing the `policy-add` command and the flags
`--from-file`, `--from-dir`, and `--yes`/`--force` so readers know the
limitation and that automation should handle failure/ordering accordingly.
---
Nitpick comments:
In `@docs/reference/troubleshooting.md`:
- Line 499: Update the heading "### Git clone fails with a certificate
verification error" to format the CLI command as inline code by changing it to
"### `git clone` fails with a certificate verification error"; locate the
heading text in the docs (search for the exact string) and replace it so that
the command `git clone` uses inline backticks to comply with the guideline that
CLI commands, file paths, flags and parameters use code formatting.
🪄 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: 6fc5ce9d-e072-4faf-864a-8435b6bf1d13
📒 Files selected for processing (10)
.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md.agents/skills/nemoclaw-user-deploy-remote/SKILL.md.agents/skills/nemoclaw-user-reference/references/commands.md.agents/skills/nemoclaw-user-reference/references/troubleshooting.mddocs/deployment/deploy-to-remote-gpu.mddocs/inference/inference-options.mddocs/project.jsondocs/reference/commands.mddocs/reference/troubleshooting.mddocs/versions1.json
Comment on lines
+503
to
+509
| It also forwards standard CA bundle variables for subprocesses, including `GIT_SSL_CAPATH`, `CURL_CA_BUNDLE`, and `REQUESTS_CA_BUNDLE`. | ||
|
|
||
| If Git still reports `server certificate verification failed`, reconnect to the sandbox and check that the CA variables are present: | ||
|
|
||
| ```console | ||
| $ env | grep -E 'SSL_CERT_FILE|GIT_SSL_CAINFO|CURL_CA_BUNDLE|REQUESTS_CA_BUNDLE' | ||
| ``` |
Contributor
There was a problem hiding this comment.
Include GIT_SSL_CAPATH in the verification command.
Line 503 documents GIT_SSL_CAPATH, but Line 508 does not verify it. That can hide the exact missing variable in failing environments.
Proposed doc fix
-$ env | grep -E 'SSL_CERT_FILE|GIT_SSL_CAINFO|CURL_CA_BUNDLE|REQUESTS_CA_BUNDLE'
+$ env | grep -E 'SSL_CERT_FILE|GIT_SSL_CAINFO|GIT_SSL_CAPATH|CURL_CA_BUNDLE|REQUESTS_CA_BUNDLE'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/reference/troubleshooting.md` around lines 503 - 509, The verification
command omits GIT_SSL_CAPATH even though the text mentions it; update the env
check used in the troubleshooting doc (the grep pattern used in the `env | grep
-E '...'` line) to include GIT_SSL_CAPATH alongside SSL_CERT_FILE,
GIT_SSL_CAINFO, CURL_CA_BUNDLE, and REQUESTS_CA_BUNDLE so the command actually
verifies all listed CA-related variables.
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
cv
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes user-facing docs for the last 24 hours of merged NemoClaw history and bumps the docs metadata to 0.0.29, the next version after v0.0.28. The updates are limited to behavior supported by merged PR descriptions and diffs.
Changes
docs/reference/commands.md: documentednemoclaw <name> policy-add --from-fileand--from-dir, including custom preset review guidance, from feat(policy): support custom preset files via --from-file / --from-dir (closes #2039) #2077 / commit7720b175.docs/deployment/deploy-to-remote-gpu.md: clarified that non-loopbackCHAT_UI_URLdisables OpenClaw device pairing for remote browser-only deployments, from fix: auto-disable device auth for non-loopback URLs (#2341) #2449 / commitf5ee8a4d.docs/inference/inference-options.md: documented provider-aware credential retry validation and the NVIDIA-onlynvapi-prefix check, from fix(onboard): don't enforce nvapi- prefix on non-NVIDIA API keys #2389 / commit6f7f0c6d.docs/inference/switch-inference-providers.md: documentedNEMOCLAW_INFERENCE_INPUTSfor text/image-capable model metadata baked intoopenclaw.json, from fix(onboard): propagate NEMOCLAW_INFERENCE_INPUTS to baked openclaw.json #2441 / commitf4391892.docs/reference/troubleshooting.md: added the Git certificate verification entry for proxy CA propagation throughGIT_SSL_CAINFO,GIT_SSL_CAPATH,CURL_CA_BUNDLE, andREQUESTS_CA_BUNDLE, from fix(sandbox): export GIT_SSL_CAINFO so git trusts proxy CA #2345 / commitfa0dc1ab.docs/versions1.jsonanddocs/project.json: promoted docs version0.0.29;docs/versions1.jsonomits unpublished0.0.26,0.0.27, and0.0.28entries..agents/skills/nemoclaw-user-*: regenerated derived user skill references from the updated docs.d392ec07, fix(sandbox): include generate-openclaw-config.py in optimized build context #2565 /a3231049, fix(uninstall): source nvm before npm uninstall to find the correct p… #1965 /db1ef3ca, fix(inference): migrate GLM-5 model references to GLM-5.1 (#1744) #1990 /db665834, refactor(onboard): extract modules from onboard.ts (Steps 1-3, rebased) #2495 /7da86fa3, feat(cli): add gateway-token command to retrieve sandbox auth token #2496 /3192f4f4, fix(sandbox): strip forward-proxy fields when rewriting to https.request #2490 /8c209058, fix(onboard): auto-patch cluster image for Docker 26+ overlayfs nested mount break #2487 /1f615e2f, perf(dockerfile): move token injection to late layer to preserve build cache #2483 /5653d33a, fix(security): revert gateway auth token externalization #2482 /31c782c0, chore(deps): bump OpenClaw from 2026.4.2 to 2026.4.9 #2464 /23bb5703, fix(sandbox): fix non-root gateway startup and add crash safety net #2472 /a54f9a34, and fix(install): refuse to auto-resume a failed onboarding session #2437 /6bc860d7.7b76df6btouched the experimental sandbox config path listed indocs/.docs-skip; fix(hermes): set file permissions so sandbox user can read copied files #2466 /cc15689ctouched a skipped term and CI-only sandbox image files.Type of Change
Verification
npx prek run --all-filespassesnpm testpasses — failed locally in installer-integration tests and one onboard helper timeout; the doc-scoped hook test projects passed underprek.make docsbuilds without warnings (doc changes only) — build succeeded, but local Sphinx emitted the existing version-switcher file read message.AI Disclosure
Signed-off-by: Miyoung Choi miyoungc@nvidia.com
Summary by CodeRabbit
New Features
Improvements
Documentation