Get the base
The goal of this step is to get scene-studio onto your computer. The video tools (ffmpeg, codex, yt-dlp) were already installed in prerequisites, so here you only get the base. Usually done within 10 minutes.
1) Get the base
Section titled “1) Get the base”If you have a license and Template access, use “Use this template” to make your own repository, then clone it. Otherwise, get it directly with git clone.
cd ~/projectsgit clone https://github.com/ddakit/scene-studio.git my-channelcd my-channelIf the ~/projects folder doesn’t exist, run mkdir -p ~/projects first. You can rename my-channel to whatever you like.
Normal screen: a line starting with “Cloning into ‘my-channel’…” shows, and after a moment the prompt returns.
Stuck screen:
- “command not found: git” → git isn’t installed. Go back to prerequisites.
- An auth request → if it’s a private repository, you need to be logged into GitHub. Using your own repository URL made via Template is cleaner.
2) Step into the folder you got
Section titled “2) Step into the folder you got”cd my-channellsIf you see names like AI_AUTOMATION.md, CLAUDE.md, and .claude/, you got it right.
3) Dependencies to install
Section titled “3) Dependencies to install”The video tools are system tools, already installed in prerequisites. The base itself has no extra packages to install. Video, images, and the cache pile up under _workspace/ as you work, and they’re in .gitignore and drop out of git tracking.
4) first-run handles git history separation
Section titled “4) first-run handles git history separation”When you get the base with git clone, the base’s commit history comes along. It’s cleaner to cut the history before your own work commits pile on top, but that spot is something the next step’s /start detects automatically and asks about once. No need to do it by hand now.
Once you’ve got it, go to first-run. You verify the environment and pick a track with /start.