[Brev][Onboard] Hermes Agent deploys with OpenClaw runtime instead of Hermes from API Catalog Try Now flow

[hulynn]

Description

When using the Try Now button from the NemoClaw for Hermes Agent API Catalog card to deploy a Brev launchable, the resulting agent page reports RUNTIME = OpenClaw instead of Hermes / NemoHermes. The Hermes agent selected from the API Catalog appears to be wired to the OpenClaw runtime in the Brev launchable.

Environment

Device:        Brev cloud instance (qa-team org)
OS:            Linux (Brev managed; exact distro not captured)
Architecture:  x86_64
OpenClaw:      Reported as RUNTIME on the agent-live page (version string not shown)
API Catalog:   https://build.nvidia.com/nvidia/nemoclaw-for-hermes-agent/nemoclawcard
Launchable:    https://brev.nvidia.com/launchable/deploy/now?launchableID=env-3Azt0aYgVNFEuz7opyx3gscmowS
Agent page:    https://nemoclaw-p22df9k6d.brevlab.com/onboard
Model shown:   Nemotron 3 Super 120B
Provider:      NVIDIA Cloud

Steps to Reproduce

1. Open https://build.nvidia.com/nvidia/nemoclaw-for-hermes-agent/nemoclawcard
2. Click Try Now (top-right)
3. On the Brev launchable page, click Deploy Launchable
4. After the instance is provisioned, click the NemoClaw (Go to instance page) button on the right-hand status panel
5. The brev-spawned agent UI completes CONFIGURE → SETUP → LAUNCH and shows YOUR AGENT IS LIVE
6. Inspect the RUNTIME field on the LAUNCH page

Expected Result

Since the entry point is the NemoClaw for Hermes Agent API Catalog card, the deployed agent should be a Hermes agent. RUNTIME should show Hermes (or NemoHermes), not OpenClaw.

Actual Result

RUNTIME  = OpenClaw
AGENT    = my-assistant
MODEL    = Nemotron 3 Super 120B
PROVIDER = NVIDIA Cloud

The Hermes agent type selected on the API Catalog is silently deployed as an OpenClaw runtime instead of Hermes.

Logs

Not captured. Bug is observable from the agent-live page UI. Three screenshots attached to NVBug:

• API Catalog Try Now button (build.nvidia.com/nvidia/nemoclaw-for-hermes-agent/nemoclawcard)
• Brev launchable deploy page (brev.nvidia.com)
• Agent live page showing RUNTIME = OpenClaw (nemoclaw-p22df9k6d.brevlab.com/onboard)

---

NVB#6304576

[jason-ma-nv]

Root cause: shared Brev launchable, not a code bug

The NemoClaw for Hermes Agent API Catalog Try Now card points at Brev launchable env-3Azt0aYgVNFEuz7opyx3gscmowS — the same launchable the repo documents as the OpenClaw web-UI launchable (docs/deployment/brev-web-ui.mdx).

When that launchable boots, it runs the installer without exporting NEMOCLAW_AGENT. With the variable unset:

• resolveAgentName() (src/lib/agent/defs.ts) defaults to openclaw
• install.sh (case "${NEMOCLAW_AGENT:-openclaw}") brands as OpenClaw

→ RUNTIME = OpenClaw, even though the Hermes card was selected. The repo code is already correct and honors NEMOCLAW_AGENT=hermes (covered by tests in src/lib/agent/defs.test.ts).

Required fix (platform-side) ⚠️

The launchable definition lives on the Brev / build.nvidia.com platform, outside this repo, so the actual fix must happen there:

1. Preferred: create a dedicated Hermes launchable for the NemoClaw for Hermes Agent card that exports NEMOCLAW_AGENT=hermes in its startup environment, or
2. Update the existing launchable env-3Azt0aYgVNFEuz7opyx3gscmowS to export NEMOCLAW_AGENT=hermes before invoking the installer.

The installer entry point then becomes the documented Hermes form:

curl -fsSL https://www.nvidia.com/nemoclaw.sh | NEMOCLAW_AGENT=hermes bash

In-repo follow-up

PR #5213 (docs-only) has been closed — it could not change deploy behavior. A separate PR will add a defensive guard so the installer loudly warns when a non-interactive/launchable deploy lands on the default OpenClaw runtime, instead of silently falling back. That makes a misconfigured Hermes launchable detectable at deploy time rather than only from the live page.

cc: launchable owner — please action the platform change above.

[hulynn]

I get this error from build.nvidia.com > blueprints > NemoClaw for Herms Agent: Unable to find your Access application!
It appears that you have attempted to reach an invalid URL. Please navigate to your application url.