On this page

On this page

Get started

Crabbox plugin reference

Cloud worker provider and lease-backed sandbox backend for the Crabbox CLI.

Distribution

  • Package: @openclaw/crabbox-provider
  • Install route: included in OpenClaw

Surface

  • CLI commands: openclaw crabbox
  • Contracts: tools, workerProviders
  • Skills

Configure

See Cloud worker environments for the profile schema and lifecycle notes.

Forward Gateway environment variables to an operator-provided setup script by listing their names in the Crabbox profile settings:

json5
{  setup: 'install-worker "$OPENCLAW_WORKER_ARTIFACT_TOKEN"',  setupEnv: ["OPENCLAW_WORKER_ARTIFACT_TOKEN"],}

setupEnv explicitly forwards up to 16 unique environment variable names to the setup command only. Values are read from the Gateway process environment and are never stored in the profile configuration. Missing variables fail before a machine is allocated.

Was this useful?