Skip to content

docs: clarify sub-agent sandbox prerequisites - #5402

Closed
WilliamK112 wants to merge 2 commits into
NVIDIA:mainfrom
WilliamK112:wk/docs-sub-agent-prereq-5077
Closed

docs: clarify sub-agent sandbox prerequisites#5402
WilliamK112 wants to merge 2 commits into
NVIDIA:mainfrom
WilliamK112:wk/docs-sub-agent-prereq-5077

Conversation

@WilliamK112

@WilliamK112 WilliamK112 commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Summary

Clarifies that the sub-agent sandbox config commands require an onboarded, running sandbox on the host before the container lookup can succeed. The example now fails fast with a clear message when the sandbox container cannot be found.

Related Issue

Fixes #5077

Changes

  • Add the Quickstart/running-sandbox prerequisite before the Docker-driver config commands.
  • Explain that the commands discover the sandbox container from the openshell.ai/sandbox-name Docker label.
  • Add a guard that stops before docker exec when SANDBOX_CTR is empty.

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

  • Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
  • Targeted tests pass for changed behavior
  • Full npm test passes (broad runtime changes only)
  • 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)

Verification run:

  • npx prek run --from-ref origin/main --to-ref HEAD
  • npm run docs (passed with 0 errors; Fern reported existing warnings/upgrade notice)

Signed-off-by: WilliamK112 164879897+WilliamK112@users.noreply.github.com

Summary by CodeRabbit

  • Documentation
    • Updated the setup guide with clearer prerequisites, including completing the Quickstart and ensuring the sandbox is onboarded before running commands.
    • Improved container discovery instructions to clarify reliance on the sandbox Docker label and added validation with an explicit error when no matching running sandbox container is found.

@copy-pr-bot

copy-pr-bot Bot commented Jun 13, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Jun 13, 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: 36cae9c3-90d7-4446-8b7d-4554ed2e6bdb

📥 Commits

Reviewing files that changed from the base of the PR and between 575301c and 2dc00f4.

📒 Files selected for processing (1)
  • docs/inference/set-up-sub-agent.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/inference/set-up-sub-agent.mdx

📝 Walkthrough

Walkthrough

The sub-agent setup documentation gains a prerequisite paragraph before the docker exec commands, instructing readers to complete the Quickstart and have a sandbox running. The SANDBOX_CTR discovery shell snippet is extended with a guard that prints an error and exits if no matching running container is found.

Changes

Sub-agent setup documentation

Layer / File(s) Summary
Prerequisite note and SANDBOX_CTR empty-check guard
docs/inference/set-up-sub-agent.mdx
Adds a prerequisite paragraph before the docker exec block noting that the Quickstart must be completed and a sandbox must be onboarded and running. Extends the SANDBOX_CTR discovery snippet with a non-empty check that exits with an error message when no running container matching the openshell.ai/sandbox-name label is found.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#5247: Modifies the same docs/inference/set-up-sub-agent.mdx file, updating the Docker-driver sandbox container discovery flow using the openshell.ai/sandbox-name label and SANDBOX_CTR-based commands that this PR now guards.

Suggested labels

area: docs, area: sandbox

Poem

🐇 Hop hop, the doc now says:
"Run Quickstart first, or else amaze —
No container found? We'll shout and bail,
No silent errors down the trail!
A prereq note to light the way,
Keeps confused devs from going astray!" 🌟

🚥 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 accurately summarizes the main change: clarifying sandbox prerequisites in sub-agent documentation.
Linked Issues check ✅ Passed The PR addresses the primary objective from issue #5077 by adding a prerequisite note and improving sandbox container discovery error handling.
Out of Scope Changes check ✅ Passed All changes are directly scoped to addressing the missing prerequisite issue identified in #5077; no unrelated modifications are present.
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

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

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

🧹 Nitpick comments (1)
docs/inference/set-up-sub-agent.mdx (1)

54-58: 💤 Low value

