A motion design studio on your own machine: Claude makes the video step by step, you approve every stage. Bring your own Claude Code or API key.
Windows
Work in progress. Installing works as described below, but a session (the part where Claude makes the video) doesn't run on Windows yet: see What's left. The goal is a working Windows version by October 20, 2026.
Install
In PowerShell (not CMD; you don't need to run it as Administrator):
irm https://raw.githubusercontent.com/GTKottman/mortiflix-oss/main/install.ps1 | iex
It checks for what Mortiflix needs and offers to install what's missing, asking first each time:
| Needs | Why | Installed with |
|---|---|---|
| Windows 10 1809 or newer | what Node 20, Claude Code and winget need | |
| Node.js 20+ | runs Mortiflix | winget install OpenJS.NodeJS.LTS |
| Git for Windows | downloads Mortiflix and the 3D toolkits; its Git Bash runs the sessions' shell commands | winget install Git.Git |
| ffmpeg | renders and checks every video | winget install Gyan.FFmpeg |
| Claude Code (optional) | does the work on your Claude plan; an Anthropic API key works instead | Anthropic's installer, irm https://claude.ai/install.ps1 | iex |
Node and Git may show Windows' "allow this app to make changes" prompt. Then it clones Mortiflix into
%USERPROFILE%\mortiflix-oss (or updates the clone that's there), runs npm install and npm link (which puts
mortiflix in %APPDATA%\npm, already on your PATH), and starts mortiflix init.
Choices, as environment variables (set them before the line above):
$env:MORTIFLIX_DIR = 'D:\mortiflix-oss' # where the code goes
$env:MORTIFLIX_BRANCH = 'main' # which branch to clone
$env:MORTIFLIX_YES = '1' # yes to every question
$env:MORTIFLIX_SKIP_INIT = '1' # stop before mortiflix init
From a clone: powershell -ExecutionPolicy Bypass -File install.ps1 -Dir D:\mortiflix-oss -Yes -SkipInit.
Run it again any time to update. mortiflix doctor shows what's there, with the winget command for anything
missing.
What mortiflix setup does on Windows
- Music: renders in your Chrome, or in Microsoft Edge if there's no Chrome (Edge is Chromium and comes with Windows), so nothing is downloaded.
- Downloads are unpacked with Windows' own
tar.exe(C:\Windows\System32), never the GNU tar from Git for Windows, which readsC:\…as a network address. - npm and npx (
.cmdprograms on Windows) are run throughcmd.exewith each argument quoted, so a studio under a folder with spaces (C:\Users\Ada Lovelace\Mortiflix) works. - uv and browser-harness install to
%USERPROFILE%\.local\bin, as on Linux. - Blender: yours is reused from
C:\Program Files\Blender Foundation; otherwise the official Windows zip is unpacked into the studio. Nova FX doesn't build on Windows yet (the other toolkits install).
Removing it
npm uninstall -g mortiflix
Remove-Item -Recurse -Force "$env:USERPROFILE\mortiflix-oss", "$env:USERPROFILE\Mortiflix\tools"
%USERPROFILE%\Mortiflix is your studio (projects, keys): delete it only if you mean to. Node, Git, ffmpeg and
Claude Code are ordinary programs: remove them in Settings › Apps, or winget uninstall <id>.
What's left
Found by reading the code for Linux-only assumptions. Checked items are done on this branch.
Installing
-
install.ps1: prerequisites with winget, Claude Code, clone/update,npm link,mortiflix init -
src/platform.mjs: finding programs (PATHEXT), running.cmdprograms, Windows' tar, Git Bash, opening files -
mortiflix setup: the repository path (file:///C:/…), tar, npm/npx, Edge, hidden ComfyUI window -
mortiflix doctor: Git Bash, git, and winget hints - Run the installer and every setup part on a real Windows 10 and 11 machine
Running sessions (next)
- The bridge listens on a Unix socket path (
src/bridge.mjs); on Windows it has to be a named pipe (\\.\pipe\mfx-…) - Sessions'
PATHis joined with:(src/backends/claude-code.mjs,src/backends/anthropic-api.mjs); usepathDelimiter() -
bin/mfxis a Node script with a shebang: Git Bash runs it, but Claude Code's PowerShell tool needs anmfx.cmdnext to it - Stopping a session kills its process group (
process.kill(-pid): claude-code backend, the API backend's shell, the render queue); Windows needstaskkill /T /F /PID - The API backend's shell is
bash; on Windows, Git Bash fromfindGitBash() - The video template (Kinetograph) links
node_moduleswith a directory symlink (needs Developer Mode or admin on Windows); use a junction. It also runssleep, which Windows doesn't have -
secrets.jsonrelies on file mode 600, which Windows ignores; the user profile's permissions protect it. Say so in SECURITY.md, or set an ACL - Nova FX's C core: build with MSVC or MinGW (it uses OpenMP and Vulkan)