One TypeScript runtime for goal-driven teams and explicit task DAGs. Route the topology, schedule ready work, gate consequential actions, and keep the evidence in your own environment.
Start with an outcome through runTeam(), or supply the task graph through runTasks().
An explicit mode, governance policy, or ExecutionRouter selects the topology.
The event-driven scheduler starts dependents as soon as their prerequisites complete.
Approve the plan, each ready task, and every consequential tool call at the right boundary.
Routing, task results, traces, usage, and governance conclusions stay inspectable.
The layers below are shipped in the public package. Each one links to the version-matched Reference or guide.
Generate a reviewable task DAG from a goal, execute a graph you define, or short-circuit eligible work to one agent. Explicit mode and governance declarations win; custom routers remain advisory and fall back safely.
runTeam · runTasks · mode · ExecutionRouter · routingDecisionExecution routing→Event-driven execution removes unrelated round barriers. Choose dependency-first, round-robin, least-busy, capability-match, or composite assignment, with hard task requirements and task-scoped results.
onTaskDispatch · requires · taskResults · dependencyPayloadTask scheduling→Declare required or preferred roles, ordered review paths, and budget-aware degradation. Gate plans, ready tasks, and consequential tools separately, then inspect governanceConclusion instead of inferring compliance.
governance · onPlanReady · onTaskDispatch · onToolCallOrchestration controls→Retries, model fallbacks, timeouts, loop detection, and token or estimated-cost budgets bound execution. Checkpoints persist completed task boundaries so restore can skip work already done.
fallbacks · budgets · checkpoint · restoreCheckpoint and resume→Stable run identity, execution receipts, TraceStore, the offline Run Viewer, and optional OpenTelemetry make the run inspectable. EvalSets, Scorers, reports, and gates turn that evidence into regression checks.
receipt · TraceStore · renderRunViewer · EvalSet · GateVerdictObservability and evaluation→Mix cloud and local models in one team, connect MCP servers as opt-in tools, and run external coding agents through ACP or process backends. Core remains an embeddable library, not a hosted service.
providers · MCP · ACP · process backend · default-denyIntegrations→The public site follows the latest package released on both GitHub and npm. Development-only main features stay out of the shipped surface until they are published.