Skip to main content

Module coordinator

Module coordinator 

Source
Expand description

Deterministic, no-LLM signal-tag router. See the crate-level “Two paths for agent-to-agent delegation” section: prefer delegate::DelegateTool for model-driven peer collaboration and reach for coordinator::CoordinatorAgent only when the topology is fixed and a free dispatch hop matters. CoordinatorAgentdeterministic signal-tag router. Routes an investigation to the first registered specialist whose signal tag matches the context, with no model in the loop.

This is the optional delegation path. For autonomous agent-to-agent collaboration where the parent’s LLM should choose its peer, use crate::delegate::DelegateTool instead. Reach for the coordinator only when the routing topology is fixed and a free, no-LLM dispatch hop is the point — for example, an overseer fanning one specialist out per partition before any model has loaded.

The coordinator is itself an Agent so workflows can dispatch to it uniformly. It owns no skills of its own; on step it inspects ctx.signals, picks the first matching specialist by name, and delegates. Specialists are stored as Arc<dyn Agent>, so any kernel agent (including future custom impls) can be registered.

Structs§

CoordinatorAgent
Routes investigations across a fixed set of specialist agents.
CoordinatorBuilder
RoutingRule
One routing rule: any of signals matching the context routes to agent_name. First-match wins.