<?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/36a7fc061fa3415aac550c4f63a1618e&quot; frameborder=&quot;0&quot; width=&quot;1729&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1729</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1729</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/36a7fc061fa3415aac550c4f63a1618e-c0aa7a33571e0630.gif</thumbnail_url><duration>562.302</duration><title>CodeClimbers Architecture Overview</title><description>Hi, I&apos;m Paul, the open source maintainer for CodeClimbers. In this video, I provide a rough cut of our architecture using Figma, showcasing the information flow from extensions to the walk time CLI. I explain how extensions pass information to the CLI, which then processes it and forwards it to a server. I highlight the unique architecture challenges we face and our approach to utilizing extensions for a better user experience. No specific action requested, just an overview of our architecture.</description></oembed>