Four setups. Each one installs itself. Both platforms, same day, same script.
These are working setups, not courses about setups. You paste one link into Claude and it builds the whole thing on your machine: the folders, the rules it works under, the guardrails that stop it doing something you would not have sanctioned, and a crew of agents who know your trade.
Every one of them now runs on Mac and on Windows. The Windows half is native —
no WSL, no Ubuntu, nothing to switch on — and it runs the identical tested script the
Mac does, through Git Bash. If you would rather not involve Claude in its own installation,
every Windows kit has a Run me first (Windows).cmd you can double-click instead.
Multi-Agent Claude Setup
Creative and knowledge work that is not film
The general system: writing, design, research, consulting, a small agency. The same machinery as the film tiers with none of the post-production pipeline.
Claude Code for Filmmakers · The Program
Film and television, the working system
The production pipeline: media ingest with checksums, proxies, editorial automation, paper edits from transcripts, delivery spec checking, archive drills, and a crew of agents who understand post.
Claude Code for Filmmakers · Elite
The full package
Everything The Program has, with the instructor's own working machinery layered on top: his crew charters, his guard hooks, his memory and audit scripts, exactly as they run in his studio. Where the two differ, his version is the one you get.
Claude Agent for Film Financing
Producers raising money
A desk that raises with you. It writes a hundred personal emails a day in your voice, follows every one of them up, keeps the tracker honest, plans what you spend on the raise and on festivals, and prepares you for every investor meeting. It sends nothing until you have read the batch and said send.
This one is password-gated. The install link carries the key when you have been given it; the downloads do not open without it.
Paste the install link into Claude and press return. That is the whole thing. You do not download anything by hand, you do not unzip anything, and you never open a terminal. Claude fetches the tested installer from the same site, runs it, checks its own work, and then interviews you so the result is yours rather than generic.
The one Windows thing that fools everybody. A window that was already open cannot see a
program installed after it opened. So claude works in the window that installed it and
says 'claude' is not recognized in the next one. That is not a failed install. Close the
window, open a new one. The Windows installers write the permanent PATH themselves and then prove
it from a brand-new process, so if you see that check pass, believe it.
Every kit installs from its tool's own vendor, asks for no admin password, deletes nothing, and prints what landed and what did not. What each one is allowed to touch is written out on its own site, in English, before you run it.