Skip to content

[All Platforms][Docs] quickstart 'openclaw agent --local' first-interaction command rejected by sandbox #3698

@hulynn

Description

@hulynn

Description

The get-started/quickstart.html doc lists this as the canonical first command a new user runs after nemoclaw <name> connect to verify the sandbox is responding:

openclaw agent --agent main --local -m "hello" --session-id test

Running this command inside the sandbox produces an immediate refusal — the --local flag is explicitly forbidden inside NemoClaw sandboxes because it bypasses the gateway's security protections (secret scanning, network policy, inference auth). The very first command a new user runs to "say hello" therefore fails out of the box, contradicting the doc and giving a very bad first impression.

Environment

Host:              macOS 26.1
Architecture:      arm64 (Apple Silicon M4)
Container runtime: Colima
NemoClaw:          v0.0.44
OpenShell CLI:     0.0.39
OpenClaw:          2026.4.24 (inside sandbox)
Sandboxes tested:  nv-test (Option 1 NVIDIA), ollama-test (Option 7 Local Ollama)
                   Both reject the same way — the rejection is sandbox-side,
                   not provider-specific.

Steps to Reproduce

  1. Complete nemoclaw onboard to build a sandbox (any provider).
  2. Follow get-started/quickstart.html exactly:
    nemoclaw <name> connect
    openclaw agent --agent main --local -m "hello" --session-id test
  3. Observe the sandbox rejects the command and prints the guidance to drop --local.

Expected Result

The doc command runs successfully and prints a model reply (e.g. "hello" or a greeting). The expected user experience at this step is "see the sandbox say hello back."

Actual Result

The sandbox prints this rejection and exits non-zero:

Error: 'openclaw agent --local' is not supported inside NemoClaw sandboxes.
The --local flag bypasses the gateway's security protections (secret scanning,
network policy, inference auth) and can crash the sandbox.
Instead, run without --local to use the gateway's managed inference route:
  openclaw agent --agent main -m "hello"

Root Cause Analysis

The runtime rejection is correct and intentional — --local bypassing gateway protections in a sandbox would defeat the security model. The bug is purely on the docs side. get-started/quickstart.html shows the user a command the sandbox itself explicitly forbids. The connect banner already gives the correct guidance ("run openclaw tui"), so the quickstart doc is the outlier. The --session-id test argument is also unnecessary and worth dropping for clarity.

Proposed Fix

Update get-started/quickstart.html to use the sandbox-supported form:

openclaw agent --agent main -m "hello"

…i.e. drop --local and --session-id test.

Optionally add a one-line caveat near the example: "Inside a NemoClaw sandbox, --local is rejected on purpose because it bypasses the gateway's security and network policy. Use the form above to route through the gateway." Cross-reference reference/openclaw-cli.html so users who want to understand the flag find the explanation.

Affected docs / pages

  • Confirmed: get-started/quickstart.html (the "say hello" step at end of quickstart).
  • Not in scope (already covered by NVB#6186072): deploy-to-remote-gpu.html, monitor-sandbox-activity.html.

This bug is specifically for the quickstart page since it's the first page a new user reads.

Logs

Full transcript and other 11 findings from this validation run at nemoclaw-test/nemoclaw-doc-validation-2026-05-18.md (section "Critical #11").


NVB#6187087

Metadata

Metadata

Assignees

No one assigned

    Labels

    NV QABugs found by the NVIDIA QA Teamarea: docsDocumentation, examples, guides, or docs buildarea: installInstall, setup, prerequisites, or uninstall flowarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flow

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions