After rebuilding AG16, the next question: can the content production be automated too?
Back to the AG16 storyAG16 was shipped. The YouTube channel existed. But producing even a 60-second Short every week required context-switching between a dozen tasks: reviewing what changed in the code, picking an angle, writing a script that matched the channel voice, and tracking what performed.
The content wasn't hard to make. Remembering to make it — and keeping it consistent — was. What if the entire production chain was an autonomous agent?
Five steps. Zero manual intervention. Runs every day on cron.
Scans git history across all repos under c:/bench. Pulls yesterday's commits, diffs, and file changes into structured context.
Emails three angle suggestions via Gmail API. Waits for a reply — 1, 2, 3, or a custom angle. Polls at noon and 3pm. No reply? No script. The human stays in the loop on what, not how.
direction.jsSends the chosen direction + channel voice guidelines to Claude. Returns a structured script: hook, demo, reveal, CTA — plus a title, thumbnail concept, and capture mode for the screen recorder.
generate.jsPulls weekly YouTube Analytics — views, watch time, retention, click-through. Saves snapshots so the system builds a record of what works over time.
feedback.jsOrchestrates the whole cycle. Harvest at 9am. Direction email at 9:05. Poll at noon and 3pm. Generate at 6pm. Analytics pull on Monday morning. All Node.js, all local.
cron.jsThe difference between a toy and a tool.
This agent doesn't just call an API. It crosses four systems: git, Gmail, Claude, and YouTube Analytics. Each has its own auth, rate limits, and failure modes.
You approve the direction with a one-tap email reply. Everything after that — script generation, file output, analytics collection — runs autonomously on pm2 with no further input. Human judgment on what. Full automation on how.
Every external input — email replies, git commit messages, API responses — is sanitized before it touches a prompt. Length-limited. Pattern-stripped. Treated as data, not instructions.
What the pipeline does while you're doing other things.
scripts/
AG16 is the app. The pipeline is the engine behind the content.