-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Open
Labels
Getting StartedUse this label to identify setup, installation, or onboarding issues.Use this label to identify setup, installation, or onboarding issues.bugSomething isn't workingSomething isn't workingpriority: highImportant issue that should be resolved in the next releaseImportant issue that should be resolved in the next release
Description
Description
Can't get past stage 2 of nemoclaw onboard. It gets hung up and I've tried different solutions for past 1.5 hours.

I tried new terminal also and adding api key, path, etc. Talked to claude and gpt. nothing worked for this issue.
The openshell container did work though. But no sandbox to connect assistant
Reproduction Steps
- Run nemo claw onboard on Mac Studio
- Hung up after step 2
Environment
-Docker
Logs
nemoclaw onboard
NemoClaw Onboarding
===================
[1/7] Preflight checks
──────────────────────────────────────────────────
✓ Docker is running
✓ Container runtime: docker-desktop
✓ openshell CLI: openshell 0.0.11
Cleaning up previous NemoClaw session...
✓ Previous session cleaned up
✓ Port 8080 available (OpenShell gateway)
✓ Port 18789 available (NemoClaw dashboard)
✓ Apple GPU detected: Apple M1 Max (24 cores), 32768 MB unified memory
ⓘ NIM requires NVIDIA GPU — will use cloud inference
[2/7] Starting OpenShell gateway
──────────────────────────────────────────────────
✓ Checking Docker
✓ Downloading gateway
✓ Initializing environment
✓ Starting gateway
✓ Gateway ready
Name: nemoclaw
Endpoint: https://127.0.0.1:8080
✓ Active gateway set to 'nemoclaw'Checklist
- I confirmed this bug is reproducible
- I searched existing issues and this is not a duplicate
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Getting StartedUse this label to identify setup, installation, or onboarding issues.Use this label to identify setup, installation, or onboarding issues.bugSomething isn't workingSomething isn't workingpriority: highImportant issue that should be resolved in the next releaseImportant issue that should be resolved in the next release