Claude Code can write Blender Python all day, but it can’t tell whether the result looks right from the code. One small loop fixed most of that, and I’ve used it on 13 YouTube Shorts so far. The loop Claude writes the scene as a Python script and runs it with blender -b . A small script renders 5 to 10 frames at 30% size and stitches them into one contact sheet image. Claude reads the image, names the worst problem and fixes only that. Repeat until nothing is obviously wrong, then do the final render. What made it work Fix one thing per pass. When it tried to fix everything at once, it broke things that were fine. Low res test frames are enough to catch floating props, bad poses and broken shots, and they take seconds. Every fix goes into LESSONS.md as one line, and new sessions read it first. Examples: matrix_world is stale until you call view_layer.update() , two keys within half a frame collapse, and frame_set on a non-context scene doesn’t evaluate animation in background mode. Keep one timeline file. Scenes, captions and audio all read the same timings, so one change doesn’t desync everything. Where it still falls short Character animation. People on r/ClaudeAI told me the quality is bad today, and for hand-animation standards they’re right. This gets you to watchable, not to Pixar. Numbers About 1,300 frames per video at 1.6 to 4.4 seconds each on an 18 GB M3 Pro, with EEVEE. The contact sheet script, one real scene and 28 of the lessons are in a free starter . Disclosure: I also sell the full pipeline there. Claude helped write this. Happy to answer questions, especially if you’ve got a better way to review renders. submitted by /u/FlightSimCentralYT
Originally posted by u/FlightSimCentralYT on r/ClaudeCode