Skip to content

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

New issue
New issue
Closed
Bug
#5216
Closed
[Brev][Onboard] Hermes Agent deploys with OpenClaw runtime instead of Hermes from API Catalog Try Now flow#5211
Bug
#5216
Assignees
jyaunchesjason-ma-nv
Labels
NV QABugs found by the NVIDIA QA Teamarea: integrationsThird-party service integration behaviorarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flowintegration: hermesHermes integration behaviorplatform: brevAffects Brev hosted development environmentsprovider: nvidiaNVIDIA inference endpoint, NIM, or NVIDIA provider behavior

Description

@hulynn
hulynn
opened on Jun 11, 2026

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

Activity

  1. hulynn
    added
    NV QABugs found by the NVIDIA QA Team
    UATIssues flagged for User Acceptance Testing.
    status: triage
    on Jun 11, 2026
  2. hulynn
    added the
    Bug
    issue type on Jun 11, 2026
  3. jason-ma-nv
    self-assigned this
    on Jun 11, 2026

  4. jason-ma-nv commented on Jun 11, 2026

    @jason-ma-nv
    jason-ma-nv
    on Jun 11, 2026
    Collaborator

    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.

  5. ahunnargikar-nvidia
    assigned
    jyaunches
    on Jun 11, 2026

  6. hulynn commented on Jun 12, 2026

    @hulynn
    hulynn
    on Jun 12, 2026
    ContributorAuthor

    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.

    Image
  7. wscurran
    added
    area: integrationsThird-party service integration behavior
    area: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flow
    integration: hermesHermes integration behavior
    platform: brevAffects Brev hosted development environments
    provider: nvidiaNVIDIA inference endpoint, NIM, or NVIDIA provider behavior
    v0.0.56
    and removed
    status: triage
    on Jun 12, 2026

  8. jyaunches commented on Jun 12, 2026

    @jyaunches
    jyaunches
    on Jun 12, 2026
    Contributor

    Update: cross-repo check in brevdev/nemoclaw-image

    I checked the Brev image/onboard repo to see whether this is already fixed there or if the remaining fix is upstream/platform-side.

    Findings:

    • brevdev/nemoclaw-image main already includes generic Hermes launchable/onboard support via f724bd4 feat: add Hermes launchable onboarding for NemoClaw v0.0.55 (#27).
    • The image/onboard flow supports both agents, but it is selection-driven, not automatically pinned to Hermes:
      • onboard-ui/lib/onboard-agents.ts defines both openclaw and hermes, but DEFAULT_AGENT_ID = "openclaw".
      • onboard-ui/app/onboard/page.tsx initializes the UI from that default.
      • onboard-ui/app/api/onboard/route.ts falls back to openclaw when agent is missing/invalid.
      • onboard-ui/lib/services/nemoclaw.ts passes the selected agent through as NEMOCLAW_AGENT.
      • scripts/gcp-image-provision.sh / brev-quickstart honor NEMOCLAW_AGENT=openclaw|hermes and switch Hermes ports/model/runtime behavior accordingly.
    • I did not find the API Catalog/Try Now mapping, Hermes card config, or launchable ID (env-3Azt0aYgVNFEuz7opyx3gscmowS) checked into nemoclaw-image.

    Conclusion: nemoclaw-image has the Hermes capability, but the observed behavior still looks like the upstream API Catalog/Brev launchable path is entering the generic/default OpenClaw flow without forcing agent=hermes / NEMOCLAW_AGENT=hermes.

    Likely required platform-side fix:

    1. Point the Hermes API Catalog Try Now card at a dedicated Hermes launchable, or
    2. Configure the existing launchable/card path to pass/pin Hermes explicitly, e.g. NEMOCLAW_AGENT=hermes or an equivalent supported preselection mechanism.

    Possible repo-side hardening in nemoclaw-image:

    Also, the latest report of Unable to find your Access application! from build.nvidia.com looks like a separate platform/catalog routing/access issue rather than a NemoClaw runtime-selection bug.

  9. cv
    added a commit that references this issue on Jun 13, 2026

    fix(install): surface silent OpenClaw runtime fallback in launchable …

    ed82777
  10. cv
    closed this as completedin #5216on Jun 13, 2026

  11. hulynn commented on Jun 15, 2026

    @hulynn
    hulynn
    on Jun 15, 2026
    ContributorAuthor

    Remove the test-blocker keyword:
    Steps:

    Image
    1. Click Deploy.
    Image
    1. Click NemoClaw.
    Image

    Result:

    The agent runtime is OpenClaw, not Hermes.

    Image

    However, after switching to the Hermes agent manually, I can use the Hermes TUI successfully.

  12. hulynn
    removed
    UATIssues flagged for User Acceptance Testing.
    on Jun 15, 2026
  13. cjagwani
    added a commit that references this issue on Jun 22, 2026

    fix(platform): tighten matrix claims with evidence for each row

    61f78c6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

NV QABugs found by the NVIDIA QA Teamarea: integrationsThird-party service integration behaviorarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flowintegration: hermesHermes integration behaviorplatform: brevAffects Brev hosted development environmentsprovider: nvidiaNVIDIA inference endpoint, NIM, or NVIDIA provider behavior

Type

Bug

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions