<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f8b67486801b4cee8d8970fa3d405553&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f8b67486801b4cee8d8970fa3d405553-13c7cf9700147b2f.gif</thumbnail_url><duration>627.868</duration><title>Preventing Agent Conflicts in Git Changes</title><description>This Loom focuses on detecting conflicts when two agents work on the same change in a Git-based workflow. The author, Alexey, has been using agents for over a year and has run into issues like limited storage space and lack of coordination, especially with Rust worktrees. After researching problems from sources including Git and social media such as Hacker News, Reddit, and X, he chose to address the specific case where conflicts could happen before merging. By having agents coordinate which parts they handle, merge conflicts can be avoided and merging becomes easier, which was the core focus for the competition.</description></oembed>