I Left Claude Code Working All Night: The Morning Report

You go to bed at midnight with an approved queue of jobs and leave Claude Code working. At eight in the morning you open the file that should tell you what happened, and it is empty. Three jobs had really been finished during the night, and all three were thrown away. That is the part nobody warns you about: the work can be fine and the night still be useless, because you cannot prove anything. This video is the full recording of how it gets fixed. First you see the empty morning happen, and a read-only helper trace exactly where the night stopped. Then the fix, step by step: the night writes one line per job at the moment it happens, with the result and whether it ended done or blocked. A failure is recorded instead of killing the night. A night cut off halfway can resume without drafting anything twice. And the morning report reads that record instead of re-running the queue. You also see the queue's own limits being respected, the four one-line notices for the end of a night, and a verifier that tried to break the report and found two holes: it could claim things the night never did, and a job could ask to send itself. Both get closed and held down by tests, so a message only leaves with a person's signature. This is a real session on a demonstration project with invented data. No client information appears on screen. You do not need to know how to program to follow it. Flowara AI: the work is recorded, the report is read, a person signs. 0:00 Intro 0:51 The empty morning 2:03 A file that cannot lie 3:52 A night you can interrupt 5:31 Limits and notices 6:48 Nothing leaves unsigned 10:06 Close