nemoclaw-user-deploy-remote

Deploy NemoClaw to a remote GPU instance and onboard the sandbox.

Updated May 29, 2026
One-click install
npx skills add https://github.com/rblake2320/vigil --skill nemoclaw-user-deploy-remote-rblake2320
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-user-deploy-remote
Source: https://github.com/rblake2320/vigil/tree/main/.claude/skills/nemoclaw-user-deploy-remote
Command: npx skills add https://github.com/rblake2320/vigil --skill nemoclaw-user-deploy-remote-rblake2320

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables deploying NemoClaw to a remote GPU instance, including support for the Brev compatibility path and the standard onboard flow, so teams can deploy, onboard, and migrate away from local deployments without manual SSH setup.

Core Features & Use Cases

  • Remote deployment and provisioning of NemoClaw on GPU-backed hosts
  • Onboarding flow to configure gateways, providers, and sandbox setup
  • Migration guidance from legacy nemo deploy wrappers and Brev-based workflows
  • Quickstart-oriented guidance for remote installations

Quick Start

Provision the remote VM, run the NemoClaw installer on the host, and then run onboard to create and start the sandbox.

Frequently Asked Questions about nemoclaw-user-deploy-remote

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy NemoClaw to a remote GPU instance?

Deploy NemoClaw remotely by provisioning a GPU-backed VM, running the standard installer on the host, and executing the onboard flow to configure and start the sandbox without manual SSH setup.

What do I need to set up before remote deploying a GPU sandbox?

Remote GPU sandbox deployment requires the Brev CLI, valid provider credentials, and authentication tokens before provisioning the remote host and initiating the standard NemoClaw onboard flow.

How do I migrate from legacy nemoclaw deploy wrappers to remote deployment?

Migrate from legacy nemoclaw deploy wrappers by following the provided guidance to transition Brev-based workflows into the standard remote installer and onboard flow for GPU instances.

Does NemoClaw remote deployment work with Brev compatibility paths?

NemoClaw remote deployment explicitly supports the Brev compatibility path, allowing teams to provision remote GPU VMs and onboard sandboxes while migrating away from local deployments.

What is the standard onboard flow for a remote NemoClaw sandbox?

The onboard flow configures gateways, providers, and sandbox setup after running the NemoClaw installer on the remote host, creating and starting the sandbox environment automatically.