<?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/a2e8f39cd02e4f54a07711ca429fd32b&quot; frameborder=&quot;0&quot; width=&quot;1916&quot; height=&quot;1437&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1437</height><width>1916</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1437</thumbnail_height><thumbnail_width>1916</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a2e8f39cd02e4f54a07711ca429fd32b-c87ad3dcf60374a3.gif</thumbnail_url><duration>119.403</duration><title>Debuggable CLI Demo with Detailed Logging</title><description>I wanted to show the command line interface demo and how it works. I also added a detailed logging feature that records every session and every AI tool execution, with structured debug, warning, and logging messages to make it easier to understand what went wrong. The CLI runs the same scheduling engine logic without AI, including priority sorting, conflict detection, recurring tasks, and filtering across two paths. I ran it and the output showed created profiles, generating and sorting schedules, detecting conflicts, auto scheduling, and completion. No specific action is requested from viewers.</description></oembed>