Projects

The whole video lives as project files: the animation, the timeline, and the narration, all plain and editable.

Video as code

Project files diff and review like any other source. They sit in a git repository next to the product they demonstrate, which changes what a stale demo costs: when the UI changes, the fix is a pull request, not a re-shoot.

It is also what makes scheduled video possible. A cron job, an agent reading the week's merged PRs, and coa render at the end will keep a changelog video current without anyone opening the app.

Why agents can edit them

Because everything the agent needs to touch is an ordinary file, the agent's normal read–edit–run loop applies with no adapter in between. The editor reflects each change on the stage immediately, so a human directing the work sees the result before the agent's next turn rather than after a batch export.

Packaged projects

A project can also travel as a single .coa file holding the whole video. Share it, back it up, reopen it in a year, change one thing, re-render. Nothing is baked: there is no flattened output you have to work around, because the project is the video.

coa render accepts one directly:

coa render launch-video.coa --out launch.mp4

Your footage stays local

Nothing about the app depends on network access once it is installed, and rendering never leaves your machine. Unreleased product footage stays on your hardware.