🦀 📦 Crabbox

!Crabbox banner

crabbox run -- pnpm test

The optional coordinator is intended for a cooperative trusted team. Its authentication, ownership, and sharing controls prevent unauthorized access and accidental cross-owner operations, but do not provide isolation between mutually adversarial tenants. See the Security Policy for the supported boundary and Operational security for deployment guidance.

Within that boundary, credentialed HTTP redirects are confined to their configured origin, destructive provider recovery requires an exact local claim or stronger provider-side ownership metadata, and artifact publication accepts only regular files from the selected bundle. Provider diagnostics redact configured credentials on the documented clients, but captured output and failure bundles are not automatically scrubbed; review them before sharing. See Operational security and Artifacts.

How it works

your laptop                 coordinator runtime              cloud provider
-------------               -------------------              --------------
crabbox CLI    -- HTTPS --> Cloudflare + Durable Object  --> Hetzner / AWS / Azure / GCP / Daytona
   |                      or Node.js + PostgreSQL              |
   |                                                           |
   +------------- SSH + rsync to leased runner <---------------+

• CLI — Go binary. Loads config, mints a per-lease SSH key, asks the broker

• Coordinator — the same fleet control plane on either Cloudflare Workers

• Runner — a throwaway machine reachable over SSH on the primary port

The normal CLI data plane — SSH, rsync, command execution — runs directly from the CLI to the runner. A dedicated private AWS workspace service is a separate SSM-only controller path for API-managed workspaces; it has no public instance address or SSH access.

Only aws, azure, daytona, gcp, and hetzner can transfer provider lifecycle to the coordinator, and even those run direct from the CLI when no coordinator URL is configured. Every other provider runs direct or delegated. A direct-provider mode (--provider hetzner|aws|azure|daytona|gcp|digitalocean|linode|proxmox with local credentials) exists for debugging the coordinator itself or using private infrastructure.

Coordinator deployment choices

| Path | State and scheduling | Best fit | | ------------------------ | ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | Cloudflare Workers | Fleet Durable Object, alarms, scheduled Worker trigger | Managed edge deployment with minimal server operations and optional Cloudflare Access. | | Node.js + PostgreSQL | PostgreSQL key/value state, pg-boss alarms and reconciliation | Initial runtime for containers, a VM, or Kubernetes with one replica; requires Node.js, PostgreSQL 13+, TLS, and WebSockets. | | No coordinator | Local claims and provider-owned state | Personal/direct providers where shared credentials, history, budgets, and central cleanup are unnecessary. |

Both coordinator runtimes expose the same API, GitHub login, portal, provider adapters, cost controls, cleanup behavior, and live bridges. State is not automatically migrated between Durable Object storage and PostgreSQL. Cloudflare is the established deployment; validate the newly shipped Node runtime against the production proof checklist before cutover. See Infrastructure for deployment and ingress details. For a dedicated Node/PostgreSQL service that owns small private AWS workspaces, use the fail-closed ECS Fargate deployment and canary in Private AWS Workspaces. Client-side labels do not select that service's AWS placement; its URL and server policy do.

For the full mental model, see How Crabbox Works. For product scope and non-goals, see the Crabbox Vision. For the doc-to-code map, see Source Map.

Install

Homebrew installs the complete release distribution:

brew install openclaw/tap/crabbox
crabbox --version

The release archives are the other complete distribution for macOS, Linux, and Windows. Go users can instead compile and install only the CLI from an explicit release version (supported starting with v0.44.0; do not use @latest while older releases remain visible):

go install github.com/openclaw/crabbox/cmd/[email protected]

The module requires Go 1.26 and declares go1.26.5 as its preferred toolchain; use Go 1.26.5 or newer, or leave Go's automatic toolchain selection enabled. go install builds the Go CLI locally. It does not install release companion executables or assets, especially crabbox-apple-vm-helper, and it is not the signed/notarized prebuilt distribution. Use Homebrew or a release archive for complete platform capabilities, notably the Apple VM provider on Apple Silicon.

