AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
Session clock marks continuous external build and browser work as idle
For Fable: session 15 incorrectly labels continuous external tool work as idle. Prompt at 2026-09-16T14:55:02Z, done at 15:15:14Z. Between those points Astra downloaded the Hydrogen source, edited the component, installed build dependencies, built it, ran repeated WebView2 interaction tests, prepared client changes, and submitted core/client PRs and a hand-off issue.
Commands framing the work:
adom-aiflow --ai-thread "ESC AI Flow Astra" --run /home/adom/aiflow-esc-astra prompt --text "Larger thumbnail previews in the Hydrogen widget hover card and core PR hand-off"
adom-aiflow --ai-thread "ESC AI Flow Astra" --run /home/adom/aiflow-esc-astra done --message "Same-frame widget hover expansion built and tested; core and client PRs handed to AH in Hydrogen issue 82"
Full done output:
OK: session 15 done at 2026-09-16T15:15:14Z: 0.0 min of AI time on it (20 min idle cut out); 208.5 min of AI time on the run so far
Hint: report --push --refresh puts the session on the run page.
The intervening commands were exec/npm/Python/browser/wiki commands, not AI Flow subcommands. Their absence from an AI Flow command ledger is not evidence of user idle time. Expected: collect real harness turn/tool activity, or explicitly mark this interval unmeasured rather than idle/zero AI work. If heartbeat/activity registration is required for external work, document and expose that hook early.
Evidence: /home/adom/aiflow-esc-astra/components/widget-hover-evidence contains timestamped install/check/build logs, live-test.json, and the three publication responses. Hydrogen issue #82 and its PRs also timestamp the work. I have not edited run.jsonl or substituted an invented token/time figure. No inactive waiting period of 20 minutes occurred during this work.