{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/460337d003c44718a76f7e5bc66926db\" frameborder=\"0\" width=\"1108\" height=\"831\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":831,"width":1108,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":831,"thumbnail_width":1108,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/460337d003c44718a76f7e5bc66926db-3f715df2547916c4.gif","duration":290.861,"title":"How I manage AI agent conflicts with Jujutsu","description":"Three Claude Code agents working in parallel on the same repo, each in its own Jujutsu workspace, in macOS sandboxes with bypass-permissions. When two of them produce a conflict, I dispatch a fourth agent to resolve it.                                                                                \n\nCode generation got cheap. Review, integration, and judgement are now the work - this setup puts your attention there.\n\nBuilt on Jujutsu (https://github.com/jj-vcs/jj) and VisualJJ (https://www.visualjj.com)."}