Remotion Agent Composer

agent Remotion render contract

Render Contracts for Agent-Composed Remotion Projects

Save agent-generated Remotion descriptors remotely, then render locally with short-lived render contracts and hosted Composition bundles.

Audience
Developers building code-agent video workflows with Remotion
Product
Remotion fragments, MCP schemas, render descriptors

Separate composition from rendering

The product stores a render descriptor and issues a short-lived render contract. The Composition receives only an opaque render token, fetches the descriptor, and lets the user's local renderer produce the final video.

No long-lived MCP tokens in downloadable code

The hosted Composition bundle is public JavaScript, so it should never receive API tokens. Render contracts keep access narrow, scoped, expiring, and revocable.

Best fit

Use this architecture when a code agent composes a Remotion project but the customer controls the actual render environment.

Compose with schema-safe video fragments

Browse the catalog, create a project, save a descriptor, and render locally with a short-lived contract.

Open the workbench

Related articles

How a Remotion Fragment Library Helps Code Agents Compose VideosA practical architecture for giving code agents reusable Remotion fragments, schema constraints, and predictable render descriptors.Local Remotion Rendering with Short-Lived Render ContractsHow to let users render locally while a hosted Composition bundle safely fetches the saved descriptor at render time.SEO Pages for Developer Video Tools: What to Publish FirstA simple publishing plan for a developer video tool: use-case pages, comparison articles, integration guides, and schema-driven tutorials.