Description
When onboarding NemoClaw with the Model Router provider, the model-router-venv virtual environment is created and contains python3, but the expected .fingerprint file is not created, breaking the intended venv version tracking and rebuild detection.
Environment
OS: macOS
Architecture: arm64 (assumed for recent MacBook Pro; adjust if x86_64)
Node.js: v22.22.3
npm: 10.9.8
Docker: Docker version 29.2.1, build a5c7197
OpenShell CLI: openshell 0.0.44
NemoClaw: nemoclaw v0.0.55
OpenClaw: OpenClaw 2026.5.22 (a374c3a)
Steps to Reproduce
Pre-conditions:
- NemoClaw CLI installed (v0.0.37+; tested with v0.0.54).
- Docker running.
Steps:
- Verify
install.sh does not set up Model Router:
grep -c "model-router\|pip3.*install" ~/.nemoclaw/source/scripts/install.sh
- Run NemoClaw onboard and select Model Router as the provider (if available):
nemoclaw onboard --fresh --name model-router-test
- Walk through provider/model selection.
- When prompted for provider, choose Model Router (if present in the menu).
- Complete the rest of the onboarding flow.
- Confirm the Model Router virtual environment exists:
ls ~/.nemoclaw/model-router-venv/bin/python3
- Check for the fingerprint file in the Model Router venv:
cat ~/.nemoclaw/model-router-venv/.fingerprint
Expected Result
grep in step 1 returns 0 matches, confirming install.sh does not pre-setup Model Router or run pip3 for it (Model Router venv should be created during onboard).
nemoclaw onboard completes successfully, and selecting Model Router creates a model-router-venv under ~/.nemoclaw.
- The file
~/.nemoclaw/model-router-venv/bin/python3 exists, indicating the venv is populated.
- The file
~/.nemoclaw/model-router-venv/.fingerprint exists and contains a version fingerprint to track the venv's build, enabling NemoClaw to detect when the venv is stale and trigger a rebuild.
Actual Result
Steps and outputs from an actual run on macOS:
Checking for python3 inside the Model Router venv:
$ ls ~/.nemoclaw/model-router-venv/bin/python3
/Users/pshevate/.nemoclaw/model-router-venv/bin/python3
Attempting to read .fingerprint inside the Model Router venv:
$ cat ~/.nemoclaw/model-router-venv/.fingerprint
cat: /Users/pshevate/.nemoclaw/model-router-venv/.fingerprint: No such file or directory
The Model Router venv and python3 binary are present, but the .fingerprint file is missing, so there is no version-tracking metadata for the Model Router venv, contrary to the test's Expected criteria.
Logs
Not captured.
Description
When onboarding NemoClaw with the Model Router provider, the
model-router-venvvirtual environment is created and containspython3, but the expected.fingerprintfile is not created, breaking the intended venv version tracking and rebuild detection.Environment
Steps to Reproduce
Pre-conditions:
Steps:
install.shdoes not set up Model Router:ls ~/.nemoclaw/model-router-venv/bin/python3cat ~/.nemoclaw/model-router-venv/.fingerprintExpected Result
grepin step 1 returns0matches, confirminginstall.shdoes not pre-setup Model Router or runpip3for it (Model Router venv should be created during onboard).nemoclaw onboardcompletes successfully, and selecting Model Router creates amodel-router-venvunder~/.nemoclaw.~/.nemoclaw/model-router-venv/bin/python3exists, indicating the venv is populated.~/.nemoclaw/model-router-venv/.fingerprintexists and contains a version fingerprint to track the venv's build, enabling NemoClaw to detect when the venv is stale and trigger a rebuild.Actual Result
Steps and outputs from an actual run on macOS:
Checking for
python3inside the Model Router venv:Attempting to read
.fingerprintinside the Model Router venv:The Model Router venv and
python3binary are present, but the.fingerprintfile is missing, so there is no version-tracking metadata for the Model Router venv, contrary to the test's Expected criteria.Logs
Not captured.