How it works
One sentence in. A proven pull request out.
AgentCrew runs a durable pipeline on your Mac and stops exactly twice: once for you to approve the plan, once for you to approve delivery. Everything between is recorded, isolated and verifiable.
- 01
Describe the outcome
One sentence is enough: "Add invite links to the team page." Paste a brief, drop in a Markdown spec, or import Linear issues. Nothing runs yet; importing work never starts execution.
agentcrew mission run "Add invite links to the team page" --project ~/code/app --wait - 02
The analyst writes a PRD
A read-only planning pass inspects the repository, separates existing behaviour from requested change, and produces requirements with stable IDs, acceptance criteria, assumptions and open questions. Inferred requirements are marked as inferred.
PRD.md · revision 1 · 7 requirements · 2 open questions - 03
You approve the plan
The lead turns the PRD into a dependency-aware task graph: each task has a role, a runtime, the requirement IDs it covers and what it depends on. The graph must cover every requirement and contain no cycles before you are asked to approve it.
Decision · Approve plan revision 1? · 5 tasks · 3 can start now - 04
Tasks run in parallel worktrees
Every task whose dependencies are done starts at once, each in its own Git worktree with its own provider session. Finished tasks are committed and merged into the run's integration branch so dependents build on real work. Conflicts block, never auto-resolve.
agentcrew/run-7f3a · invite-model ✓ · invite-api ✓ · invite-ui running - 05
The verifier proves it
A verifier role exercises the behaviour and records evidence against each requirement ID and the exact commit. Edit the PRD or push new commits and that evidence goes stale; the completion gate closes until it is fresh again.
agentcrew evidence review-package JOB_ID → 7/7 requirements fresh - 06
You approve delivery
Delivery prepares a draft pull request whose body carries a per-requirement evidence table. Merging happens in your Git host, by you. There is no auto-merge setting to accidentally enable.
Draft PR #412 · evidence table · 2 approvals recorded
Two approvals, never zero
Autonomy you set, not autonomy you hope for.
Plan approval can be skipped per mission when you trust the crew. Delivery approval cannot. Routine actions you have already authorised never interrupt you; consequential ones always do.
Decision inbox
Every question the crew has for you, with its impact on dependent work, in one place. Answer from the app or the CLI.
Steer in flight
Redirect a running task with one instruction. The provider is interrupted cleanly and continues with your note.
Take over anytime
Pause scheduling, cancel a run, reassign remaining tasks, or open the worktree and finish it yourself.
Four surfaces, one engine
Start a mission in the app. Finish it in the terminal.
Native macOS app
Projects, missions, decisions, crews, extensions, delivery and a menu-bar glance. Every screen shows real engine data.
Terminal dashboard
Run agentcrew with no arguments for an interactive dashboard that drives the same engine as the app.
Scriptable CLI
Every operation has a command with a stable JSON envelope and documented exit codes. Automate it, or wire it into your own tooling.
MCP server
Expose missions, runs and reviews to your other agents. Creating a mission over MCP never starts execution.
Waitlist open