The native Windows CLI requires Windows 10 version 1709+ or Windows Server 2019+ for snapshot-preserving state replacement and cleanup. Supported WSL2 and x64 no-WSL Windows transfer selection requires a build from current main or Crabbox v0.42.1 and newer. Follow the Windows installation guide for the supported setup.

The Apple Silicon Homebrew install uses the release archive that also contains the native crabbox-apple-vm-helper for the local Apple VM provider.

Laptop prerequisites: git, ssh, ssh-keygen, rsync, curl.

Integrations

crabbox init --detect generates a repo-local Agent Skill for compatible coding agents. The Zed package adds checked tasks and YAML support; a separate core command, crabbox open --editor=zed, provides the Zed Remote Projects handoff. No Zed registry submission exists yet; it is tracked in https://github.com/openclaw/crabbox/issues/1157. See the integration catalog for current support and lifecycle boundaries.

Existing repositories that only need agent discovery can install the generic Skill with GitHub CLI:

gh skill install openclaw/crabbox skills/crabbox \
  --pin refs/heads/main --agent codex --scope project

Or use the cross-client Skills CLI:

npx skills add https://github.com/openclaw/crabbox --skill crabbox

Crabbox also publishes a digest-verified discovery index from its own domain:

npx skills add https://crabbox.sh --skill crabbox

Cross-vendor discovery services can index the same Skill through Crabbox's draft-compatible AI Catalog.

Herdr users can add Crabbox lease controls and repository workflows to the Herdr action palette. Use a Crabbox build that already contains this integration; the plugin installation rejects older binaries:

herdr plugin install openclaw/crabbox/plugins/herdr

Direct installation is available now; Herdr marketplace indexing is tracked in https://github.com/openclaw/crabbox/issues/1156.

The plugin provides a live boxes overlay plus actions for warmup, prewarm, connect, repository jobs, and doctor. It does not add lifecycle hooks or keybindings; normal Crabbox job stop policies still apply. See Crabbox for Herdr for action details and optional keybindings.

Quick start

Broker access is deployment-specific. Use a coordinator URL from your team, use direct-provider mode for a personal cloud account, or self-host the broker on Cloudflare or Node.js/PostgreSQL with your own provider credentials and spend caps. See Getting started and Infrastructure for the setup paths.

# log in once per machine (stores a broker token in user config)
crabbox login --url https://broker.example.com
verify local prerequisites and broker reachability
crabbox doctor
one-shot: lease, sync, run, release
crabbox run -- pnpm test
named repo workflow from .crabbox.yaml
crabbox job run full-ci
or warm a box once, then reuse it
crabbox warmup                                       # prints cbx_... + a slug
crabbox prewarm                                      # lease + Actions hydration
crabbox run --id blue-lobster -- pnpm test:changed
crabbox connect blue-lobster                         # open an interactive SSH session
crabbox ssh --id blue-lobster
crabbox open --editor=zed --id blue-lobster          # prepare a Zed Remote Projects session
crabbox stop blue-lobster

Every lease has a stable cbx_... ID and a friendly crustacean slug (blue-lobster, swift-hermit, …). Either works wherever an --id is accepted. Use --slug on fresh leases when a specific reusable slug helps, and --label on run when the history entry needs a human-readable name.

Providers

Brokered providers can run through either coordinator runtime (or direct when no coordinator is configured); every other provider runs direct or delegated from the CLI.

SSH-lease providers (provision or connect a box, full lifecycle)

