https://errorvault.dev/tags/environment/ Recent content in Environment on ErrorVault — Developer Error Code Dictionary Hugo en-us Tue, 19 May 2026 07:56:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-sandbox-not-found/ Tue, 19 May 2026 07:56:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-sandbox-not-found/ <h2 id="1-symptoms">1. Symptoms</h2> <p>The <code>clw-sandbox-not-found</code> error surfaces when running OpenClaw CLI commands that depend on an active sandbox session. You will typically see the error immediately after invoking any <code>clw</code> command that requires a sandbox context, such as <code>clw run</code>, <code>clw shell</code>, or <code>clw status</code>.</p> <p>Common symptoms include:</p> <ul> <li><strong>Terminal output</strong>: The error message is printed to stderr and the command exits with a non-zero status code.</li> <li><strong>Abrupt command termination</strong>: No further processing occurs after the error is thrown.</li> <li><strong>Context-dependent failures</strong>: Commands like <code>clw exec</code> or <code>clw attach</code> fail because they cannot establish a sandbox connection.</li> <li><strong>Stale shell sessions</strong>: If you previously had a sandbox open, attempting to interact with it may produce this error after the underlying sandbox was destroyed or expired.</li> <li><strong>Missing sandbox file</strong>: The OpenClaw client writes a <code>.clw-sandbox</code> metadata file in the project directory. If this file is missing, corrupted, or points to a non-existent sandbox ID, the CLI raises this error.</li> </ul> <p>Example error output:</p>