Description

[Description]
Starting with NemoClaw v0.0.34, the curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash installer path fails during onboarding with a hard error about interactive third‑party software acceptance, even in environments where v0.0.33 completed successfully with interactive prompts.
The new version introduces a stricter requirement that the third‑party software notice must be accepted from a real TTY, but this change is not called out in the high‑level install docs and breaks the previously working, documented curl|bash command in common Docker/remote setups.
The error message suggests using --yes-i-accept-third-party-software or NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1, yet there is no example showing how to integrate these with the curl|bash installer, and the default install command now exits instead of guiding the user through acceptance as in v0.0.33.

Workaround:

• Run the installer from a TTY‑attached session that NemoClaw recognizes as interactive (for example, local terminal or ssh with a real TTY), or
• Use a non‑interactive install with explicit acceptance, e.g.:bash NEMOCLAW_NON_INTERACTIVE=1 \ NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 \ curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash

  as implied by the troubleshooting docs for non‑interactive environments.

[Environment]

• Host: DGX Spark / remote Linux environment where NemoClaw detects Container runtime: docker (single‑node OpenShell gateway at port 8080)
• NemoClaw v0.0.33: curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash completes successfully with interactive onboarding (sandbox name, API key, model selection, third‑party acceptance)
• NemoClaw v0.0.34: same installer URL, same host, same shell
• Shell: bash, invoked in a non‑login, non‑graphical session (SSH / Spark shell)
• Docker: running and healthy; OpenShell cluster container ghcr.io/nvidia/openshell/cluster:0.0.36 already started by NemoClaw

[Steps to Reproduce]

1. Start from an environment where:
   • NemoClaw detects Container runtime: docker during onboarding,
   • Docker and the OpenShell gateway are running (e.g., DGX Spark / similar setup).
2. With NemoClaw v0.0.33 available behind https://www.nvidia.com/nemoclaw.sh, run:bash curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash

   2.1. Observe: installer runs, onboarding is interactive, and you can accept third‑party software terms in‑line.

3. 
   Upgrade to v0.0.34 (or wait until the installer URL serves v0.0.34).
4. 
   In the same environment and shell configuration, run again:bash
   curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
5. 
   Result: installer exits withtext
   [ERROR] Interactive third-party software acceptance requires a TTY. Re-run in a terminal or pass --yes-i-accept-third-party-software (or set NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1).

   and does not proceed with onboarding.

[Expected Result]

• The documented one‑liner curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash should continue to work in the same environments where it worked in v0.0.33, including common Docker/remote shells, by presenting an interactive third‑party software prompt when possible.
• If stricter TTY requirements are introduced, the release notes and install docs should explicitly call this out as a breaking change, and the default installer command should either:
  • Detect that it cannot get a TTY and fall back to a clear, supported non‑interactive path (with full example using --yes-i-accept-third-party-software / NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1), or
  • Fail with an error that is integrated into the docs, including explicit examples for curl|bash usage in non‑interactive environments.

[Actual Result]

• With v0.0.34, running the same curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash in the same environment now fails early with Interactive third-party software acceptance requires a TTY…, even though v0.0.33 succeeded and showed the acceptance prompt.
• NemoClaw is treating the environment as non‑interactive and refuses to proceed with onboarding unless the user already knows to set --yes-i-accept-third-party-software or NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1, which is not documented in the quickstart path for this installer.
• This behavior effectively breaks the primary documented install command in common Docker/remote setups and constitutes a regression from v0.0.33, with no visible warning in the high‑level docs or release notes that this TTY requirement changed.

Bug Details

[NVB#6142864]