| Provider and aliases | Runs on / mode | Notes | | --- | --- | --- | | AWS EC2 — aws | Linux, macOS, Windows · brokered | EC2 instances and EC2 Mac; native AMI/EBS checkpoints; optional dedicated SSM-only private workspace service. | | Azure — azure | Linux, Windows · brokered | VMs with Tailscale support; native Windows and WSL2. | | Google Cloud — gcp (google, google-cloud) | Linux · brokered | Compute Engine VMs with Tailscale support. | | Hetzner Cloud — hetzner | Linux · brokered | VMs with desktop/browser/code and Tailscale. | | DigitalOcean — digitalocean | Linux · direct | Droplets with per-lease SSH keys and Crabbox tags. | | Linode — linode | Linux · direct | Linode instances with metadata user-data, optional existing firewall attachment, and Crabbox tags. | | Hostinger — hostinger | Linux · direct | VPS leases over public SSH; explicit purchase opt-in, stop-only release. | | Parallels — parallels | Linux, macOS, Windows · direct | Local or remote macOS host; checkpoint/fork/restore/snapshot. | | Proxmox — proxmox | Linux · direct | Clone QEMU templates on a private Proxmox VE cluster. | | XCP-ng — xcp-ng | Linux · direct | Self-hosted XCP-ng pool on dedicated x86_64 server hardware. | | Incus — incus | Linux · direct | Idempotent SSH leases and private container disk checkpoints through the official Incus Go client. | | Firecracker — firecracker | Linux · direct | Self-hosted Firecracker microVM leases on a Linux KVM host with prepared kernel, rootfs, and CNI. | | Static SSH — ssh (static, static-ssh) | Linux, macOS, Windows · direct | Existing machines; no provisioning. | | Local Container — local-container (docker, container, local-docker) | Linux · direct | Local Docker-compatible runtime (Docker Desktop, OrbStack, Colima, Podman). | | Apple Container — apple-container (apple, applecontainer) | Linux · direct | Apple's native container runtime on Apple silicon macOS. | | Apple Container Machine — apple-machine (applemachine) | Linux · direct | Persistent Linux development machines from Apple Container 1.0, defaulting to Alpine. | | Apple VZ — apple-vm (applevm) | Linux ARM64 · direct | Full Ubuntu VMs through Apple Virtualization.framework; no cloud account or VM daemon. | | exe.dev — exe-dev (exe, exedev) | Linux · direct | exe.dev VMs exposed as public SSH leases. | | KubeVirt — kubevirt (kubernetes-vm) | Linux · direct | Generic KubeVirt VMs through kubectl, virtctl, and control-plane SSH forwarding. | | External — external (exec-provider) | Linux · direct | Configured executable implementing the Crabbox provider protocol. | | Namespace Devbox — namespace-devbox (namespace, namespace-devboxes) | Linux · direct | Namespace.so Devboxes over SSH. | | Namespace Compute Instance — namespace-instance (namespace-compute) | Linux · direct | Namespace Compute instances through nsc and SSH. | | Semaphore — semaphore (sem) | Linux · direct | A Semaphore CI job leased as a testbox. | | Sprites — sprites | Linux · direct | Sprites microVMs through sprite proxy. | | Tenki — tenki | Linux · direct | Tenki sandbox VMs through tenki sandbox ssh-proxy. | | Coder — coder | Linux · direct | Coder workspaces through coder ssh --stdio; stops by default, deletes only by opt-in. | | Daytona — daytona | Linux · direct | Daytona-managed dev sandbox over SSH. | | Morph — morph | Linux · direct | Morph Cloud snapshot-backed instances over the shared SSH gateway. | | RunPod — runpod (run-pod, runpodio) | Linux · direct | RunPod GPU pods with public SSH. | | ASCII Box — ascii-box (ascii, asciibox) | Linux · direct | ASCII Box Ubuntu sandboxes exposed as SSH leases. |

XCP-ng itself can host Linux, Windows, and BSD guests, but Crabbox's current xcp-ng adapter provisions normal leases from Linux templates only. The separate XCP-ng ISO E2E harness also covers Windows x86_64/x64 installers. macOS guests are out of scope on this path; use the Tart provider on Apple hardware for macOS VM workflows.

Delegated-run providers (sandbox/proof runners, no SSH lease)

