Agents & collaboration

Teams, workers and reviews

Organize larger coding tasks with a lead, separate workers and optional quality reviews.

App version 0.7.934 · Updated

Get started

  1. Open Team in the tools sidebar and create or choose a team profile.
  2. Configure workers, review rules, integration and the real deployment process.
  3. Enable Start as team lead in a new session and choose a repository and profile.
  4. Describe the overall task and inspect the resulting worker assignments.
  5. Follow reports and Git state in the team area, review decisions and integrate completed work according to your rules.

Use the roles you need

The lead coordinates the overall task and integrates results. Workers take bounded subtasks in their own working copies and branches. An optional delegator helps turn a larger request into assignments before workers start.

Guardian
An optional review role checks results against your standards and can request corrections. Its backend, model, thinking level, preset and maximum review rounds are configurable.
Worker defaults
Choose providers, models, thinking levels, permissions and working rules. Inherited settings use the applicable defaults; an explicit selection overrides them.
Gang mode
Lets a role delegate to additional parallel subagents where the backend supports them. It is an extra option, not a requirement for starting a team.

Profiles and readable instructions

The team command center contains Overview, Delegator, Workers, Guardian, Flow, Deploy and Prompts. Profiles preserve different working arrangements, such as a small review group or a development team with a follow-up review.

Create and rename profiles, or import and export them. Team Builder helps assemble a setup. The prompt view shows the instructions that will be sent; add project rules and inspect their effect before using them for new work.

Track the actual work

The team board, worker reports, decisions, lead inbox and timeline support coordination. A completed report and an integrated branch are different states. Team views use Git state so a written completion claim alone does not count as a completed merge.

After a worker report, the profile can notify you, request review or merge automatically. Integration, pushing, release and approvals have separate settings. Check whether pushing actually deploys this particular project.

For direct collaboration between Claude and Codex inside a conversation, use shared chat. Human participation in sessions is handled through Collab.

Related topics