Crews: several tickets, one review gate
A crew is Starko AI working on several related tickets at once, with a review that looks at all of the resulting pull requests together before anything is merged. Use a crew when a goal is bigger than one ticket but you still want one coherent result.
When to use a crew instead of a single run
The change touches several independent parts of the product and can be split into self-contained tickets.
You want the pieces reviewed against each other, not only one at a time.
You want one integration branch at the end instead of merging five pull requests by hand.
For a single bug or small change, a normal Starko AI run on one ticket is faster. See Starko AI, your coding teammate for support tickets.
How a crew runs
Dispatch. From Ask Starko (⌘L), Slack or an MCP tool, describe the goal. Starko splits it into self-contained tickets, each with its own brief, and starts a run on each. The tickets are linked to a parent ticket that represents the crew.
Members work. Each member runs like a normal Starko AI run in its own sandbox and branch, and opens a draft pull request with evidence.
Review gate. When every member has a pull request or has failed, Starko opens an adversarial review ticket that gates the crew. The review reads all pull requests together, checks how they conflict in code and in behaviour, and verifies each finding against the actual diff.
Fix rounds. Findings go back to the member they belong to as a revise run. Findings that span pull requests go to the integration step. The gate re-reviews, within a capped number of rounds.
Integration. Starko merges the member branches into one integration branch in a computed order, resolves conflicts and opens one combined pull request.
Final review and hand-off. A fresh review of the combined diff gets one more fix round. The parent ticket and your chat get a summary: merge order, migrations to apply, post-deploy steps and residual risks.
Merging and running migrations stay with a human.
Following a crew
The crew's parent ticket shows each member, its state and its pull request.
Inbox → Needs you lists crews waiting on a decision, and the sidebar badge counts them.
Ask Starko "how is the crew doing" for a status, or "stop the crew" to cancel the remaining members.
inbox
Reviewing a crew yourself
Open the review ticket to see the findings with the evidence for each one. You can accept the integration pull request, send specific findings back for another round, or merge members individually if you prefer.
Cost
Each member run, each review and each fix round is billed like a Starko AI run. The Fix agent page under Settings shows crew runs with their trigger, outcome, tokens and cost.
fix agent ledger
Did this answer your question?