openclaw/docs/plugins/reference/crabbox.md
Peter Steinberger 4d62efeccf
feat: open Crabbox apps beside the conversation (#152094)
* feat: open Crabbox apps beside the conversation

Attach temporary cloud environments without moving the session's primary workspace. Reuse private node transports for managed app processes, CUA, desktop observation, and web portals; let screen open the exact preview in the requesting browser. Preserve conversation lifecycle authority, one-shot command approvals, manual desktop control, and cleanup across reconnects.

* feat: show Crabbox startup before provisioning

* test: type Crabbox desktop startup fixture

* refactor: isolate worker environment summaries

* refactor: make partial computer action dispatch explicit

* fix: complete Crabbox preview integration

* test: rebalance agent runtime typecheck roots

* fix: preserve desktop control when showing its source again

* fix: fence Crabbox allocation at provider commands

* test(crabbox): move allocation authority proof to plugin owner

* fix(crabbox): keep allocation authority type internal

* test: fix preview validation assertions

* test(ui): exercise inventory recovery after reopening

* build: regenerate Workboard assets after main refresh
2026-09-18 17:12:51 -07:00

1.4 KiB

summary read_when title
Cloud worker provider and lease-backed sandbox backend for the Crabbox CLI.
You are installing, configuring, or auditing the crabbox plugin
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:

{
  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.