Crews

A crew is a reusable team of roles arranged into named slots, with one lead and shared team conventions. Starting a crew creates a mission with a terminal for each slot.

Slots and the lead

Each slot selects a role and gives it a handle, such as coder or reviewer. These handles are the names members use when sending messages. They must be unique within the crew, even when two slots use the same saved role.

A launchable crew has at least one slot and exactly one lead. The lead receives the mission goal and coordinates the team. A reviewer can be a worker in one crew and the lead in another; lead status belongs to the slot, not the role template.

The crew page lets you reorder slots and override an individual slot's agent, model, effort or Codex speed. Inherited values come from the role, subject to the selected runtime's capabilities.

Team conventions

Team conventions are shared instructions appended for every member in a mission. Use them to establish who edits, who reviews, when to hand work over, what checks are required, and whether commits or other external actions are permitted. They do not apply when the role starts a direct chat.

For example, the default pair asks the coder to implement on a feature branch, the reviewer to inspect the working-tree diff, and both to repeat until review is clean. The default conventions leave changes uncommitted unless the goal explicitly authorizes Git actions.

Crew versus mission

The crew is the reusable starting configuration. The mission owns the live work, goal, feed and membership. Adding or removing a worker from a mission does not edit the saved crew. A mission can also start with No crew, then receive workers one at a time; that mission has no lead.

Follow Build a crew to make your own team.