crabbox/docs/features

Features

Feature docs explain what Crabbox can do and how the pieces fit together. Command syntax lives in ../commands/README.md.

Read when:

• you want a capability overview;
• you are deciding where a behavior belongs;
• you need the feature-level contract before changing code.

Core features:

• Coordinator: brokered leases through Cloudflare Workers and Durable Objects.
• Broker auth and routing: bearer tokens, Cloudflare Access identity, and Worker routes.
• Providers: Hetzner and AWS EC2 Spot provisioning, classes, and fallback.
• Runner bootstrap: cloud-init, installed tools, SSH port, and readiness.
• Sync: Git file-list manifests, rsync, fingerprints, excludes, guardrails, and sanity checks.
• Actions hydration: let GitHub Actions prepare a runner, then sync local work into that workspace.
• SSH keys: per-lease keys, provider key cleanup, and local storage.
• Cost and usage: guardrails, provider-backed pricing, and reporting.
• History and logs: coordinator run records and retained remote output tails.
• Test results: JUnit summaries attached to recorded runs.
• Cache controls: inspect, purge, and warm remote package/build caches.
• Auth and admin: login/logout/whoami and trusted operator controls.
• Lifecycle cleanup: release, expiry, keep mode, and direct cleanup.
• Repository onboarding: crabbox init, repo config, workflow stub, and agent skill.
• Source map: implementation files behind documented behavior.

Command docs:

• doctor
• init
• warmup
• run
• history
• logs
• results
• cache
• status
• list
• usage
• ssh
• inspect
• stop
• actions
• cleanup
• config
• login
• logout
• whoami
• admin