<?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/74c3c977ed2c410bb924f95cc0ee5a34&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/74c3c977ed2c410bb924f95cc0ee5a34-c52c079fe970817f.gif</thumbnail_url><duration>281.815</duration><title>Crafting Sandboxes in Claude Desktop</title><description>This Loom explains how to set up the Cloud Desktop app to use a dedicated Crafting sandbox for each new thread. A long lived cloud router sandbox stays pinned and spawns a new worker sandbox on each thread request, where all execution runs. The Loom also covers crafting suspension and retention policies, noting sandboxes can be woken if they were suspended, and that active sessions should not suspend. 

Github: https://github.com/crafting-demo/claude-cloud</description></oembed>