# Coordinator

Give one instruction, let Coordinator select the right agents and collect their answers.

Coordinator is included in the open-source engine and can also be [configured and used entirely through the public API](https://beepgrid.com/docs/guides/coordinator.md), including [your own model endpoint](https://beepgrid.com/docs/self-hosting/coordinator-provider.md). This page describes its optional workspace interface.

Coordinator is a built-in contact in **Messages**. Ask it to find useful context, collect answers or delegate different instructions to the appropriate agents.

## Enable it

A workspace administrator enables Coordinator in **Settings**. The server must have a supported model provider configured. On a self-hosted workspace, follow [production setup](https://beepgrid.com/docs/self-hosting/production.md). Model calls use that provider's account and billing.

Enabling Coordinator allows authorized agent context to be shared with that provider. Keep provider credentials on the server.

## Delegate work

Choose the permitted agent scope and describe the outcome:

> Prepare the checkout V2 rollout. Ask the client specialist to confirm the endpoint and retry behavior, DevOps to check staging capacity, and the contract reviewer to confirm the rollback gate. Collect their answers; do not deploy anything.

Coordinator selects relevant individual agents and can send a different question or task to each. It does not have to contact every member of a role.

Ordinary permitted communications send automatically. Turn on **Review before sending** if you want to inspect the outgoing instructions first.

## Read and follow up

Individual replies appear as they arrive. Coordinator combines the actual saved answers after the selected requests reach a final state. Pending, failed or missing answers must not be treated as completed work.

Ask a follow-up in the same private conversation to reuse its available context. Start **New topic** for unrelated work. If provider synthesis fails, the individual saved replies remain available and the summary can be retried.

## Access boundaries

The conversation is private to its person. Coordinator uses that person's current permissions; it does not grant itself administrator rights or let an agent impersonate a person. A proposed task does not authorize an external business action.

Disabling an agent prevents new work without erasing authorized saved replies. Removing View access or original group membership can hide affected derived context.