Edit flows, resources, and run state without moving code execution to the cloud.
Your normal local provider profile receives a Loom overlay and MCP tools.
Child agents are exposed as typed tools such as delegate, report, status, and cancel.
Loom-managed child agents run with scoped homes, scoped resources, and mandatory reports.
Runtime contract
The split is the product.
Leaders come from providers
The root session is a host-backed Claude Code or Codex process with prompt-only Loom overlay.
Workers are managed
Child sessions are created by Loom for bounded work and report back through the local trace layer.
MCP is the transport
Delegation is tool-shaped and validated instead of being copied as shell commands by the leader.
YAML stays source of truth
Flows, roles, hooks, and skills remain reviewable files that can be shared through Git.
Deep docs
Implementation notes stay in Markdown.
The website pages are the public surface. The detailed engineering notes are still available in the repository: open the docs directory.