Isolated Runtime Environment

Execution Sandbox

Every candidate patch is tested inside an isolated Docker container or constrained subprocess sandbox. The host machine is never touched — security is enforced at the kernel level.

Sandbox Engine Status

Ready

Dual-mode executor: Ephemeral Docker container with automatic subprocess fallback.

Docker Image
python:3.11-slim
Memory Cap
512 MB
Wall Timeout
60 seconds
Subprocess Fallback
Automatic
sandbox/security.py

SandboxPolicy Dataclass

Configurable policies dynamically enforce execution bounds depending on deployment mode. All fields are validated at runtime before container creation.

@dataclass
class SandboxPolicy:
    timeout_seconds:  int  = 60
    network_disabled: bool = True
    memory_limit_mb:  int  = 512
    allowed_env_vars: List[str] = field(
        default_factory=lambda: [
            "PATH", "PYTHONPATH", "HOME"
        ]
    )
    run_as_nonroot:   bool = True
    max_output_bytes: int  = 1_000_000

    # Auto-fallback to subprocess when
    # Docker daemon is unavailable
    prefer_docker:    bool = True
Kernel Containment Active

Live Security Telemetry

0-Trace
Host Isolation
Network Socket EgressOutbound TCP/UDP packets dropped via iptables
BLOCKED
Host Filesystem MountHost codebase bind-mounted strictly read-only
READ-ONLY
Memory Allocation CapHard cgroups limit enforced at 512 MB
CAPPED 512M
Execution Process TimerSIGKILL triggered if wall time exceeds 60s
60s TIMEOUT
Non-Root Execution UIDRuns as unprivileged user (UID 1000:1000)
ENFORCED
Container LifecycleEphemeral container pruned upon exit
ZERO-TRACE
Kernel cgroups v2 + IPC namespace separation enforcedOpen Debug Studio →