Files
openclaw/docs/plugins/reference/crabbox.md
Peter Steinberger 044c0feb7c fix(crabbox): preserve Machine0 provisioning budget (#128185)
* fix(crabbox): bound Machine0 lifecycle backoff recovery

* fix(crabbox): reserve full Machine0 cleanup budget

* fix(crabbox): allow paced Machine0 inspection

* fix(crabbox): reserve Machine0 readiness retry

* fix(crabbox): pace Machine0 readiness checks

* fix(crabbox): use readiness-aware Machine0 status

* feat(crabbox): forward explicit setup environment

* fix(crabbox): preserve bounded command failure context

* fix(crabbox): enforce exact setup environment
2026-08-25 03:41:06 -07:00

39 lines
1.1 KiB
Markdown

---
summary: "Cloud worker provider backed by the Crabbox CLI."
read_when:
- You are installing, configuring, or auditing the crabbox plugin
title: "Crabbox plugin"
---
# Crabbox plugin
Cloud worker provider backed by the Crabbox CLI.
## Distribution
- Package: `@openclaw/crabbox-provider`
- Install route: included in OpenClaw
## Surface
contracts: `workerProviders`
<!-- openclaw-plugin-reference:manual-start -->
## Configure
See [Cloud worker environments](/gateway/configuration-reference#crabbox-profile) 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 validate=false
{
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.
<!-- openclaw-plugin-reference:manual-end -->