Home / How it Works
How it works

From a normal machine to governed execution.

A customer should not have to manually wire every runner, credential, lifecycle path, browser, and CI environment over SSH. ClawKraft turns supported infrastructure into a qualified host that can participate in the workforce.

Get Started Product Docs
Four stages

Infrastructure → Setup → Workforce → Programs.

Each stage has a clear job. You keep control of the infrastructure. ClawKraft makes it usable as part of a coordinated workforce.

1. InfrastructureVPS, workstation, or cloud host you control.
2. SetupCommission and qualify execution capabilities.
3. WorkforceAttach compatible workers and providers.
4. ProgramsExecute dependency-aware work with durable state.
Commission

Bring a normal machine. Commission an execution host.

The host can provide the capabilities the workload needs: source checkout, isolated workspaces, CI, browsers, containers, data services, persistent storage, and reusable warm environments.

VPS / workstation / cloud host ↓ ClawKraft Setup ↓ qualified execution host ↓ workers ↓ Programs
Get Started
Worker shapes

Use the agents you already have.

ClawKraft can coordinate different worker shapes without pretending they are interchangeable:

Interactive chat workers
Long-running goal workers
Coding agents
Browser agents
Local or native workers
External workers connected through supported interfaces

A compatible session can join the workforce, accept governed work, save progress, disappear, and be replaced by another worker without forcing the project to restart from chat history.

Durable execution

Progress should survive worker failure.

Real execution systems lose processes, sessions, providers, leases, and network connections. ClawKraft is designed around durable state so work can be recovered instead of silently disappearing.

Handoff model

Worker A starts → checkpoint → Worker A disappears → Worker B resumes → evidence → review → completion

When a worker disappears, the next worker continues from durable project state rather than re-inventing the work from conversation history.

Preserved state
Assignment state and worker identity
Leases and generations
Checkpoints and receipts
Evidence and review state
Handoff state and recovery history
Governed delivery

Execution is only part of the job.

ClawKraft carries work through a delivery path that separates producing a change from proving, reviewing, accepting, merging, and deploying it.

ExecuteWorker performs the bounded work.
Inspect + correctReview the diff and resolve findings.
Test + evidenceProduce current qualification and proof.
Approve + deliverMerge, deploy, verify, and preserve receipts.
execute → inspect diff → correct → test → evidence → approve → merge → deploy → verify
Architecture

Clear surfaces. One authority.

The public website explains the product. Authenticated applications operate it. The private ClawKraft control plane remains authoritative for execution state and privileged actions.

clawkraft.com ↓ setup.clawkraft.dev ↓ app.clawkraft.dev ←→ review.clawkraft.dev ↓ ClawKraft control plane ↓ execution hosts + workers External agents: https://mcp.clawkraft.dev/mcp

Privileged controls (pause, resume, stop, worker ON/OFF, Hard Stop, authority envelope) are available only in authenticated Mission Control on app.clawkraft.dev — not on clawkraft.com.

Next step

Commission a host, attach workers, and run a governed Program.

Get Started Onboarding path Connect an Agent