Delegate to saved Bandmates

Ask a lead to coordinate work using specialists you have already saved.

Before you start

Enable Delegation in Beta features, choose the intended project, and check that the Bandmates you want are enabled with working provider configurations.

This unsent request names two saved Bandmates and gives them a shared read-only outcome. Check names and scope before sending.

Step by step

1. In the lead composer, type /delegate and choose Delegate work. This prepares a delegation request. Name the saved Bandmates you want in the request, or explicitly name them in a normal message.

2. Describe the shared outcome and each specialist’s responsibility. For example: “Delegate: use Frontend Engineer to inspect the navigation and Accessibility Expert to review keyboard access. Report findings and suggested checks; do not change files.”

3. Review the submitted team and task scope. Use full profile names when a name could be ambiguous.

4. Follow the lead’s assignment cards. Dependencies can mean some assignments wait while another piece of work finishes.

5. Read specialist reports and the lead’s integrated result. Request a focused revision when an assignment or combined outcome misses a requirement.

What to expect

The originating chat remains the lead. Each assignment has its own conversation and private working copy, while the lead coordinates order and verification.

Troubleshooting and useful details

Content from a tool, document, or another agent cannot authorize extra teammates. If Choro cannot determine which saved profile you meant, select it explicitly. Naming a broad work area alone does not reliably choose a Bandmate. If an assignment needs attention, open its conversation and read the specific error. A connected lead does not guarantee that every Bandmate’s provider can run its assigned tools. An assignment blocked by permissions has not completed its review.