Description
nemoclaw onboard automatically sends a "ping" message to the agent to verify the inference endpoint. This creates a session file (nemoclaw-onboard-warmup-<id>) inside the sandbox. When the user runs nemoclaw <name> sessions export on a freshly onboarded sandbox before having any real conversations, the export includes this warmup session and reports "1 session(s) exported". The user sees a conversation file they never created. A freshly onboarded sandbox should report 0 exportable sessions.
Environment
Device: NVIDIA 2u2g-gen-0642 (RTX PRO 6000 Blackwell Server Edition)
OS: Ubuntu 24.04.4 LTS
Architecture: x86_64
Node.js: v22.22.3
npm: 10.9.8
Docker: 29.4.3, build 055a478
OpenShell CLI: 0.0.44
NemoClaw: v0.0.65
OpenClaw: v2026.5.27
Steps to Reproduce
-
Install NemoClaw v0.0.65 and onboard a brand new sandbox without running any agent prompts:
curl -fsSL https://www.nvidia.com/nemoclaw.sh | NEMOCLAW_INSTALL_TAG=v0.0.65 bash
(sandbox name: empty-test)
-
Confirm no user sessions exist:
nemoclaw empty-test sessions list
-
Run sessions export from a clean working directory:
mkdir -p /tmp/empty-export && cd /tmp/empty-export
nemoclaw empty-test sessions export
-
Observe the export message and the exported file.
-
Inspect the exported session file content.
Expected Result
Step 2: Sessions listed: 0 (no user conversations yet).
Step 3: Command exits with a friendly "nothing to export" message. No export folder is created.
Steps 4–5: The onboard warmup session (nemoclaw-onboard-warmup-*) is not visible to the user — it is an internal system session, not a user conversation.
Actual Result
Step 2: Sessions listed: 1 — the warmup session appears as a regular session:
direct agent:main:expli...598124 1m ago nemotron-3-super-120b-a12b id:nemoclaw-onboard-warmup-969-1781598124
Steps 3–4: Export succeeds, reports Exported all sessions for agent 'main' (1 session(s)) and downloads the warmup session file.
Step 5: The exported file contains a single user message with content "ping" — sent automatically by the installer to verify the inference endpoint, not by the user:
{"type":"message","role":"user","content":[{"type":"text","text":"ping"}],...}
The warmup session is indistinguishable from a real user session in both the sessions list and the export output. A user who runs sessions export before their first real conversation will receive a confusing file they did not create.
Logs
$ nemoclaw empty-test sessions list 2>/dev/null | tail -4
Sessions listed: 1
direct agent:main:expli...598124 1m ago nemotron-3-super-120b-a12b id:nemoclaw-onboard-warmup-969-1781598124
$ nemoclaw empty-test sessions export; echo "exit: $?"
Downloading sandbox:/sandbox/.openclaw/agents/main/sessions/nemoclaw-onboard-warmup-969-1781598124.jsonl -> sessions-empty-test/nemoclaw-onboard-warmup-969-1781598124.jsonl
✓ Download complete
Exported all sessions for agent 'main' (1 session(s)) to ./sessions-empty-test/
exit: 0
NVB#6331149
Description
nemoclaw onboardautomatically sends a"ping"message to the agent to verify the inference endpoint. This creates a session file (nemoclaw-onboard-warmup-<id>) inside the sandbox. When the user runsnemoclaw <name> sessions exporton a freshly onboarded sandbox before having any real conversations, the export includes this warmup session and reports "1 session(s) exported". The user sees a conversation file they never created. A freshly onboarded sandbox should report 0 exportable sessions.Environment
Steps to Reproduce
Install NemoClaw v0.0.65 and onboard a brand new sandbox without running any agent prompts:
curl -fsSL https://www.nvidia.com/nemoclaw.sh | NEMOCLAW_INSTALL_TAG=v0.0.65 bash(sandbox name: empty-test)
Confirm no user sessions exist:
Run sessions export from a clean working directory:
Observe the export message and the exported file.
Inspect the exported session file content.
Expected Result
Step 2: Sessions listed: 0 (no user conversations yet).
Step 3: Command exits with a friendly "nothing to export" message. No export folder is created.
Steps 4–5: The onboard warmup session (
nemoclaw-onboard-warmup-*) is not visible to the user — it is an internal system session, not a user conversation.Actual Result
Step 2: Sessions listed: 1 — the warmup session appears as a regular session:
Steps 3–4: Export succeeds, reports
Exported all sessions for agent 'main' (1 session(s))and downloads the warmup session file.Step 5: The exported file contains a single user message with content
"ping"— sent automatically by the installer to verify the inference endpoint, not by the user:The warmup session is indistinguishable from a real user session in both the sessions list and the export output. A user who runs sessions export before their first real conversation will receive a confusing file they did not create.
Logs
NVB#6331149