openclaw-workspace/memory/2026-03-04-sandbox-fix.md

Session: 2026-03-04 03:41:08 UTC

• Session Key: agent:main:main
• Session ID: 80044670-adcd-40ee-aeb7-2b32545d7a1a
• Source: webchat

Conversation Summary

assistant: Still broken — Tool not found

No dice. Same error persists.

Since the full gateway restart with config edits didn't fix it, this might be:

• A bug/regression in the new version
• Session-level issue requiring session kill/restart
• Tool registration failure at startup

When you get back from the interwebs, we can try:

1. Kill my session entirely and let it respawn fresh
2. Check openclaw doctor output
3. Look at startup logs for tool registration errors

Good luck out there 🤙 assistant: Still broken — Tool not found

No dice. Same error persists.

Since the full gateway restart with config edits didn't fix it, this might be:

• A bug/regression in the new version
• Session-level issue requiring session kill/restart
• Tool registration failure at startup

When you get back from the interwebs, we can try:

1. Kill my session entirely and let it respawn fresh
2. Check openclaw doctor output
3. Look at startup logs for tool registration errors

Good luck out there 🤙 user: Conversation info (untrusted metadata):

{
  "message_id": "1478580603933818911",
  "sender_id": "458667380332036117",
  "sender": "Rucus",
  "timestamp": "Tue 2026-03-03 20:31 CST"
}

Sender (untrusted metadata):

{
  "label": "Rucus (458667380332036117)",
  "id": "458667380332036117",
  "name": "Rucus",
  "username": "unclerucus",
  "tag": "unclerucus"
}

requested gateway; configure tools.exec.host=sandbox to allow assistant: That's the smoking gun!

The error literally tells you what to do. Here's the fix:

Set the exec host to sandbox:

openclaw config set tools.exec.host sandbox
openclaw gateway restart

Then tools should work.

Full config should look like:

openclaw config set tools.exec.host sandbox
openclaw config set tools.exec.security allowlist
# or full if you want no restrictions:
# openclaw config set tools.exec.security full

Then restart the gateway so it picks up the changes.

Want me to try a tool once you've done that? user: Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK. Current time: Tuesday, March 3rd, 2026 — 8:43 PM (America/Chicago) assistant: Running heartbeat check — 8:43 PM

Let me try a tool to see if the issue is fixed: user: Conversation info (untrusted metadata):

{
  "message_id": "16865a8a-ffbb-4dce-9e6e-217ffc096d69",
  "sender_id": "openclaw-control-ui",
  "sender": "openclaw-control-ui"
}

Sender (untrusted metadata):

{
  "label": "openclaw-control-ui",
  "id": "openclaw-control-ui"
}

[Tue 2026-03-03 20:58 CST] ok try the tools assistant: Great! Let me test the tools: assistant: Great! Let me test the tools: user: Conversation info (untrusted metadata):

{
  "message_id": "1478592458337157283",
  "sender_id": "458667380332036117",
  "sender": "Rucus",
  "timestamp": "Tue 2026-03-03 21:18 CST"
}

Sender (untrusted metadata):

{
  "label": "Rucus (458667380332036117)",
  "id": "458667380332036117",
  "name": "Rucus",
  "username": "unclerucus",
  "tag": "unclerucus"
}

Tools? assistant: ❌ Tools still broke — Tool not found

The exec host setting didn't fix it. This is deeper than just config.

Next steps:

1. Check openclaw doctor: Run diagnostics to see what's actually missing

   openclaw doctor
   

2. Kill my session and let it respawn fresh (session-level issue):

   openclaw sessions kill agent:main:main
   

3. Check if there's a tool registration error at startup:

   grep -i "tool\|register" ~/.openclaw/logs/gateway.log
   

4. Or run verbose startup:

   openclaw gateway stop
   OPENCLAW_DEBUG=1 openclaw gateway start 2>&1 | tee /tmp/gateway-debug.log
   

Want to try one of these? user: Conversation info (untrusted metadata):

{
  "message_id": "1478597847065563196",
  "sender_id": "458667380332036117",
  "sender": "Rucus",
  "timestamp": "Tue 2026-03-03 21:39 CST"
}

Sender (untrusted metadata):

{
  "label": "Rucus (458667380332036117)",
  "id": "458667380332036117",
  "name": "Rucus",
  "username": "unclerucus",
  "tag": "unclerucus"
}

Hey assistant: Hey! 🤙

Still here — but tools are still down (Tool not found).

Any luck with the openclaw doctor or checking the logs? Or want to try killing this session and letting it respawn fresh? assistant: 🦞 OpenClaw 2026.3.2 (85377a2) 🧠 Model: ollama/kimi-k2.5:cloud · 🔑 api-key o...a (models.json) 🧮 Tokens: 114k in / 79 out · 💵 Cost: $0.0000 📚 Context: 114k/256k (44%) · 🧹 Compactions: 0 🧵 Session: agent:main:main • updated just now ⚙️ Runtime: docker/all · Think: off 🪢 Queue: collect (depth 0) assistant: Usage: /kill <id|#|all>