| Provider and aliases | Runs on | Notes | | -------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------- | | AWS Lambda MicroVM — aws-lambda-microvm | Linux ARM64 | Lambda Firecracker MicroVM with archive sync, retained reuse, and pause/resume. | | Cloudflare — cloudflare (cf) | Linux | Cloudflare Containers via the Worker runtime. | | Cloud Run Sandbox — cloud-run-sandbox (gcrun-sandbox, cloudrun-sandbox) | Linux | Google Cloud Run sandboxes via gateway or in-container sandbox CLI. | | Docker Sandbox — docker-sandbox | Linux | Docker Sandboxes through the standalone sbx CLI. | | E2B — e2b | Linux | E2B Firecracker sandbox. | | Freestyle — freestyle | Linux | Freestyle VMs through the Freestyle REST API. | | Islo — islo | Linux | Islo sandbox. | | Modal — modal | Linux | Modal Sandbox through the local Python client. | | Microsoft Execution Containers — mxc (execution-container) | Windows | Policy-driven local Windows process containment. | | OpenComputer — opencomputer (oc, open-computer) | Linux | OpenComputer Linux VMs through the OpenComputer REST API. | | OpenSandbox — opensandbox | Linux | OpenSandbox delegated containers through the OpenSandbox Go SDK. | | Railway — railway (rail, railwayapp) | Linux | Inspect and stop an existing Railway service. | | Anthropic Sandbox Runtime — anthropic-sandbox-runtime (srt) | macOS, Linux | Local one-shot sandboxing through Anthropic's srt CLI. | | SmolVM — smolvm (smol, smolmachines, smolfleet) | Linux | Smol Machines microVM sandboxes via the smolfleet API. | | Tensorlake — tensorlake (tl, tensorlake-sbx) | Linux | Tensorlake Firecracker sandbox via the Tensorlake CLI. | | Upstash Box — upstash-box (upstash, box, upstashbox) | Linux | Upstash Box through the Box REST API. | | Azure Dynamic Sessions — azure-dynamic-sessions | Linux | Azure Container Apps dynamic sessions. | | Blacksmith Testbox — blacksmith-testbox (blacksmith) | Linux | Delegated Blacksmith CI Testbox lifecycle and execution. | | W&B Sandboxes — wandb (weights-and-biases) | Linux | Weights & Biases Sandboxes; reuses wandb login credentials. | | Windows Sandbox — windows-sandbox (wsb, windows-sandbox-provider) | Windows | Disposable Microsoft Windows Sandbox sessions through generated .wsb configs. |

See Providers for the full reference, capabilities, and authoring guide.

Highlights

• One-shot or warm workspaces. crabbox run for fire-and-forget;

• Named repo jobs. crabbox job run lets repos define warmup,

• Local-first workspace sync. No clean-checkout requirement. Tracked and

• Run observability. Every coordinator-backed run gets an early run_...

• GitHub Actions hydration. crabbox actions hydrate runs supported setup

• Failure capsules. crabbox capsule from-actions captures a

• Checkpoints. Save VM-or-workspace state and restore/fork from it, via

• Pond peer groups. Leases that share a --pond label form an

• Brokered cloud with cost guardrails. Maintainers and agents share infra

• Interactive desktop, browser, and code leases. --browser provisions

• Authenticated web portal. Browser login opens owner-scoped and shared

• Agent workspace evidence. History, logs, events, telemetry, JUnit

• Stable timing records. --timing-json on run, warmup, prewarm, and

• Coordinator access controls. GitHub browser login, owner-scoped leases,

Machine classes

beast is the default for providers that expose class-based managed capacity. The providers below fall back across ordered instance-type lists unless --type pins a specific provider-native size.

Hetzner    tiny      ccx13, cpx22, cx23
           small     ccx23, cpx32, cx33
           standard  ccx33, cpx62, cx53
           fast      ccx43, cpx62, cx53
           large     ccx53, ccx43, cpx62, cx53
           beast     ccx63, ccx53, ccx43, cpx62, cx53
AWS Linux  tiny      m7a.large, m7i.large, c7a.xlarge, c7i.xlarge
           small     c7a.2xlarge, c7i.2xlarge, m7a.xlarge, m7i.xlarge, c7a.xlarge
           standard  c7a/c7i/m7a/m7i.8xlarge family
           fast      …16xlarge family
           large     …24xlarge family
           beast     …48xlarge family, falling back to 32x/24x/16x
           arm64     c7g/m7g/r7g families with --arch arm64
