openclaw-sandbox

Manage Docker sandboxing configurations for tool execution in OpenClaw.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/ollieb89/openrepo --skill openclaw-sandbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-sandbox
Source: https://github.com/ollieb89/openrepo/tree/main/skills/openclaw-sandbox
Command: npx skills add https://github.com/ollieb89/openrepo --skill openclaw-sandbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides robust Docker-based sandboxing for tool execution, ensuring that potentially risky operations are isolated from the host system, enhancing security and stability.

Core Features & Use Cases

  • Configurable Isolation: Define the scope and mode of sandboxing (session, agent, shared) for different execution contexts.
  • Workspace Management: Control how agents access their workspace within the sandbox (none, read-only, read-write).
  • Customization: Mount host directories into the sandbox and configure network access and environment variables.
  • Use Case: When running untrusted code or tools that require specific dependencies, configure the sandbox to use a read-only workspace and no network access to prevent unintended side effects.

Quick Start

Configure the sandbox to use 'non-main' mode with 'session' scope and 'rw' workspace access.

Frequently Asked Questions about openclaw-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate untrusted code execution in a Docker sandbox?

To isolate untrusted code execution in a Docker sandbox, you can configure the sandbox to use a read-only workspace and disable network access, preventing unintended side effects and protecting the host system.

Can I mount host directories into a containerized sandbox environment?

Yes, you can mount host directories into a containerized sandbox environment using custom volume mounts, allowing you to manage workspace access permissions and provide specific dependencies to the isolated execution context.

What is the best way to configure workspace access for ephemeral execution environments?

The best way to configure workspace access for ephemeral execution environments is by defining granular permissions such as none, read-only, or read-write, ensuring agents only have the necessary access levels within the sandbox.

How does container isolation scope affect tool execution security?

Container isolation scope affects tool execution security by defining the sandbox boundary as session, agent, or shared, which controls how isolated the ephemeral environment is from other concurrent operations and the host system.

Do I need Docker to manage network configurations for isolated tools?

Yes, Docker is required to manage network configurations for isolated tools, as this Skill relies on Docker-based sandboxing to control network access and securely isolate potentially risky operations from the host.

When should I not use a read-write workspace in a sandbox?

You should not use a read-write workspace in a sandbox when running untrusted code, as it can lead to unintended side effects; instead, configure a read-only workspace and restrict network access to maintain strict security.