Skip to main content

Sandboxes

Sandboxes are a Burdenoff Workspaces platform feature, not a Vibecontrols-specific concept. They provide isolated, short-lived execution environments.

How Vibecontrols uses sandboxes​

The agent's AI plugin can dispatch generated code to a sandbox for safe execution — typical use case is the AI assistant running a snippet to test a hypothesis without touching your real environment.

AiToolEvent records on the backend track sandbox interactions per agent.

Quotas + lifecycle​

Sandbox quotas, lifecycle, and isolation are platform-level. See Platform sandboxes docs for the full details.

Default per-tenant quotas:

  • Concurrent sandboxes: 20
  • Max sandbox uptime: 4h
  • Max disk per sandbox: 10 GiB
  • Max RAM per sandbox: 4 GiB

Adjust via vibecontrols config set --scope WORKSPACE --key sandbox.quota.*.

Per-vibe sandboxes​

You can enable a sandbox per-vibe (off by default):

vibecontrols config set --scope VIBE --scope-id <vibeId> \
  --key sandbox.enabled --value true

Sessions inside the vibe can then opt into running inside a sandbox via the AI plugin.

Next steps​