AWS Win    tiny      m7a.large, m7i.large, t3.large
           small     c7a.2xlarge, c7i.2xlarge, m7a.xlarge, m7i.xlarge, t3.xlarge
           standard  m7i.large, m7a.large, t3.large
           fast      m7i.xlarge, m7a.xlarge, t3.xlarge
           large     m7i.2xlarge, m7a.2xlarge, t3.2xlarge
           beast     m7i.4xlarge, m7a.4xlarge, m7i.2xlarge
AWS WSL2   tiny      m8i.large, m8i-flex.large, c8i.xlarge, r8i.large
           small     c8i.2xlarge, m8i.xlarge, m8i-flex.xlarge, r8i.large, c8i.xlarge
           standard  m8i.large, m8i-flex.large, c8i.large, r8i.large
           fast      m8i.xlarge, m8i-flex.xlarge, c8i.xlarge, r8i.xlarge
           large     m8i.2xlarge, m8i-flex.2xlarge, c8i.2xlarge, r8i.2xlarge
           beast     m8i.4xlarge, m8i-flex.4xlarge, c8i.4xlarge, r8i.4xlarge, m8i.2xlarge
AWS macOS  all       mac2.metal, then mac1.metal unless --type is set
Azure      tiny      Standard_D2ads_v6, Standard_D2ds_v6, then v5/F2 fallbacks
           small     Standard_D8ads_v6, Standard_D8ds_v6, then v5/F8/4-vCPU fallbacks
           standard  Standard_D32ads_v6, Standard_D32ds_v6, Standard_F32s_v2, then 16-vCPU fallbacks
           fast      Standard_D64ads_v6, Standard_D64ds_v6, Standard_F64s_v2, then 48/32-vCPU fallbacks
           large     Standard_D96ads_v6, Standard_D96ds_v6, then 64/48-vCPU fallbacks
           beast     Standard_D192ds_v6, Standard_D128ds_v6, then 96/64-vCPU fallbacks
           arm64     Standard_Dps_v6 / Dpds_v6 Cobalt families with --arch arm64
Azure Win/
WSL2       tiny      Standard_D2ads_v6, Standard_D2ds_v6, Standard_D2ads_v5, Standard_D2ds_v5, Standard_D2as_v6
           small     Standard_D8ads_v6, Standard_D8ds_v6, Standard_D8ads_v5, Standard_D8ds_v5, Standard_D8as_v6
           standard  Standard_D2ads_v6, Standard_D2ds_v6, Standard_D2ads_v5, Standard_D2ds_v5, Standard_D2as_v6
           fast      Standard_D4ads_v6, Standard_D4ds_v6, Standard_D4ads_v5, Standard_D4ds_v5, Standard_D4as_v6
           large     Standard_D8ads_v6, Standard_D8ds_v6, Standard_D8ads_v5, Standard_D8ds_v5, Standard_D8as_v6
           beast     Standard_D16ads_v6, Standard_D16ds_v6, Standard_D16ads_v5, Standard_D16ds_v5, Standard_D8ads_v6
Namespace  tiny      S
           small     S
           standard  S
           fast      M
           large     L
           beast     XL
Namespace
Compute    tiny      1x2
           small     2x4
           standard  4x8
           fast      8x16
           large     16x32
           beast     32x64
Cloudflare tiny      standard-4
           small     standard-4
           standard  standard-4
           fast      standard-4
           large     standard-4
           beast     standard-4

Override with --type or CRABBOX_SERVER_TYPE for a specific instance. Use --arch arm64 / architecture: arm64 for Linux ARM capacity on Azure or AWS; explicit ARM provider types also select ARM images when no custom image is set. Cloudflare also accepts lite, basic, standard-1, standard-2, and standard-3 as smaller explicit --type values; standard-4 is the default. Providers without a row either use provider-native capacity settings or reject class/type selection.

The dedicated private AWS workspace API does not use these AWS class tables. It accepts only its server-configured instance allowlist; the recommended small policy starts with t3a.small,t3.small and a 20 GiB encrypted gp3 root volume.

Configuration

Config resolves in order: flags → env → repo .crabbox.yaml → user ~/.config/crabbox/config.yaml → defaults.

