Description
After running nemoclaw my-assistant shields up, openclaw tui inside the sandbox fails with "EACCES: permission denied, mkdir '/sandbox/.openclaw/agents/main/sessions'". The TUI connects to the gateway but cannot create its session directory, rendering it completely unusable. Additionally, the NemoClaw plugin reports "plugin not found" during TUI startup under shields-up lockdown, which disables the /nemoclaw shields slash command — the only in-sandbox way to check shields state.
The shields lockdown is too restrictive: it locks down config files (intended) but also prevents the TUI from creating runtime session directories (unintended).
Environment
Device: Brev GCP instance (n2d-standard-4)
OS: Ubuntu 22.04.5 LTS (Linux 6.8.0-1048-gcp x86_64)
Architecture: x86_64
Node.js: v22.22.2
npm: 10.9.7
Docker: Docker version 29.1.3
OpenShell CLI: 0.0.39
NemoClaw: v0.0.49
OpenClaw: v2026.4.24 (cbcfdf6)
Steps to Reproduce
nemoclaw onboard (fresh install v0.0.49, NVIDIA Endpoints, default sandbox my-assistant)
nemoclaw my-assistant shields up
nemoclaw my-assistant shields status — confirms "Shields: UP (lockdown active)"
nemoclaw my-assistant connect
- Inside sandbox:
openclaw tui
- Inside TUI: type
/nemoclaw shields and press Enter
Expected Result
- TUI starts normally, session created
/nemoclaw shields outputs "Shields: UP" with current lockdown state
Actual Result
-
TUI shows three issues on startup:
a. Config warnings:
plugins.entries.nemoclaw: plugin not found: nemoclaw (stale config entry ignored)
plugins.entries.openclaw-weixin: plugin not found: openclaw-weixin (stale config entry ignored)
b. Session creation fails:
run error: Error: EACCES: permission denied, mkdir '/sandbox/.openclaw/agents/main/sessions'
c. Status bar shows "connected | error"
-
/nemoclaw shields produces no output — the slash command is not registered because the nemoclaw plugin failed to load under lockdown permissions.
Note: After running nemoclaw my-assistant shields down from host, openclaw plugins inspect nemoclaw shows the plugin loads correctly and /nemoclaw slash command is registered. The plugin itself is intact; the lockdown permissions prevent it from loading during TUI startup.
Logs
Config warnings:
- plugins.entries.openclaw-weixin: plugin not found: openclaw-weixin (stale config entry ignored; remove it from plugins config)
- plugins.entries.nemoclaw: plugin not found: nemoclaw (stale config entry ignored; remove it from plugins config)
🦞 OpenClaw 2026.4.24 (cbcfdf6)
session agent:main:main
run error: Error: EACCES: permission denied, mkdir '/sandbox/.openclaw/agents/main/sessions'
connected | error
agent main | session main | inference/nvidia/nemotron-3-super-120b-a12b | tokens ?/131k
NVB#6205720
Description
After running
nemoclaw my-assistant shields up,openclaw tuiinside the sandbox fails with "EACCES: permission denied, mkdir '/sandbox/.openclaw/agents/main/sessions'". The TUI connects to the gateway but cannot create its session directory, rendering it completely unusable. Additionally, the NemoClaw plugin reports "plugin not found" during TUI startup under shields-up lockdown, which disables the/nemoclaw shieldsslash command — the only in-sandbox way to check shields state.The shields lockdown is too restrictive: it locks down config files (intended) but also prevents the TUI from creating runtime session directories (unintended).
Environment
Steps to Reproduce
nemoclaw onboard(fresh install v0.0.49, NVIDIA Endpoints, default sandbox my-assistant)nemoclaw my-assistant shields upnemoclaw my-assistant shields status— confirms "Shields: UP (lockdown active)"nemoclaw my-assistant connectopenclaw tui/nemoclaw shieldsand press EnterExpected Result
/nemoclaw shieldsoutputs "Shields: UP" with current lockdown stateActual Result
TUI shows three issues on startup:
a. Config warnings:
b. Session creation fails:
c. Status bar shows "connected | error"
/nemoclaw shieldsproduces no output — the slash command is not registered because the nemoclaw plugin failed to load under lockdown permissions.Note: After running
nemoclaw my-assistant shields downfrom host,openclaw plugins inspect nemoclawshows the plugin loads correctly and/nemoclawslash command is registered. The plugin itself is intact; the lockdown permissions prevent it from loading during TUI startup.Logs
NVB#6205720