Your changelog, on video, every Friday

Yes — that’s the entire model. One template project carries your branding, pacing, and structure; each release, the agent swaps in the week’s content and the video re-renders locally. Nothing gets rebuilt and nothing drifts off-brand, because every episode is a re-render of the same editable files rather than a new production. It’s the difference between publishing a series and commissioning videos.

A changelog video is a short recap — usually 30 to 60 seconds — that turns a release’s ship-notes into something people actually watch: features, fixes, one highlight. Text changelogs get skimmed; a video in the feed gets seen. Almost nobody makes them weekly because production cost defeats the habit, which is exactly the problem a scheduled agent plus a re-renderable CoAnimator project removes.

On a schedule — cron, CI, or a release workflow — the agent reads the merged pull requests, updates the existing project with the week’s scenes, and the coa CLI renders the MP4 headlessly. The CLI exits 0 on success and 1 on failure, so it slots into pipelines like any other build step. A human can stay in the loop as the final publish click.

They serve different readers, so keep both. The written changelog is the reference; the video is the reach — a 45-second recap posts to X, LinkedIn, and your community, where release notes never travel. Since the agent generates the video from the same merged PRs that produce the notes, the video costs a schedule entry rather than a production cycle.

Yes — branding lives in the template project: type, colors, motion, intro and outro. Weekly episodes only change the content scenes, so episode 40 looks like episode 1 without anyone policing it. If the brand refreshes, you update the one project and every future episode inherits the change on the next render.