gitwtfhub

wtf is shorts-factory?

dikshantbhatia09/shorts-factory — explained in plain English

Analysis updated 2026-05-18

68TypeScriptAudience · developerComplexity · 5/5Setup · hard

TL;DR

A self-hosted, AI-driven pipeline that autonomously researches, scripts, renders, publishes, and learns from a faceless YouTube Shorts channel.

Mindmap

mindmap
  root((repo))
    What it does
      Researches topics
      Validates against competitor data
      Renders animated videos
      Publishes automatically
      Learns from analytics weekly
    Tech stack
      TypeScript
      Python
      Claude Code CLI
      Remotion
      YouTube Data API
    Use cases
      Run an autonomous faceless channel
      Study competitor Shorts techniques
      Automate video research to publish
    Audience
      Developers experimenting with AI automation
    Setup
      Requires GPU and Docker
      Requires Claude subscription

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Study a working reference architecture for a fully autonomous content pipeline.

REASON 2

Automate researching and validating video topics before producing content.

REASON 3

Build a self improving system that rewrites its own rules from real analytics.

REASON 4

Learn how to structure a variation engine that avoids repetitive automated content.

What's in the stack?

TypeScriptPythonClaude CodeRemotionFFmpegYouTube Data API

How it stacks up

dikshantbhatia09/shorts-factoryezbuilder/chatgpt2codexmarinedotsh/better-auth-referral
Stars686868
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyhardmoderateeasy
Complexity5/53/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1day+

Requires a local GPU, Docker, a Postiz publishing setup, and a paid Claude subscription, paths are hardcoded to the author's machine.

The explanation does not state a license for this repository.

Wtf does this do

This repository is a self hosted automation pipeline that runs a faceless YouTube Shorts channel on its own, publishing three videos a day with no person involved in the daily work. It picks a topic, checks whether similar videos have actually performed well before spending any time or computing power on it, writes a script, generates a voiceover, renders a fully animated video, and uploads it to YouTube, all driven by the Claude Code command line tool running unattended on the author's Windows machine with a local GPU. The system is organized into five recurring jobs. One produces and publishes a single Short three times a day, deliberately one at a time rather than in bulk, since the project favors quality over volume. Another studies a top performing competitor video daily and adds what it learns to a growing notes file of techniques that work. A weekly job reads the channel's real YouTube analytics and rewrites the system's own rules for what to try next based on real performance data. A daily digest job emails a summary of what was published and how it performed. A always on local dashboard shows what has run, what is scheduled next, and lets the owner trigger jobs manually. Two ideas shape how it behaves. First, every topic idea has to pass a validation check using real competitor view counts before any video gets made, so weak ideas are rejected on paper. Second, a built in variation system forces every new video to differ from its last six videos across several traits such as title style, format, visual look, and voice, since YouTube can penalize channels that look repetitive. The author is explicit that this is their own running personal project, not a polished product others can install with one click. It contains real file paths, credentials setup instructions, and performance numbers specific to their own machine and channel, and depends on a GPU, Docker, and a paid Claude subscription to run. It is aimed at developers experimenting with autonomous content pipelines who are comfortable adapting a reference system to their own setup, and the README explicitly reminds users to follow YouTube's terms of service around automated content.

Yoink these prompts

Prompt 1
Explain how the virality GATE validation step in this project decides whether to produce a video.
Prompt 2
Walk me through the five autonomous loops in this repo and what each one is responsible for.
Prompt 3
Help me identify which parts of this reference architecture are specific to the author's machine versus reusable.
Prompt 4
Summarize how the weekly ShortsLearn job updates the system's own rules from analytics.

Frequently asked questions

wtf is shorts-factory?

A self-hosted, AI-driven pipeline that autonomously researches, scripts, renders, publishes, and learns from a faceless YouTube Shorts channel.

What language is shorts-factory written in?

Mainly TypeScript. The stack also includes TypeScript, Python, Claude Code.

What license does shorts-factory use?

The explanation does not state a license for this repository.

How hard is shorts-factory to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is shorts-factory for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.