YouTube Automation Agent: an approval-first pipeline for running a YouTube channel from a local dashboard
🎬 Fully automated YouTube channel management with AI agents. Creates, optimizes & publishes videos 24/7. Works with FREE Gemini API or OpenAI. No coding required!
At a glance
- What is it?
- YouTube Automation Agent (darkzOGx/youtube-automation-agent) is a self-hosted Node.js tool that turns a channel brief into researched, narrated, rendered and scheduled YouTube videos, with human review gates and SQLite checkpoints at every stage. Its central design bet is that automation should fail closed rather than publish something unreviewed.
- Who is it for?
- Adopt AgentTube if you already run a channel, are comfortable with Node.js 18+ and API keys, and want a local dashboard that refuses to publish until quality, rights and review gates pass. Do not adopt it if you want a hosted service, if you have no budget for paid image or video providers, or if you expect the free Gemini tier to cover the whole pipeline without limits.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 20 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- darkzOGx/youtube-automation-agent5,223 ★ · +1,892
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| darkzOGx/youtube-automation-agent | 3.3k | 5.2k |
1,892 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The channel operator problem AgentTube is aimed at
Running a YouTube channel is a sequence of small jobs that each have their own tooling: picking a topic, writing a script, recording narration, sourcing visuals, cutting a video, writing a title and description, choosing a thumbnail, scheduling, then reading analytics. AgentTube's premise is that one local process can hold that whole sequence, and that the operator supplies strategy rather than keystrokes. The README frames the loop as research topics, write scripts, generate narration and visuals, assemble videos, optimize metadata, review, schedule, publish, then learn from analytics and from what the audience says.
The intended user is a solo operator or small team that already understands YouTube and wants throughput, not a beginner looking for a hosted product. The README states that no coding is required for the guided path, and the walkthrough does test credentials and guide YouTube authorization. But installing it means running npm install and npm start on your own machine, and every provider key, media file and channel token stays on that machine. That is the trade: you keep control of credentials and data, and you accept the operational work that comes with it.
Strategy in, scheduled videos out: the Autonomous Channel Operator
The entry point is the Autonomous Channel Operator. According to the README, you give it an objective, an audience, content pillars, a cadence and guardrails, and it turns those into researched content plans and production runs. That is a different shape from a prompt-to-video script.
Provider choice is deliberately broad. The README lists Gemini, OpenAI, OpenRouter, Kimi, MiMo, GLM, DeepSeek and MiniMax as text providers, and for video it names Seedance, MiniMax H3, Gemini Omni, Kling or Wan, with local slideshow rendering as the default. The free path is Gemini, which has free tiers for text and narration, plus local slideshow rendering. The paid path buys generated footage. Everything in between is a config decision, and the walkthrough is described as explaining each provider choice before testing it.
SQLite checkpoints and the Scene Repair Studio
The mechanism that holds the pipeline together is a local SQLite database. Every stage is checkpointed, the README states, so a crash or timeout resumes where it stopped instead of starting over.
The finer-grained version of the same idea is Scene Repair Studio, which lets you edit, reorder, lock, replace or regenerate a single scene, then rebuild the video. This is the most concrete answer the project gives to the usual failure of generative pipelines, which is that a single bad ten seconds forces a full re-render.
Finished videos still wait for fact review, media-rights confirmation and your approval, and the Evidence desk links each factual claim in the script to a verified source before approval.
Getting it running: commands, config and the readiness gate
The README's quick start is a short list of commands and a URL:
git clone https://github.com/darkzOGx/youtube-automation-agent.git cd youtube-automation-agent npm install npx playwright install chromium # renders slideshow videos; on Linux add --with-deps npm run walkthrough npm start
Then open http://localhost:3456. The walkthrough is the guided path added in v2.4.0 and is described as explaining each provider choice, testing credentials and guiding YouTube authorization. If you already know the stack, npm run setup is the shorter classic flow, and .env.example is documented as covering every setting.
Before switching on autonomous production, the dashboard has a Production readiness screen with a Run verified check button. The README describes what that check does: small live text and narration requests, verification of access to the connected YouTube channel, creation and decoding of a temporary MP4 containing audio and video. It does not upload anything. Paid image and video probes sit behind separate opt-in checkboxes, so the default run does not spend on image or video generation.
Where it stops: fail-closed publishing and the reconciliation case
The most interesting limitation is also a design choice. Finished videos wait for fact review, media-rights confirmation and your approval, and turning on autonomy doesn't skip those checks. Anyone expecting the unattended 24/7 operation the repository description advertises should read that twice.
The other constraint is economic. The free tier is real but partial: Gemini has free tiers for text and narration, and the default video path is local slideshow rendering. Paid image and video probes are separate opt-ins, and AI video generation comes with a cap on paid seconds. A channel that needs original footage on every upload is not running on free infrastructure.
DarkzSEO preflight and what the evidence layer actually stores
The Discoverability preflight runs advisory search and AI-answer checks from a bundled DarkzSEO audit.
Two other features are named but described only briefly: controlled growth experiments, which test approved title and thumbnail variants on a live video, require a 95% evidence threshold for a winner and restore the original before you decide, and an Outcome & ROI Studio, where you set a target (views, watch hours, net subscribers, engagement or revenue) and a budget and track progress. The README says missing data shows as unavailable, never as zero.
How this differs from a hosted AI video tool, and where the maintenance sits
The obvious alternative is a hosted generator such as a browser-based AI video service: you type a prompt, it returns a clip, and you upload it yourself. The difference in approach is not quality, it is where state lives. A hosted tool owns the render queue, the asset library and the billing relationship, and it forgets your channel between sessions. The project runs on your own machine and keeps your keys, media and channel data there, with stage checkpoints so a half-finished production can resume. It is also why you own the backup, the disk and the upgrade path.
The licence is MIT, which permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. That is a permissive arrangement, and it also means no warranty and no support obligation from the author. This is a description of the licence text, not legal advice; if you are building a business on it, have someone qualified read the LICENSE file.
Maintenance cost is the part the README does not quantify. The release history shows v2.3.0 and v2.4.0 both dated 2026-07-16, then v2.11.0 on 2026-10-14, so the project moves in dense bursts. Provider APIs change, and the project depends on many of them. The .env.example file is the single place that documents every setting, so treat it as the upgrade checklist rather than the README.
Editorial conclusion
Adopt AgentTube if you already run a channel, are comfortable with Node.js 18+ and API keys, and want a local dashboard that refuses to publish until quality, rights and review gates pass. Do not adopt it if you want a hosted service, if you have no budget for paid image or video providers, or if you expect the free Gemini tier to cover the whole pipeline without limits. Before activating autonomous production, run the dashboard's Production readiness check, then open .env.example and confirm every provider key, and the YouTube OAuth client saved as config/credentials.json.
Frequently asked questions
What does this YouTube automation agent actually do?
It runs a channel end to end: research topics, write scripts, generate narration and visuals, assemble videos, optimize metadata, review, schedule, publish, and learn from analytics and audience feedback. The review step sits between optimization and scheduling, which is where the safety gates apply.
How do I start the YouTube automation agent?
Clone the repository, install dependencies, run the walkthrough and then start it, then open http://localhost:3456. The walkthrough explains each provider choice, tests credentials and guides channel authorization; a shorter classic setup script exists for people who already know what they are doing, and the environment example documents every setting.
Does the readiness check cost money?
Not by default. The check makes small live text and narration requests, checks access to your channel, and builds and decodes a test MP4 without uploading anything. Paid image and video probes are separate opt-ins.
What happens if a run is interrupted?
Every generation stage writes a local SQLite checkpoint, so a provider timeout or an application restart can be resumed rather than restarted.
Which AI providers does it support?
For text it accepts OpenAI, OpenRouter, Gemini, Kimi, MiMo, GLM, DeepSeek or MiniMax keys, with the environment example keeping unused placeholders commented out. For video the default is a local slideshow, with a configurable order of remote generators including Seedance, MiniMax, Gemini Omni Flash, Kling and Wan, with FFmpeg installed through the optional ffmpeg-static dependency.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/darkzogx-youtube-automation-agent)Star history chart for your README
[](https://hysenlabs.com/projects/darkzogx-youtube-automation-agent)Was this useful?