How It Works

From a feature request, error, or quality finding to a change you can review.

steps

Step 1: Connect your repository
Connect GitHub, GitLab.com, or Bitbucket Cloud, or start with a local project. Choose the repositories CrewWork can access. It indexes their code to give each run project context.
Step 2: Choose the work
Use Start work for a planned outcome or direct request, or begin from a grounded issue, security finding, production error, or measured coverage gap.
Step 3: Approve the plan
Review the proposed scope, assumptions, and validation targets. Approve that plan version or request a revision before execution begins.
Step 4: Follow execution and checks
CrewWork implements the change, runs required validation, and attempts repairs within your configured limits. Saved state and checkpoints support recovery after interruptions. A final review evaluates the whole program.
Step 5: Review the changes and evidence
Inspect diffs, logs, executed checks, and acceptance results. Project fixes are prepared on separate local delivery branches, with push disabled by default. Platform Self-Repair prepares draft pull requests. You decide what merges.
Step 6: Return to what needs you
Work opens on Needs attention and the Outcomes collection. Open an outcome to review its narrative, changes, logs, diagnostics, validation evidence, and the decision it needs from you.

Explore run budgets, recovery, and operational controls on Platform for more detail.

See whether CrewWork fits your work.

CrewWork is built and running, and not yet generally available.

worth discussing: The errors and backlog you would hand off; Where your source has to stay; The evidence you would need to trust a change