Builder

Orchestrator + sub-agent builder

Create workspace-scoped agents, edit prompts and skill references, and publish the generated agent YAML back into the Go backend.

Loading…

Create or select a workspace to begin editing.

Live YAML preview

This is exactly what gets posted to /api/agents in the Go backend.

# Select an agent to preview

Selection summary

WorkspaceNone

Selected agentNone

Skill references0

Saved skill drafts0

Suggested pattern: persist the orchestrator and every sub-agent as separate YAML files, then reference them via delegation skills or explicit routing logic in your runtime.