Your agent writes the film. Codeflix renders it.
One command your coding agent runs to turn a Blender project into a video link. The frames go to as many GPUs as the film can use, all at once, and come back as an MP4.
8 min 39 s240 frames of 4K Cycles at 192 samples, from command to video link
3 commandspreview, quote, render: your agent does this instead of running a render farm
Pay per secondonly for the time GPUs spend rendering your frames, with a hard spending cap
How it works
- Set up once. One command installs the
codeflixtool, saves your API key and teaches Claude Code (or Codex) how to use it. - Ask your agent for a film. It builds the Blender scene on your machine, then runs
codeflix previewand shows you one frame from every shot. - Approve the price.
codeflix quoterenders three real frames and tells you the cost and time for the whole film. - Get the video.
codeflix renderspreads the frames across GPUs, retries anything that fails, encodes the MP4 and hands back a link.
codeflix preview ./my-film # free: one frame per shot, as one image
codeflix quote ./my-film # free: price and time from 3 real frames
codeflix render ./my-film --max-spend 10
Built for agents
- Every command prints at most a dozen lines and waits until it has an answer, so your agent spends its tokens on the film, not on watching machines.
- Problems are caught before any GPU starts: missing textures, absolute paths, unbaked simulations, the wrong engine. Each comes with the exact fix.
- Every render has a spending cap and stops before it, not after it.
- Exit codes your agent can act on, and
--jsonon every command.
Get access
Codeflix is invite-only while we test it with people making films with coding agents. If you have an invite link, open it to get your API key and free credit. Otherwise, contact us at support@codeflix.run.