The short answer

Agent Room coordination resolves explicit participant references, then an eligible injected router, then a declared default. Membership and revision constraints determine eligible agent participants. A routing result selects a target; task execution and external effects keep their own policy checks.

Know which rule selected the recipient

The routing documentation gives an explicit order: participant references, an injected router limited to eligible agents, and a declared default. This makes selection inspectable across repeated processing.

For an illustrative analysis Room, a request addressing the research participant should not be explained as a generic classifier choice. Retain enough information to distinguish an explicit reference from a fallback. That helps diagnose an unexpected target without blaming model output by default.

Eligibility depends on current Room membership

The participant lifecycle is revisioned independently from Room state and can constrain permitted agent revisions. An active Room does not imply every visible participant is a valid execution target.

Human participants contribute and review; they are not silently selected as agents for task execution. Build your router's candidate input from the eligible agent set rather than every name displayed in the conversation.

Use an explicit default instead of a hidden guess

A declared default can make a general request routable, but its role should be deliberate. In an illustrative app, the default may triage work rather than execute a specialized operation itself.

If the intended target is unavailable, follow the configured eligibility and error behavior. Do not widen the candidate set to another tenant or an unrelated agent catalog merely to produce a response. That fallback changes the authority and context assumptions of the Room.

Selection does not authorize delegation or effects

A routing decision is followed by policy-checked task creation and execution. A formal transfer between participants may require the typed Handoff lifecycle, including acceptance and revision constraints.

Likewise, the chosen participant does not gain every tool permission needed for a requested action. Your application should be able to report “selected, but denied execution” without treating those results as contradictory.

Test the route with changing membership

  • Address an eligible participant explicitly.
  • Submit unaddressed work that exercises the injected router.
  • Exercise the declared default under its intended conditions.
  • Change a participant's eligibility before execution.
  • Verify that selection cannot bypass the subsequent policy boundary.

The integrated scenario provides the surrounding services for a bounded evaluation. Keep routing evidence, task identity and run outcome connected so an operator can see where work changed from selection into execution.

Sources and further reading

Documentation reviewed . Consult the linked documentation for current implementation details.