ShellX Motion v0.1.0

ShellX Motion is a local-first motion graphics and video rendering engine built to be
driven by an AI agent rather than a mouse. It runs entirely on your own machine — no
service, no account, no upload.

This is the first public release. It ships as source: clone the tree, build it, run
it. There is no prebuilt binary.

What it does

Agent-native. 169 typed Debug API commands and 155 discoverable actions, reachable
over MCP, HTTP, WebSocket, or the CLI. Ask it "change snow intensity and preview it"
and it answers with a callable plan instead of expecting you to find a menu.

Your files stay yours. The server binds loopback only and authenticates with a
per-user key. Remote publishing is not enabled.

Declarative layers cannot run code — web layers can, deliberately. Shapes, text,
keyframes, environments, shaders, particles and fixed 3D scenes are pure data and cannot
execute anything, implicitly fetch remote assets, or raise host resource limits. A
web/html/canvas layer renders package-local HTML in Chromium with JavaScript
enabled — fenced (network denied by default, reads confined to the package), but
genuinely executing. Treat a package from an untrusted source the way you would treat
any downloaded script; security-model.md states the
full boundary.

Permission tiers that bind. Six of them, read_motion up to push_remote. The host
sets a ceiling at launch; a caller can ask for less, never more.

Receipts, not claims. Every operation writes a receipt with input hashes, artifacts
and outcome. When an agent says it rendered something, the receipt is how you check.

Two render lanes, a deterministic browser lane and a fixture-proven fallback, with a
capability probe that tells you what your machine can do before you ask it to. H.264 and
HEVC MP4, VP9 and AV1 WebM where your FFmpeg supports them, plus audio, captions, alpha,
GIF and stills.

Also included: a full authoring surface (masks, mattes, effects, gradients, spatial paths,
easing curves, keying, roto, tracking, compositing graphs, precomposition), 12 template
families held to a published quality bar, bounded HTML/OTIO/glTF/Lottie interchange, and a
local Workbench built on the same contracts the agents use.

Getting started

pnpm install
pnpm build
pnpm start

pnpm start creates a per-user access key, starts Motion, and opens the Workbench. The
Connections page has one-click setup for supported agent CLIs and the MCP command for
anything else.

Requires Node.js 24 and pnpm 10.6+. FFmpeg and FFprobe are needed for video render and
readback — run doctor and it will tell you exactly which operations your machine can
perform.

Honest limits

docs/public/FEATURES.md documents what exists and what does not, deliberately. The
short version: hosted execution, cloud collaboration and remote push are out of scope;
render status views are derived from receipts on disk rather than live processes; and
browser-lane renders are bounded by a per-job memory ceiling that grows with frame count.

Verifying what you got

docs/public/BINARY_ASSETS.md lists every binary file in this repository with its
SHA-256, where it came from, and how to confirm that yourself — redownload the upstream
font package and compare digests, or regenerate the template posters with
pnpm run template-pack:proof.

Full detail in FEATURES.md. MIT licensed.