openclaw/crabbox

What it solves

Crabbox provides a way to run software tests and execution commands on remote infrastructure instead of a local laptop. It solves the problem of needing more powerful hardware, specific operating systems, or clean, disposable environments for every test run without having to configure a full CI/CD pipeline for every small change.

How it works

Crabbox uses a Go-based CLI that interacts with an optional coordinator (deployed via Cloudflare Workers or Node.js) to lease a remote runner from various cloud providers (such as AWS, GCP, Azure, or Hetzner). Once a runner is leased, the CLI syncs the local working directory to the remote machine via SSH and rsync, executes the specified command, streams the output back to the user, and then releases the runner.

Who it’s for

• Maintainers who need larger machines or platform-specific validation for test suites and builds.
• Contributors who want disposable environments that match a repository's setup scripts.
• AI agents and automation tools that require auditable remote boxes for command execution and log collection.
• Teams that want centralized control over cloud credentials, spending caps, and shared usage history.

Highlights

• Extensive Provider Support: Integrates with a wide array of cloud providers (AWS, Azure, GCP, Hetzner, DigitalOcean) and local virtualization tools (Docker, Apple VM, Proxmox).
• Flexible Coordination: Can be run in a decentralized "direct-provider" mode or via a centralized coordinator for team management.
• Agent-Ready: Includes an "Agent Skill" for compatible coding agents to discover and use remote execution capabilities.
• Workflow Integration: Supports named repository workflows via .crabbox.yaml and integrates with editors like Zed for remote project handoffs.