broker:
  url: https://broker.example.com
  provider: aws
  token: ...
class: beast
capacity:
  market: spot
  strategy: most-available
  fallback: on-demand-after-120s
  hints: true
aws:
  region: eu-west-1
  rootGB: 400
lease:
  idleTimeout: 30m
  ttl: 90m
ssh:
  key: ~/.ssh/id_ed25519
  user: crabbox
  port: "2222"
  # Ordered fallback ports tried after ssh.port; use [] to disable fallback.
  fallbackPorts:
    - "22"

Set broker.mode: registered to keep provisioning and cleanup in any direct provider while registering lease metadata with the coordinator for inventory, sharing, and portal WebVNC. Kept desktop leases start the outbound WebVNC bridge automatically by default; set broker.autoWebVNC: false to opt out. The coordinator never receives provider credentials or directly calls a registered provider. By default it removes only registration metadata; an explicitly bound outbound runtime adapter can perform a user-confirmed workspace delete. API clients request the same generation-fenced delete with POST /v1/leases/{id}/release and body {"delete":true}.

Forwarded environment is intentionally narrow: NODE_OPTIONS and CI. Do not pass secrets as command-line arguments. For live-secret smoke tests, use crabbox run --env-from-profile --allow-env NAME so Crabbox forwards only selected names and prints redacted presence/length metadata. For stale warm boxes, --full-resync (alias --fresh-sync) resets the remote workdir before syncing. For larger commands, use --script or --script-stdin so the remote runner executes an uploaded file instead of a giant quoted shell string.

