How It Works
From a feature request, error, or quality finding to a change you can review.
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.
Choose the work
Describe a feature, ask for a fix, or start from an issue, security finding, or measured coverage gap. The Run Composer lets you define the objective and attach the context already available in your project.
Approve the plan
Review the proposed scope, assumptions, and validation targets. Approve that plan version or request a revision before execution begins.
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.
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.
Return to what needs you
The Inbox separates Needs you, Active, and Done so you can find decisions and follow work in progress. Quality findings and code improvement suggestions provide starting points for the next run.
Explore run budgets, recovery, and operational controls on Platform for more detail.
Bring a project to the conversation
Discuss the work you want to delegate and what it would take to run CrewWork in your environment.