Crabbox features are reusable capability contracts for configuration, fleet control, runner access, synchronization, execution, and evidence. Use this page to understand what Crabbox can do after a provider has supplied the execution target.
Provider choice, direct/coordinator routing, API-key and credential expectations, sandbox/provider behavior, adapter-specific caveats, and the generated provider matrix live in the Provider Reference. Use crabbox providers and crabbox providers recommend to inspect the provider capabilities compiled into your current binary. Exact command syntax and flags live in the Command Reference.
Capability explorer
Find the contract you need.
Search by task, behavior, or system concept. Press / anywhere to focus search.
No matching capabilities. Try a broader term or another area.
Foundations
Configuration, identity, networking, and capability selection.
- 01↗Configuration
precedence, YAML schema, profiles, classes, and env vars.
Read guide - 02↗Identifiers
lease IDs, slugs, run IDs, claims, and how lookup resolves.
Read guide - 03↗Doctor checks
what
Read guidecrabbox doctorvalidates and how to extend it. - 04↗Network and reachability
Read guide--network auto|tailscale|public, port fallback, and the public/tailnet planes. - 05↗Lease capabilities
Read guide--desktop,--browser, and--codeselection rules. - 06↗Environment forwarding
name-based env allowlist for the remote command.
Read guide
Fleet control and coordination
Coordinate capacity, access, observability, cost, and lifecycle.
- 01↗Runtime adapter stack
compose
Read guideadapter serve,adapter ingress, andadapter connectbehind a fleet UI. - 02↗Coordinator
shared broker behavior across Cloudflare Durable Object and Node.js/PostgreSQL runtimes.
Read guide - 03↗Portable coordinator
deploy and operate the Node/PostgreSQL runtime on a conventional container platform.
Read guide - 04↗Bring your own infrastructure
connect a private control plane through generic providers and optional registered mode.
Read guide - 05↗Browser portal
authenticated lease/run UI, detail pages, bridge routes, and runner visibility.
Read guide - 06↗Broker auth and routing
GitHub login, shared bearer tokens, trusted proxy identity, optional Cloudflare Access, and public routes.
Read guide - 07↗Auth and admin
login/logout/whoami and trusted operator controls.
Read guide - 08↗Telemetry
lightweight Linux load, memory, disk, uptime, and per-run resource samples.
Read guide - 09↗History and logs
coordinator run records, events, and retained remote output.
Read guide - 10↗Cost and usage
guardrails, provider-backed pricing, and reporting.
Read guide - 11↗Marketplace credits gateway
one customer credit balance and smart routing across brokered capacity.
Read guide - 12↗Lifecycle cleanup
release, expiry, keep mode, and direct cleanup.
Read guide
Runners and reachability
Reach boxes securely and prepare reusable runner environments.
- 01↗Tailscale
optional tailnet reachability for managed Linux leases and static hosts.
Read guide - 02↗Pond
group related leases and discover their Tailscale, URL bridge, or SSH-mesh reachability.
Read guide - 03↗Mediated egress
browser/app egress through an operator machine using the coordinator mediator.
Read guide - 04↗Runner bootstrap
cloud-init, installed tools, SSH port, and readiness.
Read guide - 05↗Nested execution
WSL2, container engines, prepared KVM hosts, and their conditional boundaries.
Read guide - 06↗Prebaked runner images
image storage and the image/cache/state boundary.
Read guide - 07↗Image bake runbook
exact bake, candidate smoke, promotion, rollback, and cleanup flow.
Read guide - 08↗SSH keys
per-lease keys, cleanup, and local storage.
Read guide - 09↗SSH lease transport
native-or-rsync copy selection, loopback tunnels, readiness, and credential boundaries.
Read guide
Sync, execution, and evidence
Move code, execute work, collaborate, and retain review-ready proof.
- 01↗Sync
Git file-list manifests, rsync, fingerprints, excludes, guardrails, and sanity checks.
Read guide - 02↗Jobs
named repo-local warmup, hydrate, run, and cleanup workflows.
Read guide - 03↗Hermetic agent evidence
repo-local pattern for separate code/test writer contexts, QA arbitration, required artifacts, and Crabbox remote proof collection.
Read guide - 04↗Deterministic perf evidence
contract for future reproducible metric budgets and perf gate evidence.
Read guide - 05↗Actions hydration
let GitHub Actions prepare a runner, then sync local work into that workspace.
Read guide - 06↗Capsules
local-first replay manifests for GitHub Actions failures.
Read guide - 07↗Checkpoints
save, restore, and fork reusable remote workspaces.
Read guide - 08↗Editor handoff
prepare a synced lease for an external editor and keep its activity alive.
Read guide - 09↗Interactive desktop and VNC
VNC hub, support matrix, tunnel model, and QA boundaries.
Read guide - 10↗Artifacts
screenshots, video, trimmed GIFs, logs, metadata, templates, and PR publishing.
Read guide - 11↗Linux VNC
Linux desktop setup and troubleshooting.
Read guide - 12↗Windows VNC
Windows desktop setup and troubleshooting.
Read guide - 13↗macOS VNC
macOS desktop setup and troubleshooting.
Read guide - 14↗Test results
JUnit summaries attached to recorded runs.
Read guide - 15↗Cache controls
inspect, purge, and warm remote package/build caches.
Read guide - 16↗Cache volumes
provider-backed persistent cache mounts for rebuildable speed state.
Read guide
Integrations
Connect repositories, automation, and implementation surfaces.
- 01↗Integration catalog
editors, terminal UIs, coding-agent clients, and one-shot harnesses.
Read guide - 02↗Repository onboarding
Read guidecrabbox init, repo config, workflow stub, and agent skill.