Objective Evaluation
ExodeUI CLI vs Rive CLI
ExodeUI CLI vs Rive CLI compared: file formats, live and device previews, headless input, interaction tests, video rendering, editor sync, AI agent setup and pricing.
Updated November 2026
The fundamental architectural difference
Both are command lines that let you, or an AI agent, build an interactive file from text and check it without opening an editor. The Rive CLI (a free technical preview since September 2026) builds .riv files from Rive Markup Language, previews on Android and iOS devices and syncs with the Rive editor through push and pull. The ExodeUI CLI builds .exode files from a JavaScript kit or JSON and adds plain-text interaction tests, a design review, video rendering, a verified .bexode build and Rive and Lottie import. Choose by the editor and runtime you already use.
Side-by-side comparison
Feature & Capability Breakdown
| Dimension | ExodeUI CLI | Rive CLI | Advantage |
|---|---|---|---|
| Install | npm i -g @exodeui/cli (Node 18.17+, Chrome) | Install script or Homebrew cask (brew upgrade --cask rive-cli) | Tie |
| Source format | scene.js (a JavaScript kit) or open .exode JSON | Rive Markup Language (scene.rml) with rive.yaml | Tie |
| Output | .bexode for every ExodeUI runtime, verified against the source; offline HTML page | .riv file that opens in the Rive editor | Tie |
| Live preview | Browser preview with input controls, live states and a test recorder | Native preview window with FPS, memory and build status | Tie |
| Device preview | Not yet (browser only) | rive . --android and --ios install the player on a connected device | Rive CLI |
| Headless input | click, hover, drag, wheel, key, set and fire, by point or layer name | --pointer, --touch, --key, --gamepad, --semantic-action, --advance and --data, with --screenshot | Tie |
| Interaction tests | Plain-text .test files with expectations for states, inputs, pixels and errors | Scripted input runs with screenshots | Tie |
| Checks | exode check: compile, validate, design review, run on the engine | rive inspect: structure problems, unfired events, object counts | Tie |
| Video rendering | MP4, WebM, GIF, MOV with alpha, PNG sequences, with audio | Screenshots; no video export in its announcements | ExodeUI CLI |
| Editor sync | exode open launches the ExodeUI editor; no push and pull yet | rive push and rive pull, including new files and library versions | Rive CLI |
| Import other formats | Converts .riv and Lottie JSON to native, editable objects | Rive files only | ExodeUI CLI |
| Libraries and scripting | Effect scripts in JavaScript inside the file | Libraries (publishing needs a paid plan) and AnimaScript with threads and GPU scripts | Rive CLI |
| AI agents | AGENTS.md, CLAUDE.md and .mcp.json (160+ MCP tools); --json on every command | rive create writes CLAUDE.md and AGENTS.md; rive docs for agents | Tie |
| Price | 30-day free trial, then ExodeUI Professional ($5/month billed yearly) | Free technical preview; some features need a paid Rive plan | Rive CLI |
When to choose Rive CLI
- Your team already designs in Rive and ships .riv files.
- You need to preview on real Android and iOS devices while you work.
- You want changes from the terminal to flow back into the Rive editor with push and pull.
- You are writing heavy scripted content and want AnimaScript's threads and GPU scripts.
When to choose ExodeUI CLI
- You want interaction tests in plain text that fail CI when a hover or a state breaks.
- You need marketing video, GIFs or transparent MOVs rendered from the same file.
- You are moving Rive or Lottie files to an open JSON format that a designer can still edit.
- Your agent works over MCP and you want it to build, check and test in one project.
Direct Answers
Frequently Asked Questions
Related
Build living software components today.
Design it once and ship the same file to web and mobile — no handoff, no rebuild.