<?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/2eec592ef6c540d29760659f753ec6fb&quot; frameborder=&quot;0&quot; width=&quot;1482&quot; height=&quot;1111&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1111</height><width>1482</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1111</thumbnail_height><thumbnail_width>1482</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/2eec592ef6c540d29760659f753ec6fb-8165f3929033c6a8.gif</thumbnail_url><duration>59.2677</duration><title>How to fix OpenClaw stuck in &amp;quot;starting&amp;quot; state</title><description>In this video, I address a common issue where your agent may get stuck in a starting state due to incorrect open clock configuration. To resolve this, I recommend running the command &apos;open clock doctor --fix&apos; in your terminal, which usually identifies and auto-fixes the problem. I also share a screenshot of an example error related to an unrecognized key maintenance. Please make sure to follow these steps if you encounter similar issues. That&apos;s all you need to do to get your agent back on track!</description></oembed>