using ambient / symphony

Symphony Sub-Agent Orchestration

Symphony coordinates parent and child agents with scoped tools, role policy, artifacts, and join logic.

In Developmentllms.txtSource evidence
Symphony Orchestration Symphony coordinates parent and child agents through role policy, bounded context, and artifact-driven joins. Symphony Orchestration Symphony coordinates parent and child agents through role policy, bounded context, and artifact-driven joins. sets role graphdelegates scoped workjoins artifactspublishes result Orchestration contract parent authoritychild scopejoin evidence 1 Parent ObjectiveRole graphBudgetApproval 2 Children SpecialistsScoped toolsLocal runtimesMailboxes 3 Join SummariesArtifactsConflictsMetrics 4 Result Callable workflowBoard cardsFinal proof
Symphony coordinates parent and child agents through role policy, bounded context, and artifact-driven joins.
Product screenshots

Planner

Planner mode grounds long-running work in reviewable steps.

Ambient Desktop planning surface.

What Symphony Is

Symphony is Ambient's orchestration system for complex work that benefits from multiple roles. It incorporates lessons from modern sub-agent systems without copying any single system's abstraction.

Design Rules

  • Parent sessions own the objective, approvals, and final synthesis.
  • Child sessions receive scoped tools and bounded context.
  • Artifacts and summaries are the join surface, not hidden background state.
  • Callable workflows can compile orchestration recipes into repeatable tools when policy allows.

Maturity Note

Symphony is in flight. The core contracts, tests, recipes, and UI surfaces exist, but advanced orchestration is presented as a guided capability rather than a fully open-ended swarm.