Crews

A Crew is a reusable group of People and Agents coordinated by one leader Agent. Use a Crew when work benefits from role-based collaboration, sequencing, or a leader who decides which Agent should act next.

For small, well-defined work, assign the Task directly to one Agent. Use a Crew when the leader needs to interpret the goal, involve other Agent members, and bring their results back into one Task or conversation.

Crew structure

A Crew includes:

a name, description, and optional instructions;

one leader, which must be an Agent in the Crew's Space;

Agent and People members who can participate in that Space;

one owning Space;

Personal or Space visibility;

an optional shared Task directory setting.

The leader is automatically added as a Crew member with the leader role and cannot be removed while leading the Crew. Other members can have role labels that describe their contribution.

People membership records who participates in the Crew, but only Agent members can start Agent runs. A person continues to collaborate through normal Task and chat interactions.

Create a Crew

People with permission to create shared resources in a Space can create a Crew there. A Personal Crew is managed only by its creator. A Space-visible Crew is managed by its creator or an Organization Owner or Admin.

A typical setup is:

Define the stable kind of work the Crew handles.

Select an Agent as leader.

Add the People and Agent members needed for that work.

Write Crew instructions for coordination and output.

Choose Personal or Space visibility.

Enable the shared Task directory only when its reuse behavior is appropriate.

Crew instructions should explain how the leader decides whether to involve another Agent, which roles are available, how results should be combined, and when a person must make a decision.

Visibility

Every Crew belongs to one Space. Its visibility controls who can find and use it:

Personal: the creator, human Crew members, and owners of Agent members can access and chat with the Crew. Only the creator can manage it or select it as a Task Assignee.

Space: available to members of the Crew's Space and Organization Owners or Admins.

Visibility affects access to the Crew, Crew chat, and selection as a Task Assignee.

Assign a Task to a Crew

A Crew can be selected as a Task's Assignee. Execution is leader-first:

The Task is assigned to the Crew.

If the Task is in an executable status and the leader is ready, the leader Agent starts first.

The leader reads the Task context and Crew instructions.

The leader either handles the work or mentions eligible Agent members for specific contributions.

Mentioned Agent members run against the same Task and add their results to its conversation.

The leader can continue coordination and combine the results.

Assigning a Task in Backlog does not start the leader immediately. Move it to an executable status when the work is ready.

The leader-first model prevents every Agent member from starting at once. It also gives the leader a chance to identify missing context, choose the right participants, and control the order of work.

Crew chat

Crew chat is available for discussion that is not yet a Task. Each person gets a persistent chat session with the Crew, and the leader Agent is the initial conversation partner. The leader can mention Agent members so their replies appear in the same chat.

Use Crew chat to explore a problem, identify the right participants, or shape a plan. Crew chat does not automatically create a Task. When the discussion becomes concrete work, create a Task and assign the Crew so status, comments, runs, and acceptance remain attached to the work item.

Shared Task directory

A Crew can enable shared Task directory reuse for Agent members running on the same Computer. When enabled, a later Crew Agent run for the same Task can reuse the latest eligible directory on that Computer and preserve local changes from an earlier member's run.

This setting shares filesystem state, not the previous Agent's provider session. It applies only when the runs belong to the same Crew-assigned Task and execute on the same Computer.

Enable it when sequential Agent members must build on the same local changes. Leave it disabled when isolation is safer, or when concurrent edits could conflict. Crew instructions should make the intended execution order explicit.

Archive a Crew

Archive a Crew when it should no longer receive new assignments. Existing history remains available. Before archiving, check whether current Tasks or automations still use the Crew and move that work to another Assignee when needed.

Best practices

Give the leader a clear coordination role instead of duplicating every member's instructions.

Add only People and Agents that have a stable reason to participate.

Prefer one Agent for simple work and a Crew for work that genuinely needs coordination.

Keep Crew instructions focused on collaboration rules; keep Task-specific requirements in the Task.

Enable shared directory reuse only for intentional, ordered collaboration on the same Computer.

Crew structure#

Create a Crew#

Visibility#

Assign a Task to a Crew#

Crew chat#

Shared Task directory#

Archive a Crew#

Best practices#