Autonomy, rooms, and Conductor

Autonomy is the workspace for organizing several agent tasks. Use it when work can be split into clear, independent pieces.

When to use one thread#

Stay in one thread when:

• one area owns the change;
• the steps depend on each other;
• the task is mostly sequential;
• coordinating several tasks would take longer than doing the work.

When to use a room#

Create a room when:

• several tasks can progress independently;
• each task can have clear ownership;
• one initiative needs a shared objective;
• you want one place to review progress and combined work.

Give the room an outcome-focused objective, such as:

Make session expiry consistent across the app, including refresh and offline
recovery, with focused regression coverage.

General Hall and named rooms#

• General Hall is useful for triage, ideas, and stand-alone tasks.
• A named room groups tasks that belong to one initiative.

Autonomy offers different views for the same work:

• Exposé shows where agents are working;
• Kanban shows task status;
• Detailed brings a named room's conversations and changes together.

Create a clear task#

A good room task includes:

• a short outcome-based title;
• a description of the expected result;
• the workspace it belongs to;
• the files or area it owns;
• dependencies on other tasks;
• the check that proves it is finished.

Use Plan first when you want to review the approach. A created task does not start until you run it.

Prevent collisions#

Before several tasks run:

1. Give each one a separate area of ownership.
2. Name one person or agent to combine shared changes.
3. Decide who runs the final project-wide checks.
4. Start dependent tasks only after their inputs are ready.

Tasks working in the same room may see shared changes. Avoid assigning the same important file to several writers.

Use Conductor#

Conductor can turn one larger objective into rooms and tasks, then start and steer the work.

A useful Conductor request says:

• which workspaces are involved;
• the final outcome;
• how work should be divided;
• which tasks can start immediately;
• which tasks must wait;
• who owns combined review and validation;
• what requires your approval.

Example:

Coordinate consistent search filters across the selected projects.

Create one room. Split the work into investigation, app changes, service
changes, focused checks, and final review. Give every task separate ownership.
Start the independent tasks now, but wait to start final review until they are
complete. Ask before any compatibility-breaking change. Do not commit or push.

Review the room#

Do not review only the individual task summaries. Review the combined result, check the room's shared objective, and run the final validation before merging room work.

Next#

Automate a repeated task with Scheduled Tasks.

← Advanced workflows · User guide · Documentation use notice