app

AI Flow

Public Made by Adom

by adom

Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.

kicadpcbedaroutingplacementcopper poursablationcurrent densitythermalkelvincomparison
Overview Files Skills Discover Packages Releases Dependencies Issues10 Breadcrumbs Pull Requests Activity
Closed PR #67 released in 0.2.52 on 5 Nov 2026 bug report

finish/deliver re-creates clips that were moved off the run folder as 0-byte placeholders, then flags them truncated

Glenn Jones · ·closed by Colby Knox

We kept a list of tool issues as we worked on a project, the 772 power module (LM251772), a 4-layer board built with AI Flow on the Fusion lane, and set them aside so they wouldn't slow the build down. Now that the project is finished, we're filing them together. Some were seen on earlier versions; where we could, we checked that they still apply.

Versions: adom-aiflow 0.2.44, Fusion lane.

What happens: our rule is that raw screen recordings can't stay on C:, so after each step we moved the raw takes to another drive. At finish / deliver, AI Flow's "pulled N clips" step re-created each missing clip in the run folder as an empty 0-byte file, then flagged those files as truncated or blank. deliver refused until we replaced the placeholders with symlinks to the moved copies (and used --accept-suspect for some old clips).

Expected: a clip that was moved (or is missing) is reported as missing, not replaced with an empty file; ideally the run can record where a clip was moved to, so compose can still use it.

No design files attached; happy to describe more on request.

1 Reply

Colby Knox marked this in progress ·
Colby Knox mentioned this in pull request #67 ·
Colby Knox ·

Glenn, thanks. adom-aiflow 0.2.52 stops an empty clip file from being left behind: a pull that doesn't land now removes any 0-byte file and the clip is reported as missing.

I couldn't reproduce your case. A failed pull with today's Adom Bridge leaves no empty file, so the fix is covered by a unit test, not by your exact steps. I also didn't find what made the files on 0.2.44. deliver no longer refuses over these clips either; it warns and carries on.

Not added: recording where a clip was moved to, so compose can still use it. Your symlinks still work for that, because a symlink to a real file counts as the clip.

I'm closing this. If you still see 0-byte clips on 0.2.52, please reopen it with the finish output.

Upgrade: tell your AI "give me the latest adom-aiflow" (or adom-wiki pkg install adom/adom-aiflow); adom-aiflow --version says 0.2.52.

Colby Knox removed the in progress marker ·
Colby Knox closed this ·

Log in to reply.