{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/f2c52e824b1f41a8a18000a2df67adf8\" frameborder=\"0\" width=\"1744\" height=\"1308\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1308,"width":1744,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1308,"thumbnail_width":1744,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/f2c52e824b1f41a8a18000a2df67adf8-a800abb0615b0b85.gif","duration":237.45,"title":"Using Corals Agent Teams to Parallelize Development","description":"This Loom walks through how the speaker uses Corals agent teams to parallelize and potentially delay development work. The system uses an orchestrator plus specialist agents such as a lead developer, DevOps, and QA, each primed with prompts for their expertise and introduced to the orchestrator. A complex opening prompt leads the orchestrator to break the work into tasks that are delegated on a Coral Board, with agents claiming tasks and communicating via a shared message board. The team health monitor tracks agent availability and task counts, periodically updating the orchestrator to handle blockers, and the Loom also covers Corals UI features like a diff viewer, editor, task queue, artifacts, and analytics, running on Linux and Mac."}