Skip to main content

Module facade

Module facade 

Source
Expand description

The seam between the merged agents__* family and the two engines it drives. Every verb that takes a target resolves it here, so the routing rule lives in one place rather than at each call site.

Re-exportsΒ§

use std::sync::Arc; πŸ”’
use crate::SessionSlot; πŸ”’
use crate::mcp::agents::target::AgentTarget; πŸ”’
use crate::mcp::agents::target::LEAD_LABEL; πŸ”’
use crate::mcp::peers::facade::DeliverError; πŸ”’
use crate::mcp::peers::facade::WorkspaceFacade; πŸ”’
use crate::mcp::peers::types::WrappedPrompt; πŸ”’
use crate::mcp::workers::facade::WorkerDeliverError; πŸ”’
use crate::mcp::workers::facade::WorkerFacade; πŸ”’
use crate::mcp::workers::facade::WorkerLeadDeliverError; πŸ”’

StructsΒ§

AgentDispatcher
The two engines, both held: a target inside the caller’s project is served by the workers engine and one outside it by the peers engine. Keeping both is what makes this a dispatcher rather than a third implementation.

FunctionsΒ§

lead_deliver_message πŸ”’
label naming a project’s own agent is worker-only addressing: a lead has no lead above it to talk back to.
worker_deliver_message πŸ”’