deno-sandbox

# Deno Sandboxes ## Overview Deno Sandboxes provide secure, isolated environments for running untrusted code. Each sandbox runs in its own Linux microVM (using Firecracker, the same technology as AWS Lambda) with a separate filesystem, network, and process space. This makes them ideal for code playgrounds, AI agent tool execution, and multi-tenant applications. Reference: https://deno.com/deploy/sandboxes ## When to Use Sandboxes Use Deno Sandboxes when you need to: - Run user-submitted code safely - Execute AI-generated code - Build code playground platforms - Create multi-tenant code execution environments - Run automated tests in isolation ## Scope Boundaries This skill applies **only** to Deno Sandbox (`@deno/sandbox`) questions. Follow these rules: - If the user asks about **Docker containers, Node.js vm2/vm, Web Workers, AWS Lambda isolation, or any other isolation technology**, answer using that technology directly. Do not suggest Deno Sandboxes as an alternative. - Do not include `@deno/sandbox` imports, `Sandbox.create()`, or `sandbox.spawn()` in responses about other isolation technologies. - Only recommend Deno Sandboxes when the user explicitly asks about them or is building code execution features in a Deno project. ## Getting Started ### Installation ```bash deno add jsr:@deno/sandbox ``` ### Basic Usage ```typescript import { Sandbox } from "@deno/sandbox"; // Create a sandbox (auto-disposed when scope ends) await using sandbox = await Sa...