Download Brutalist with Claude Code | Setup Guide
Liam demonstrates cloning the Brutalist toolkit from GitHub inside Claude Code, running its free setup doctor, and reading the readiness table before trying any feature.
Liam, standing in for Bear, walks through what actually happens when you download Brutalist, the free video-production toolkit, using Claude Code. The point of the video is to correct a common assumption: there is no installer, no DMG, no license click-through. Brutalist is a git clone plus a free setup doctor script, and the whole toolkit ends up as plain files in a folder you already control.
What the clone actually puts on disk
Pasting the setup prompt into Claude Code clones the public toolkit repository from github.com/nikbearbrown/brutalist.art into an empty folder, runs the free installer, and reports back which features are ready. Nothing happens outside the composer. The clone drops a setup shell script, an art shell script, a skills folder containing the builder recipes, a runtime folder with the Kokoro voice engine, the Remotion project, and the Python scripts that do the work, plus a docs folder and a README. There is no hidden state and no global install: everything the toolkit needs lives inside that one folder.
Running the doctor
Once the folder exists, running /setup --install once pulls the free dependencies. Running plain /setup after that, as many times as needed, prints a readiness table. Green rows mean a feature is live; red rows mean a dependency is missing, and the doctor names the exact install command to fix it. Liam notes that this is the same script the sandbox in the video itself just ran, so the readiness table on screen reflects a real run, not a mockup.
Claude Code subscription versus an Anthropic API key
A point fellows commonly get wrong is treating the Claude Code subscription and a paid Anthropic API key as the same thing. They are separate lanes. The Claude Code subscription is what lets the agent think and write inside the editor. A paid API key is optional and metered, and it is only needed if you are scripting Claude outside the desktop app. Brutalist itself, run through Claude Code, does not spend anything.
What actually costs money, and what doesn't
Kokoro, the local voice model, runs on your machine. Remotion renders on your machine. Manim runs on your machine. All three are free by default, which is the intended shape of the tool. The one network request the setup makes is downloading the Kokoro voice model itself, about 340 megabytes, straight from a GitHub release, the first time you run /setup --install. Setup does not sign you into any account, does not create accounts, does not touch any file outside the folder you cloned into, and does not upload anything.
The three-line verdict
Liam summarizes the whole process in three steps: clone the repository and you have the toolkit, run the doctor and you know exactly what is ready, and stay in the free lane and the pipeline never asks for a card. The video frames this as the boundary between installation, which Claude Code and the doctor script handle for you, and creative judgment, which stays with the fellow using the toolkit.
Key takeaways
- Brutalist installs as a git clone plus a free setup doctor script, not a traditional installer.
- Run
/setup --installonce, then plain/setupto view the green-or-red readiness table. - The Claude Code subscription and a paid Anthropic API key are separate, unrelated things; Brutalist needs only the former.
- The only network download is the roughly 340 MB Kokoro voice model, fetched once from a GitHub release.
- Setup never creates accounts, uploads files, or touches anything outside the cloned folder.
Who this is for
This video is for Humanitarians AI fellows who have Claude Code but have not yet set up Brutalist, and who want to know exactly what the setup script does, what it costs, and what it touches before running it.
Full transcript(auto-generated, with timestamps)
[0:00]Ciao, this is Liam in for Bear. You already have Claude code, so downloading Brutalist is one paste into the composer. Not a wizard, not a package, a Git clone, a free doctor script, and a readiness table. Here is what actually happens. Most fellows here download and picture an installer, a DMG, a click through a license. That is not what this is. Brutalist is a Git clone plus a free doctor script. The clone is your source tree. The doctor tells you exactly which pieces are ready. That is the whole idea, and it is worth caring about because everything you do next is just editing files in that folder.
[0:31]Here is the paste ready request. Open Claude code in an empty folder. Paste this. It clones the public toolkit repo from github.com/nickbearbrown/brutalist.art into your folder, runs the free installer for you, and reports back which features are ready. You never leave the composer. This is what the clone actually drops onto your disk, a shell script called setup, a shell script called art, a skills folder with the 15 builder recipes, a runtime folder with the Kakoro voice, the Remotion project, and the Python scripts that do the work, a docs folder, a readme. That is your toolkit. No hidden state, no global install, nothing outside this folder. Now run the doctor. /setup --install
[1:11]Once to pull the free dependencies. Then plain /setup over and over to see the readiness table. Green means the feature is live. Red means one dependency is missing, and the doctor tells you exactly which install command to run. It is the same script the sandbox in this reel just executed. The readings on screen are real. This part trips fellows up, so read it slowly. Your Claude code subscription is what lets the agent think and write. That is one lane. A paid Anthropic API key is a different lane, optional metered, only needed if you script Claude outside the desktop app. Brutalist itself doesn't spend a cent.
[1:42]Kakoro is a local voice model. Remotion renders on your machine. Manem runs on your machine. Free by default. That is the shape of this tool. Now the honest limits. Setup does not sign you into anything. No accounts are created. Setup does not touch any file outside the folder you cloned into. Setup does not upload. It does download one thing from the public internet the first time you run install, the Kakuro voice model, about 340 megabytes straight from a GitHub release. That is the whole network footprint. Verdict in three lines, clone the repo, you have the toolkit. Run the doctor, you know exactly what is ready. Keep the free
[2:15]Lane, the pipeline itself never asks for a card. That is how you download Brutalist. Your turn, open Claude code in an empty folder and paste this prompt. It clones the toolkit, runs the free installer, reads back the readiness table, and asks you which feature you want to try first. When Claude hands back the table, look at it. Red rows are the doctor telling you which install command to run next. That is the loop. Now you have Brutalist on disk. That was download Brutalist with Claude code, lay them in for bear, for humanitarian's AI.
More from Brutalist (Film as Code)
2:28Your First Brutalist Project | Build a One-Minute Film
3:07The ai-explainer Skill | How Brutalist Builds Explainers
3:49The anthropics Skill | Claude’s Official Skill Library
3:15The cli-explainer Skill | Claude Code on Screen
3:30Automating the YouTube Review Pipeline | Vikhyat
3:34