Parallel team: split one request across agents working at once
A big feature takes hours with one agent, and splitting it across several by hand leaves you merging the branches. Parallel team breaks the request into parts, gives each part to its own agent in its own worktree, merges the finished parts into an integration branch and lets you open a single pull request at the end.
This feature is in the Pro and Team plans. On the free plan it shows as locked; sign in with your AgentVera account and upgrade to unlock it. Compare plans
Plan first, you approve
When you write the request and press “Planla”, Claude Sonnet reads the repo with read-only tools (Read, Glob, Grep) and splits the work into parts. Each part has a title, the prompt its agent gets, acceptance criteria, the files it’s expected to touch and the parts that must finish first.
- The plan waits for your approval until you press “Ekibi başlat” (start the team).
- You can edit each part’s title, prompt and criteria, add or remove parts and change dependencies; up to 8 parts.
- Once the team starts, the plan is locked.
- The team works from the last commit; you get a warning if there are uncommitted changes.
Each part in its own worktree
Parts without dependencies start together, the rest follow in waves. By default 3 agents run at once, at most 6. Each part works on its own branch and worktree, cut from the tip of the integration branch, so agents never touch each other’s files.
- An agent ends with the [[TESLİM]] marker when done or [[YARDIM]] when stuck; one that stops without either is nudged twice.
- A stuck part needs attention: “Teslim al” merges what the agent did as it is, “Devam” continues the agent, “Atla” skips the part.
- The link on each part card opens that part’s agent.
- The whole team runs on Claude Code or Codex; with Automatic model on, each part’s model is picked by its difficulty.
Integration, check and one PR
Finished parts are merged one by one into an integration branch named ekip/<topic>. If a merge conflicts or the final check fails, the “Ekip · Entegrasyon” agent steps in and fixes it. The final check field comes filled with the project’s test command; leave it empty and no check runs. If the check is still red after two fix rounds, the team stops and tells you.
- When the team is done, “PR aç” pushes the integration branch and opens one pull request on GitHub.
- Removing a team deletes its worktrees; branches and the PR stay.
- Progress arrives as desktop notifications.
How to run it
- 1
Open the project’s Details → Otomasyon → Paralel ekip tab.
- 2
Write the request, choose Claude Code or Codex and press “Planla”.
- 3
Review the parts, criteria and final check, and edit them if needed.
- 4
Press “Ekibi başlat” and follow the parts on the board.
- 5
When the team is done, open the single pull request with “PR aç”.
Questions
How many agents run at once?
Three by default, at most six. Parts with dependencies start once the parts they wait for are merged.
Which agents does it use?
Parts run on Claude Code or Codex. The plan is written by Claude Sonnet, so Claude Code must be installed even when the parts run on Codex.
What if two agents touch the same file?
Each part works in its own worktree. If merging conflicts, the integration agent resolves it.
Is the pull request opened automatically?
No. When the team is done you press “PR aç”; the branch is pushed and the PR is opened on GitHub.
Which plan includes it?
Parallel team is tied to the same Pro feature as Research, plan, build, so it’s on in the Pro and Team plans.
Related features
Related terms:Multi-agent orchestration
Bring your agents to one desk.
Start on the free plan. Download it, add a project folder and open your first agent.