Description

[Description]
The current public Brev launchable flow appears to default to tracking the main branch rather than pinning to a stable release.
From the launch script:

PLUGIN_REPO="${PLUGIN_REPO:-NVIDIA/NemoClaw}"
PLUGIN_REF="${PLUGIN_REF:-main}"
COMMUNITY_REF="${COMMUNITY_REF:-${COMMUNITY_BRANCH:-main}}"

For a public launchable experience, tracking main can make behavior drift over time and may introduce instability or unexpected regressions for users.

Source: https://raw.githubusercontent.com/NVIDIA/OpenShell-Community/refs/heads/feat/brev-nemoclaw-plugin/brev/launch-nemoclaw.sh
[Environment]

• Device: Brev instance Ubuntu 22.04.5 LTS
• Node.js: v22.22.1
• Docker: Docker Engine 29.3.0
• OpenShell CLI: 0.0.10
• NemoClaw: v0.0.2
• OpenClaw: 2026.3.11 (29dc654)

[Steps to Reproduce]

1. Open https://build.nvidia.com/nemoclaw and click "Try Early Preview" button to open brev launchable like https://brev.nvidia.com/launchable/deploy/now?launchableID=env-3Azt0aYgVNFEuz7opyx3gscmowS
2. Click on "Deploy Launchable" button

[Expected Behavior]

• default the public Brev launchable link to a stable released version instead of main
• ideally pin to a release tag or another immutable/stable reference

[Actual Behavior]
Default with main branch

Bug Details

[NVB# 6038835]

[NVB#6038835]