Install the Editframe local runtime that matches this CLI version. Run it once per computer, before local commands such as render and open.
npx editframe setupThe runtime ships for macOS (Apple silicon or Intel) and for Linux x86-64. setup downloads the signed release, verifies its signature and checksums before running anything, and activates it in the user cache directory: ~/Library/Caches/editframe/components on macOS, and $XDG_CACHE_HOME/editframe/components or ~/.cache/editframe/components on Linux. No account is needed.
Local commands then use that runtime without flags. To install into another directory, pass --component /absolute/directory or set EDITFRAME_COMPONENT_ROOT, and select the same directory the same way in later commands. Progress goes to stderr; when it finishes, setup prints JSON with the installed version, runtime version, component root and release directory.
Flags
The table includes shared parser options; use the command-specific flags shown above.
| Flag | Default | Description |
|---|---|---|
-h, --help | — | Show usage |
--version | — | Show the CLI version |
--project <value> | — | Absolute local project directory |
--bridge <value> | — | Installed bridge executable |
--component <value> | — | Installed signed component directory |
--registry <value> | — | Local bridge registry directory |
--editor <value> | — | Verified editor asset directory |
--editor-version <value> | — | Verified editor version |
--compiler-pack <value> | — | Verified compiler pack file |
--compiler-pack-sha256 <value> | — | Expected compiler pack SHA-256 |
--endpoint <value> | — | Hosted runtime API endpoint |
--project-id <value> | — | Hosted project identifier |
--composition <value> | — | Composition identifier |
--input <value> | — | JSON request file with an explicit operation identity and revision |
--job <value> | — | Job identifier |
-o, --output <value> | — | MP4 file that render writes (default output.mp4) |