Ludo CLI: every Ludo generator in your terminal#
Ludo now has a command line. ludo puts every Ludo generator in your terminal: sprites and spritesheet animations, images, 3D models with rigging and animation, video, sound effects, music and voices. It's for you, and it's the recommended way to give coding agents like Claude Code access to Ludo.
npm install -g @ludoai/cli
ludo login
Log in with your browser
ludo login shows a short code and opens Ludo in your browser. Check that the code matches, click Authorize, and you're in. No account yet? You can create one on the same page. The CLI gets its own key, listed under API Keys in your account where you can revoke it, and your existing API key and MCP setup keep working. The CLI uses the Ludo API, which is included with the Pro and Studio plans.

Your assets, right in the terminal
Every result is saved to ./ludo-output, and in terminals that can draw images, like iTerm2, Kitty, Ghostty and WezTerm, it shows up right under your command:
ludo image create --image-type sprite --art-style Chibi --prompt "a tiny knight with an oversized helmet and a wooden sword"

Animate it (we renamed ours to knight.webp, or pass --name knight when you create it) and the spritesheet plays in place. Add --engine godot and you also get a Godot 4 SpriteFrames resource, ready for an AnimatedSprite2D:
ludo sprite animate --initial-image ludo-output/knight.webp --motion-prompt "walk cycle" --engine godot
Local files just work
Pass a path to any image, audio, video or model flag and the CLI uploads it for you: no hosting, no base64. That's how one sprite becomes a 3D model, then a rigged one, then gets its own sound effect:
ludo model create --image ludo-output/knight.webp

Made for coding agents
Run ludo skill install and Claude Code learns the CLI, so you can ask for assets in plain words while it builds your game. ludo init adds the same instructions for other agents.
When an agent runs ludo, it gets plain JSON with the saved file paths and no previews, and it looks up only the commands it needs through --help. That uses far fewer tokens than MCP, which loads the schema of every Ludo tool before the first request, and it's why the CLI is the recommended way to give agents access to Ludo. MCP is still there for chat assistants that can't run commands.

And a lot more
- Projects:
ludo initkeeps your engine, output folder and a style image for the whole project, andludo assets redoremakes any file with changes. - Variations and batches:
--n 4gives you four takes to pick from, andludo batchmakes a whole list of assets at once. - Credit control:
--dry-runshows the cost first, and--max-creditsand project budgets keep spending in check. - CI and scripts: set
LUDO_API_KEYor useludo login --with-keyon machines without a browser. - Feedback:
ludo feedbacklets you, or your agent, tell us about a bug, a limitation or a feature you want. - Always current: new Ludo models and features show up in the CLI without an update.
Every command and flag is on the CLI page. Show us what you make from the terminal on Discord!























































