For binary or terminal-hostile output, use crabbox run --capture-stdout or --capture-stderr . Add --preflight for a remote capability snapshot, --keep-on-failure to SSH into the exact failed one-shot lease, or --download remote=local to copy a successful-run artifact back. Failed SSH-backed and Blacksmith delegated runs save local .crabbox/captures/*.tar.gz bundles by default, falling back to the Crabbox user state directory when the project destination is unwritable. The reported failure-bundle local=... path identifies the saved bundle; see local capture storage. Captured files are not redacted by Crabbox.

Optional Tailscale reachability for managed Linux leases:

tailscale:
  enabled: true
  network: auto
  tags:
    - tag:crabbox
  hostnameTemplate: crabbox-{slug}
  authKeyEnv: CRABBOX_TAILSCALE_AUTH_KEY
  exitNode: mac-studio.example.ts.net
  exitNodeAllowLanAccess: true

Tailscale is a network plane, not a provider. --tailscale joins new managed Linux leases to the tailnet; --network auto|tailscale|public chooses how SSH and VNC tunnel commands resolve the host. Brokered mode uses Worker OAuth secrets to mint one-off keys; direct-provider mode reads the auth key from the configured env var. See Tailscale.

A few provider-specific config snippets:

# Static macOS or Windows target (existing machine, no provisioning)
provider: ssh
target: windows
windows:
  mode: normal # or wsl2
static:
  host: win-dev.local
  user: alice
  port: "22"
  workRoot: C:\crabbox

# Local container (alias: docker; detects docker or podman)
provider: local-container
localContainer:
  runtime: docker
  image: debian:bookworm
  workRoot: /work/crabbox

# Delegated Blacksmith CI Testbox
provider: blacksmith-testbox
blacksmith:
  org: example-org
  workflow: .github/workflows/ci-check-testbox.yml
  job: test
  ref: main
  idleTimeout: 90m

Keep provider tokens in environment variables, not repo config (for example CRABBOX_SEMAPHORE_TOKEN, CRABBOX_SPRITES_TOKEN, RUNPOD_API_KEY, MORPH_API_KEY, ASCII_BOX_API_KEY, E2B_API_KEY, DAYTONA_API_KEY, CLOUD_RUN_SANDBOX_URL/CLOUD_RUN_SANDBOX_SECRET). The full env-var reference, per-provider sections, and per-command flags are in docs/cli.md, Configuration, and the provider docs.

Development

# Go CLI
go build -trimpath -o bin/crabbox ./cmd/crabbox
go vet ./...
go test -race -timeout=20m ./...
Coordinator runtimes (Node 22+ locally; CI runs Node 24)
npm ci --prefix worker
npm test --prefix worker
npm run build --prefix worker
npm run check:node --prefix worker
npm run build:node --prefix worker
Repository scripts
node scripts/generate-linux-readiness.mjs --check
node scripts/generate-bootstrap.mjs --check
node --test scripts/.test.js scripts/.test.mjs
Docs
scripts/check-docs.sh
Optional live smoke, when broker/provider credentials are available
CRABBOX_LIVE=1 CRABBOX_LIVE_REPO=/path/to/my-app scripts/live-smoke.sh
Firecracker host readiness smoke (read-only; reports environment_blocked when Linux/KVM assets are missing)
CRABBOX_BIN=./bin/crabbox scripts/live-firecracker-smoke.sh

CI runs the full gate (gofmt, vet, race tests, all Go modules, coverage threshold, repository script tests, docs link/build check, GoReleaser snapshot, and Worker lint/typecheck/tests/build) on every push and PR. The required Go check aggregates three independent 30-minute jobs: Go test (formatting, vet, deadcode, full race suite, Linux supervision proof, and build), Go modules (normal tests in every module, including the root), and Go coverage (90% core coverage threshold). The race suite, all-module normal tests, and coverage collection use a 15-minute package timeout. Use the explicit timeout locally too: the CLI race suite can exceed Go's default 10-minute package deadline even when its individual tests pass. Production releases use a serialized, draft-first process: preserve and verify the signed tag, build and Developer ID sign/notarize the macOS candidates locally, verify the exact draft on native Apple Silicon and Intel runners from protected-default code, then publish those exact artifacts, dispatch the ordinary Homebrew tap update, and run independent public-download, public Go installation, and native Homebrew smokes. Publication establishes eligibility; retry a failed Homebrew update without rebuilding or republishing. The tap handoff is an explicit operator step, with generic tap reconciliation as an independent fallback. One explicit full release/publish request authorizes this complete normal sequence without renewed chat approval at each stage. Narrow requests stay narrow. The original request supplies authorization; GitHub events alone do not. Sequential technical gates, separate trust domains, and cancellation boundaries remain mandatory. See Release engineering.

Git-overlay integration tests use real Git with task-owned local and loopback origins. Their local SSH stand-ins isolate Git authentication settings and disable interactive credential requests, including during ordinary seed fallback. A credential-helper/askpass canary guards this test-only boundary; the separate production overlay security tests still inject hostile Git config.

CLI runtime optimizations retain the full normal, race, and coverage modes and their existing deadlines and observation windows. Synchronous POSIX test-executable helpers suppress only the race runtime's exit delay in their child environment, preserving inherited detection and reporting options; Windows keeps its existing execution path. HTTP deadline cases with explicit configuration and private servers overlap their real waits without changing timeout contracts. The shared immutable CLI and provider builds stay inside M.Run, with their existing fixture cleanup and rebuild ownership.

Cloudflare, Node/PostgreSQL, container, ingress, secrets, and DNS deployment live in docs/infrastructure.md. The dedicated ECS Fargate path is documented in Private AWS Workspaces.

Docs

• Get the model: How Crabbox Works, Architecture, Concepts, Orchestrator
• Use the CLI: CLI, Commands, Features, Configuration
• Integrate editors and agents: Integrations, Editors, AI agents and harnesses
• Choose a provider: Providers, AWS, Azure, GCP, Hetzner, DigitalOcean, Linode, Hostinger
• Advanced features: Actions hydration, Capsules, Checkpoints, Jobs, Pond
• Interactive QA: Interactive Desktop and VNC, Artifacts, Portal
• Integrate infrastructure: Bring Your Own Infrastructure, Portable Coordinator, Private AWS Workspaces, External Provider
• Operate it: Operations, Release engineering, Observability, Troubleshooting, Performance
• Set it up or audit it: Infrastructure, Security Policy, Operational Security, Getting Started, Source Map
• Changes: CHANGELOG.md

scripts/check-docs.sh
open dist/docs-site/index.html