Every week, without anyone opening a laptop, the AI Weekly gets a new episode: researched, written, narrated, rendered as a video, and uploaded to YouTube. The whole thing runs inside the same workspace every OnePress user gets — no special pipeline, no editor in the loop.
The pipeline
- A scheduled automation fires a prompt on a cron — the same kind any user can create in a minute: "research this week's AI news, write the episode, produce the audio and video, upload it unlisted."
- The agent researches with live web search, writes the show notes and a script, and files everything in the workspace as plain files.
- Narration and video are produced with the same media tools users have — voice synthesis for the audio version, generated footage or a licensed presenter for the video.
- Publishing is deliberately human-approved. The upload tool supports going straight to public, but the workflow default is unlisted — the artifact gets produced automatically, the publish button stays with a person.
Why we run it
Partly it's distribution — a YouTube channel and an RSS feed that update themselves. Mostly it's proof: if an agent can run a recurring production job end-to-end for us, it can run yours — a weekly client report, an investor update, a podcast episode series. The gap between "demo" and "real recurring work" is where most AI products quietly die; we wanted the receipts.
If you run a recurring content pipeline and want to see what it looks like under one workspace, that's exactly what we built content ops for.