<?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/4dd465ad38f34adc9cc4ffdd9ccde012&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/4dd465ad38f34adc9cc4ffdd9ccde012-cb7b21721fc5816a.gif</thumbnail_url><duration>248.510333</duration><title>Crafting Sandboxes in Claude Desktop</title><description>This Loom explains how to set up Claude Desktop to create a separate crafting sandbox for each new thread. It describes copying a prepared prompt into Claude, which then creates a worker template, a sandbox pool with checkout, an SSH profile to select a cracking sandbox, and a lightweight CS CLI skill. A key component is the long lived pinned CloudRouter sandbox that receives thread requests and spawns dedicated worker sandboxes for execution in the Cloud Code session. The Loom also notes sandbox suspension and retention policies, including possible wakeup when returning, and that active continuous sessions should not suspend mid session.</description></oembed>