Wrap this prerequisite in a Fern callout.

This is a prerequisite note in an MDX page, so it should use <Note> or <Warning> instead of plain prose. Also, rewrite “is onboarded” in active voice and keep the sentence on one line. As per coding guidelines, use Fern callout components for callouts in MDX pages, use active voice, and keep one sentence per line in source files.

Proposed shape
- Before you run the `docker exec` commands in this section, finish the
- [Quickstart](../get-started/quickstart) and make sure the target sandbox is
- onboarded and running on this host. The commands discover the sandbox container
- from the `openshell.ai/sandbox-name` Docker label, so the sandbox container must
- exist before `SANDBOX_CTR` can resolve.
+<Note>
+Before you run the `docker exec` commands in this section, finish the [Quickstart](../get-started/quickstart) and start a sandbox on this host. The commands discover the sandbox container from the `openshell.ai/sandbox-name` Docker label, so the sandbox container must exist before `SANDBOX_CTR` can resolve.
+</Note>
🤖 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/inference/set-up-sub-agent.mdx` around lines 54 - 58, Wrap the
prerequisite text that begins with "Before you run the `docker exec` commands"
in a Fern callout component (either `<Note>` or `<Warning>`). Within the
callout, rewrite the phrase "is onboarded and running" to use active voice
instead (change to "onboard and run" or similar active construction).
Additionally, ensure each sentence in the callout is kept on one line in the
source file to follow the coding guidelines for MDX pages.

Source: Coding guidelines

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

Nitpick comments:
In `@docs/inference/set-up-sub-agent.mdx`:
- Around line 54-58: Wrap the prerequisite text that begins with "Before you run
the `docker exec` commands" in a Fern callout component (either `<Note>` or
`<Warning>`). Within the callout, rewrite the phrase "is onboarded and running"
to use active voice instead (change to "onboard and run" or similar active
construction). Additionally, ensure each sentence in the callout is kept on one
line in the source file to follow the coding guidelines for MDX pages.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: c1227c86-7e5c-4b8d-b328-0fedc70201d9

📥 Commits

Reviewing files that changed from the base of the PR and between b0b1362 and 575301c.

📒 Files selected for processing (1)
  • docs/inference/set-up-sub-agent.mdx

Signed-off-by: WilliamK112 <164879897+WilliamK112@users.noreply.github.com>
@WilliamK112
WilliamK112 force-pushed the wk/docs-sub-agent-prereq-5077 branch from 575301c to 2dc00f4 Compare June 14, 2026 00:11
…rereq-5077

# Conflicts:
#	docs/inference/set-up-sub-agent.mdx
@WilliamK112

Copy link
Copy Markdown
Contributor Author

Merged current upstream/main into this branch to clear the conflict.

After the update, the PR now shows 0 changed files because the same sub-agent setup guidance appears to have landed upstream via #5521. So there is no remaining code/docs delta from this branch; leaving this note here so the current PR state is easier to interpret.

@wscurran wscurran added area: docs Documentation, examples, guides, or docs build area: sandbox OpenShell sandbox lifecycle, runtime, config, or recovery labels Jun 23, 2026
@wscurran

Copy link
Copy Markdown
Contributor

✨ Thanks for adding the Quickstart/running-sandbox prerequisite before the Docker-driver config commands. This proposes a way to clarify sub-agent sandbox setup by failing fast with a clear message when the sandbox container cannot be found.


Related open issues:

@WilliamK112

Copy link
Copy Markdown
Contributor Author

Closing this stale PR because it now has 0 changed files after the same sub-agent prerequisite guidance landed upstream via #5521, as noted above. This keeps the open PR queue focused on branches with an active reviewable delta.

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: sandbox OpenShell sandbox lifecycle, runtime, config, or recovery

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[All Platforms][Docs] Set Up Sub-Agents doc: missing prerequisite for running NemoClaw sandbox / openshell-cluster-nemoclaw container

2 participants