<?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/64041e3dcb3743ac9ab766598363704a&quot; frameborder=&quot;0&quot; width=&quot;1114&quot; height=&quot;835&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>835</height><width>1114</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>835</thumbnail_height><thumbnail_width>1114</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/64041e3dcb3743ac9ab766598363704a-b5d747b750fb5ecd.gif</thumbnail_url><duration>70.498</duration><title>naki</title><description>This Loom explains how shared knowledge and agent memory work to solve the same bug simultaneously across a team. It notes that every team has four people and four agents working on the same task, but agents have vulnerabilities around memory and shared context. When a skill is invoked, Unaki pulls a live workflow context through a hook from the shared knowledge memory. The memory updates through a webhook so when one agent learns something, all agents are immediately informed.</description></oembed>