Reverse engineering for any video
Install · Agents · Use cases & remakes · Why OpenMotion · Setup & architecture · Community
OpenMotion is the first full-stack agentic video generator. Upload a reference video or paste a social video link to recreate it with your own brand kit and copy.
- 🎬 Full-stack video recreation. Code video with HTML. Your agent breaks down the reference, rebuilds its shots and transitions, and generates missing assets. Edit the timing in Studio and render an MP4 from the same project.
- 🔑 BYOA — Bring Your Own Agent. BYOK — Bring Your Own Keys. OpenMotion is free and open source. Recreate videos in your local agent and use your own API keys at every layer.
- 🧩 OpenMotion introduces Motion.md, a Markdown format for shot order, timing and transitions. Use it to share how a brand film works, shot by shot.
- 🎛️ Images, video, music and voice. Generate artwork with Nano Banana 2, add a shot with Seedance 2.0, score it with Suno v4 and narrate it with Kokoro. Explore all seven built-in models.
One-click installation. No manual configuration required. Once installed, create motion videos from scratch, recreate reference videos, or start from a template—all in your conversation.
Install OpenMotion in ChatGPT →
Copy this instruction into your local agent to set up OpenMotion from source:
Read https://github.com/nexu-io/openmotion/blob/main/install.md and follow the instructions to install and connect OpenMotion in the current agent.
After setup, the agent opens the local template library and suggests a template. Confirm the choice before creating a project. Source installation guide
Use Git, npm and Node.js 26.11.1:
git clone --depth 1 https://github.com/nexu-io/openmotion.git
cd openmotion
npm ci
npm run build:studio
npm startOpen the actual studioUrl or previewUrl printed at startup, then choose Template library. Studio and MCP read the templates in this checkout. To connect your agent to this same copy, follow source setup and MCP configuration. Clone size and optional media
This installs the published npm application and uses its configured online catalog. To use or contribute repository templates, use the local source setup above.
Copy this instruction into your local agent:
Read https://github.com/nexu-io/openmotion/blob/main/docs/install.md and follow the instructions to install and connect OpenMotion in the current agent.
After installation, the agent offers a template to try. Confirm the choice before creating a project. Installation and first-run guide
22 local agents · Choose your agent
Explore product demos, brand films, talking-head videos and more. The previews below show reference videos.
Browse the full template library → — Find more templates, full videos, Motion.md and recreation instructions.
 OpenAI · Build a story from multiple scenes Connect different scenes around one narrative idea, then expand into a broader montage. View template |
 Anthropic · Recut a making-of collage Layer clips and screenshots in sequence, keeping the main title readable above them. View template |
 Notion · Show a problem, then the solution Move from crowded tasks to coordinated agents; adapt the sequence to your own product. View template |
 OpenAI · Turn demand into a product reveal Build momentum with overlapping requests, then reveal the app in one clear beat. View template |
 Kimi · Connect worlds through motion Use code strips, offset slices and transitions to connect a series of brand scenes. View template |
 Slack · Rebuild a brand mark Break a mark into simple shapes and reassemble it with your own colors and name. View template |
 Anthropic · Explain a connected workflow Follow one question through data, actions and slides, keeping the context visible. View template |
 Stripe · Show an approval step by step Carry the same request from a conversation to phone confirmation with clear visual continuity. View template |
 OpenAI · Turn complex ideas into diagrams Transform one geometric diagram into the next using shared points and connecting lines. View template |
 Anthropic · Make results progressively visible Move from an overview to individual findings, then show the action taken for each result. View template |
 ElevenLabs · Visualize a song taking shape Connect the prompt, sections and tempo to a waveform and the finished piece. View template |
 Deezer · Animate a music poster Keep the headline steady while flowing waves add rhythm around it. View template |
Build a clear story around a speaker, with readable captions, screen inserts and animated keywords. Use these references to find a style for your own recording.
| 🎓 Teach & explain | ||
|---|---|---|
 6 essential skills to transform your career Numbered points + kinetic keywords Reference · @careerwithriya |
 What's the best AI tool right now? Presenter + floating tool cards Reference · Dan Martell |
 10 Days of AI Basics, Day 1 A personal lesson + readable captions Reference · @harpercarrollai |
| 🖥️ Show the workflow | ||
 5 tools I use every day Desk-side story + workflow inserts Reference · Ali Abdaal |
 Tool demo with callouts Presenter + screens + callouts Reference · @john.tagudin |
 Top 5 plugins to install in Claude A spoken list + supporting screenshots Reference · @aiwithsachi |
| 🎬 Tell a story, show a product | ||
 The Founder Experiments, Ep. 1 Founder diary + everyday B-roll Reference · @khris.sheer |
 AI creator with product Product story + proof + picture-in-picture Reference · @ugc.rachelll |
 Stop Paying for 5 AI Tools Product tutorial + live demonstration Reference · Kevin Stratvert |
Code video with HTML. OpenMotion uses HTML, CSS and JavaScript to describe scenes, typography, layout, transitions and timing. Recorded footage, generated clips, images, music and voice-over become media inside the composition. The same project opens in Studio and renders to MP4.
Write it. Watch it. Change it. Render it. Ask your agent to replace the product, tighten the hook, add a presenter, change the captions or try another ending. It edits the project source; you review the result in the visual editor. Local MCP clients use the project tools, while agents with shell access can follow the Skills and pinned CLI workflow. Agent setup · Native composition guide · Example HTML project
If historical media are unavailable, an Agent restore is refused before changing the project. The editor shows a dismissible error with the affected file paths and confirms that the current project is unchanged.
Review your video, arrange clips and export from the same Studio workspace.
| In the Studio | What you can do today |
|---|---|
| Story and timeline | Import and arrange media; have the agent trim, reorder and revise against a script or confirmed timecodes |
| Motion and captions | Author animated type, transitions, callouts, charts and captions around your content |
| Media and sound | Import your material and generate images, video, music and TTS voice-over through the built-in model integrations |
| Image revision | Generate candidates with a reference-capable image model and adopt a replacement while preserving timing and animation |
| Preview and versions | Review in Studio, edit by hand or with your agent, and return to the project for the next revision |
| Export and source | Render a fixed version to MP4 and retain the HTML, CSS, JavaScript and media |
“Keep the reveal we approved. Replace the middle scene with this screen recording, tighten the opening using these timecodes, and hold our final CTA for two more seconds.”
- Break down the reference. Pick a sequence. Record its shot order, transitions and sound cues in Motion.md, and mark what you want to replace.
- Rebuild the shots. Your agent rebuilds the HTML scenes using your brand kit, copy and visuals, then arranges them on an editable timeline in Studio.
- Compare the cuts. Watch the same moment in the original and the remake. Adjust the timing, movement and sound, then play the sequence through.
- Export and share. Render the MP4 and keep the HTML source and media. To share a project others can adapt, include its Motion.md, a preview and assets you can redistribute. Project contribution checklist
Choose your agent. WorkBuddy, Codex, Claude Code and DeepSeek Harness have installation instructions. Other buttons open the shared MCP and CLI setup.
| Bring your own… | Make it work for your video |
|---|---|
| 🤖 Agent — BYOA | Connect your existing local agent through Skills and MCP, with CLI access where supported. Keep your preferred client, account and working context. |
| 🔑 Keys — BYOK | Connect supported media-provider API keys in Model Settings. Choose models for images, video, music and TTS; supported local media integrations can use your existing agent login. |
| 🎨 Brand and material | Add your logo, fonts, screenshots, camera footage, script and music. Keep identity and approved assets in the Brand Kit section of Motion.md. |
| 🧩 Starting resources | Browse references, motion components, templates and community Skills. Pick a direction, give the source or reference to your agent, and make it yours. |
The OpenMotion creation pipeline is open source: Skills, project tools, model integrations, Studio and rendering. Run it locally, inspect the implementation and extend the parts you need. OpenMotion charges no software subscription or per-render fee for this local workflow. You can also work with your own footage, images and audio without invoking media-generation APIs.
Provider credentials stay in your workspace, separate from the video project. Your agent and media providers bill any subscriptions or usage to your own accounts. Agent setup and compatibility
OpenMotion introduces Motion.md: a Markdown format for shot order, timing, transitions and the assets you can replace. The online library brings reference videos and their motion guides into the same detail page.
The Brand Kit section records your identity, voice and approved product facts; the Design section can reference an independent DESIGN.md for visual rules. Keep the reference’s motion and pacing while making the result recognizably yours.
To share an industry or brand system, use the Motion Package v0.2 draft and authoring toolkit. A package combines the design and motion documents with materials, declared dependencies and optional SKILL.md. The included recipe demonstrates two content presets; automatic Studio import and rendered fidelity remain separate from package validation.
Browse by reference brand, use case and video type, or search for a specific idea. A template detail page brings together the preview, visual style, production notes and Motion.md download. Choose Recreate template in Studio to copy a prompt for your agent.
Reference-only entries start a reconstruction workflow. When editable source is available, your agent can adapt the project directly.
BYOK makes your multimodal accounts part of the video workflow. Add your supported provider keys in Model Settings, choose your models, and generate images, video, music and speech through the Studio's Model Gateway. Preview candidates and adopt the results into the same project your agent and Studio edit. The supported local image path can reuse your existing agent login.
| Make what the video needs | Built-in model catalog examples | Bring it into your film |
|---|---|---|
| 🖼️ Images | Codex Image; Nano Banana 2 via Atlas Cloud; FLUX Schnell via fal.ai | Brand visuals, scene artwork and supporting images; reference-based editing through the supported Codex image path |
| 🎬 Video | Seedance 2.0 via Atlas Cloud; Wan 2.2 via fal.ai | Generated shots and B-roll to combine with your footage and motion |
| 🎵 Music | Suno v4 via Atlas Cloud | A soundtrack built around your mood and creative brief |
| 🎙️ TTS / voice-over | Kokoro via fal.ai | Narration from your approved script, placed alongside the visuals and music |
“Use the Brand Kit section of our Motion.md and our approved script. Generate artwork for the opening, a video insert, background music and TTS narration. Add the selected results to the recreated project, align the sound and visuals, then show me the full cut.”
Model catalog · Provider setup and endpoints
When choosing or replacing media, creation workflows share a material sourcing policy: reuse suitable supplied assets, prefer original sources for established subjects, and create original/supporting visuals as needed. Explicit user constraints and each workflow’s supported scope still apply.
For agent-led installation, use the installation instruction above. To run from source, follow the steps below.
After a successful Agent-led installation, open the editor's template library in the current conversation, without creating a project. Browse and preview first; choose Open and edit to create an independent editable copy. Setup provides a direct library link even before the chat reloads MCP. See the installation reply rules.
During video creation and editing, the chat stays free of preview areas. OpenMotion presents the editable Studio when the final video is ready to preview, then shows the final video in chat after its MP4 export completes and passes verification. Native-host acceptance of an installed build remains separate.
If MCP tools are missing or fail to connect, use the installed connection diagnosis and recovery guide to inspect the actual host configuration and verify the original workspace before continuing.
Use Git, npm and Node.js 26.11.1. Source-based preview and export also need Chrome/Chromium and FFmpeg/FFprobe. Runtime setup
git clone --depth 1 https://github.com/nexu-io/openmotion.git
cd openmotion
npm ci
npm run build:studio
npm startFull reference videos and optional template archives download through Git LFS only when requested. README images/GIFs and built-in templates remain available directly. See clone size and optional media downloads.
Open the studioUrl or previewUrl printed by npm start, then open Template library. Startup reuses a compatible service for the same workspace or selects an available local port. The service keeps running in the background after the launcher exits.
Select a template and choose Recreate template to copy the instruction for your agent. Keep projects and credentials outside the checkout; MOTION_DATA_DIR selects the workspace.
Source checkouts load templates from library/templates/catalog/. The local Studio and MCP use the same files; openmotion_list_templates returns a searchable local index, and openmotion_get_template returns local guide content and absolute source paths. Imported large images and videos retain existing CMS links; new contribution media can use Git LFS. Local edits appear on the next catalog read.
The plugin root is this checkout: .codex-plugin/plugin.json loads its skills/ and .mcp.json, which launches the root mcp.ts. Start stdio with npm run mcp or use an absolute path in manual MCP configuration. Local template workflow.
For Codex with plugin support, run from the checkout:
bash scripts/install-motion.commandWorkBuddy · Import the OpenMotion connector in WorkBuddy or add its mcp.json as a custom MCP server. Ask WorkBuddy to list the available video templates. WorkBuddy setup
Claude Code · Select --host claude in the local installer, then run /mcp in Claude Code to check the connection. Local installation guide
DeepSeek · Work with the editable HTML project from the terminal in DeepSeek TUI. For DeepSeek Harness, connect the OpenMotion MCP tools with the Cordis configuration. DeepSeek Harness setup
The installer uses locally built packages. Windows test packages
Try an online template:
Use OpenMotion to recreate the template at this detail-page URL with my brand kit and copy. Keep the motion and pacing, then open the editable result in Studio for review.
To start from a video instead, supply your reference and use the recreation brief. If your host cannot open Studio beside the conversation, use the returned local project link.
The plugin and MCP server are named openmotion; Tools, Skills and resources use openmotion_*, openmotion-* and openmotion://. Old Tool/resource names remain compatibility aliases; retired Skill entries are removed. Use openmotion-* Skill names and refresh host discovery after upgrading. See naming and installation compatibility.
From the checkout, discover and install the five core workflows with the Skills CLI:
npx skills add ./skills --list
npx skills add ./skills --skill openmotion-director openmotion-production openmotion-template-to-video openmotion-recreate openmotion-video-to-templateThis copies instructions; it does not install the runtime or register MCP. Keep the shared documentation available and connect the app separately, or use the integrated local installer above.
| Skill | Use it for |
|---|---|
| openmotion-recreate | Reconstructing a reference video and comparing the result |
| openmotion-template-to-video | Adapting an existing editable template |
| openmotion-director | Original films, narrative, movement, sound and creative review |
| openmotion-video-to-template | Producing a portable reusable template |
| openmotion-production | Scoped edits, preview, checks, troubleshooting and export |
Connect a local agent · Follow the installation guide for your client. Use the configuration below in clients with local stdio MCP support. In a shell-based agent, open the project directory and use the local engine CLI to preview and render the HTML scenes.
{
"mcpServers": {
"openmotion": {
"command": "/absolute/path/to/node",
"args": ["--experimental-strip-types", "/absolute/openmotion/mcp.ts"],
"env": { "MOTION_DATA_DIR": "/absolute/openmotion-data" }
}
}
}The thirteen public MCP tools cover template discovery and details, project creation and reading, editing, preview, media import and BYOK generation, reusable asset versions, export, version restoration and cancellation. Shared workflow and engine guides are available through MCP resources. Tool contract
Find a template with openmotion_list_templates, inspect it with openmotion_get_template, then create an editable copy with openmotion_create_project. Template catalog
Use npm start for the app and npm run mcp for stdio. Shell-capable agents can inspect and render with the pinned engine CLI returned by the runtime; managed edits retain project revision checks. Native authoring
| Study the reference | Rebuild for your story |
|---|---|
| Hook and narrative — what appears first, what follows, what earns the reveal | Your promise, product facts and call to action |
| Shot structure — framing, camera movement, layers and visual hierarchy | Your UI, footage, logo and supporting images |
| Motion and pacing — entrances, transitions, easing and reading holds | The same motion intent, adjusted to your content |
| Typography and identity — type hierarchy, color and composition | Your fonts, palette and words, recorded in Motion.md’s Brand Kit section |
| Sound and rhythm — speech timing, music cues and emphasis | Your voice, supplied music and sound direction |
Supply the clip and timecodes if your agent cannot open the social link. Start from the reference with the recreation workflow, or use the template workflow when you already have editable source.
Use OpenMotion to reverse-engineer the attached reference for our brand.
Study: the opening hook, shot order, typography, transitions and sound cues.
Keep: the product reveal and camera rhythm in the selected segment.
Replace: the logo, UI, claims, copy and end card with our supplied materials.
Generate: missing images, video, background music and TTS narration using
our configured models, following our brand and approved script.
Build an editable project. Open it in Studio and compare matching moments
with the reference. Explain any remaining differences. After review,
export an MP4 and retain the source for the next edit.
Open a template to watch the reference and read its visual style and production notes. Download Motion.md when you want the guide as a reusable file.
Choose Recreate template, copy the instruction and add your brand kit, copy and creative requirements. Your agent installs or connects OpenMotion if needed, then works from the selected template. Open the resulting project in Studio to review the timing, continue editing and export.
Editing the timeline in Studio and asking your agent to change a shot both update the same HTML project. The local TypeScript service manages media and revisions. A browser-based rendering engine exports the selected version to MP4.
Edits made through the project tools include a revision check so an outdated request cannot overwrite newer work. Generated media enters the project when you select it. Each export uses the version saved when the job starts. The exporter checks the file specifications, and you can play the cut to review the picture, sound and timing.
Read the full architecture and roadmap as text
CREATIVE INPUT
Reference video + brand kit + script + media
|
v
COMMUNITY KNOWLEDGE
Motion.md + BRANDKIT.md + Skills + templates + components
|
+-------------+------------------+
v v
BYOA: YOUR LOCAL AGENT OPENMOTION STUDIO
DeepSeek Harness / Codex / React 19 + TypeScript + Vite
Claude Code / other local hosts Tailwind CSS + Zustand
Skills + host analysis tools CodeMirror + Dockview
| media / preview / timeline
| stdio MCP | local HTTP
| 9 public project tools |
+------------------+-------------+
v
LOCAL APPLICATION Node.js + TypeScript + node:http
Sessions / project files / assets / revisions / export jobs
| |
v v
BYOK: MODEL GATEWAY VIDEO AS CODE
Your keys / accounts / model routing HTML scenes + media + Studio data
Discovery / generation jobs HTML + CSS + JavaScript + GSAP
| ^
v |
MODEL ADAPTERS |
Codex Image / Atlas Cloud / fal.ai |
Images / Video / Music / TTS |
| |
v |
Generated candidates -> preview / select -> adopt into the project
|
v
RENDER AND VERIFY
Selected project version -> HTML render engine + Chromium -> FFmpeg / FFprobe
|
v
DELIVERY TODAY
MP4 + editable source + media + version and export evidence
|
.----------------------'
v
COMING: PUBLISH TO EVERY PLATFORM
Platform connectors -> release review -> scheduling -> performance feedback
|
v
COMING: KNOWLEDGE FEEDBACK
Version-linked outcomes -> team memory / RAG -> evaluated Skill improvements
BYOA connects your existing Agent client; the Assets workspace also supports in-app Codex conversations. BYOK connects your supported model accounts. Studio and the local service manage the editable work, while provider credentials remain outside project files. The public phase-one MCP surface contains thirteen tools: nine project tools, two template catalog tools, one BYOK media-use tool and one workspace asset tool. Configure provider keys in Studio, then use openmotion_media_use for model discovery and media generation through the local Gateway service. Use openmotion_assets to upload or generate reusable assets, retain versions and import a chosen version into a film. Asset library guide. Keys remain in the service; the public MCP contract does not include publishing.
| Layer | Technology | Start reading |
|---|---|---|
| Studio and editor UI | React 19, TypeScript 5.9, Vite 6, Tailwind CSS 4, Zustand, CodeMirror and Dockview | Studio source · Motion app · Editor development |
| Application runtime | Node.js 26.11.1 in CI, native HTTP, TypeScript execution and local files/JSON | server.ts · workspace.ts · Session architecture |
| Agent integration | Local stdio MCP, five core Skills and generated host adapters | mcp.ts · phase1.ts · Adapter generation |
| Multimodal generation | Codex media adapter, Atlas Cloud predictions, fal.ai queue integration and persisted generation jobs | Gateway service · Provider adapters · Model catalog |
| Composition and motion | HTML/CSS/JS, GSAP, a pinned composition engine and native timeline/history | Engine integration · Template source · Version adapter |
| Rendering and media | Chromium, Puppeteer Core, FFmpeg and FFprobe | Render service · Export verifier · Native runtime lock |
| Creative knowledge | Markdown, source packages, presets and comparison evidence | Motion.md · Core Skills · Community Library |
| Validation and packaging | Node test runner, Vitest, Studio checks, npm lockfiles and explicit distribution lists | Tests · Studio tests · CI · Distribution |
| Publishing and learning — Coming | Platform adapters, scheduling, version-linked feedback and retrieval; implementation still to be designed | Studio vision |
Dependency pins live in package.json, package-lock.json and the runtime lock. Models and third-party libraries retain their own terms; the application is Apache-2.0.
| If you work on… | A useful contribution | Entry point |
|---|---|---|
| Frontend and interaction | Improve timeline editing, media generation controls, accessibility or preview behavior | Studio · Media generator |
| AI and model infrastructure | Add a provider adapter or model preset using the shared job and media flow | Gateway design · Provider adapters |
| Agents and developer tools | Improve a host adapter, Skill, resource guide or project-tool workflow | Agent adapters · MCP contract |
| Motion and creative coding | Share a component, native template or Motion.md package with an actual remix | Components · Entry checklist |
| Video and rendering | Improve export reliability, media handling or reproducible validation | Engine notes · Export verifier |
| Social publishing | Help design the Coming connector layer: account access, release review, scheduling and version mapping | Publishing direction · Discuss a proposal |
Start with the local setup, choose one layer, and follow CONTRIBUTING.md and AGENTS.md. Keep user projects and credentials outside the checkout and preserve dependency pins and upstream licenses.
Product architecture · Studio development · Model Gateway · Contribution guide
Make a separate composition for each aspect ratio, review the cut in Studio and export an MP4 for manual upload.
| Version to request | What to adapt |
|---|---|
| Portrait short — for destinations such as Reels, Shorts, TikTok or Xiaohongshu | Hook, large readable type, framing and the placement of captions |
| Landscape film — for a product page, launch or YouTube video | UI detail, wider compositions and time to explain |
| Square feed cut — for a social campaign | A compact composition, headline and clear closing message |
Channel connections, scheduled publishing and performance feedback are planned.
| Area | Available today | Direction |
|---|---|---|
| Recreate and edit | Agent-led reference reconstruction, template adaptation, editable projects and MP4 export | More evaluated recreation cases and repeatable comparisons |
| Brand and knowledge | Motion.md with its Brand Kit section, Skills and source packages | Personal/team memory, RAG and evaluated Skill improvements |
| People and agents | Handoffs on the same local project | Timeline comments, shared review and collaborative editing |
| Multimodal creation | Built-in image, video, music and TTS integrations; generation, candidate selection and timeline adoption | Integrated search across footage, images, voices, music and Avatar services |
| Publish to every platform — Coming | Authored aspect-ratio variants and MP4 handoff | Platform connectors, release review, scheduling, automatic reframing and social presets |
| Feedback | Human review and saved project versions | Version-linked performance data and recurring production tasks |
Concept preview of planned collaboration. No release date announced. Studio vision · Knowledge and feedback
Share a remake, a reusable template or a Motion.md that captures the rhythm of a film. Include the reference and your editable project so another creator can try the same cut with their own footage.
| Contribution | What to include |
|---|---|
| A recreation | Reference and creator, your brief, editable project, preview, comparison and remaining differences |
| A template or component | Working source, editable choices, assets, preview and attribution |
| A Skill or design system | The method, keep/change rules and an example of what you actually ran |
| Brand Kit content for Motion.md | Identity, accurate product facts and approved assets within the creative specification |
| Agent support or editor improvements | A focused change with reproducible validation |
Library entry checklist · Contribute · Report an issue · Contributors · Media kit
The dedicated OpenMotion site is coming to open-design.ai/openmotion.
Motion showcase · OpenDesign Go · Discord · Feishu · X @OpenDesignDevs · X @OpenDesignHQ · YouTube
The template previews come from the current online catalog. Detail pages identify the reference brand; preview sources and hashes record the assets used here. Agent and model marks
OpenMotion is licensed under Apache-2.0. Third-party code, templates, media and fonts retain their own licenses and attribution.
| Source | Connection |
|---|---|
| OpenDesign | UI provenance, resource structure and brand direction; design system and Motion showcase |
| Hyperframes | HTML-to-video composition, Studio and rendering foundations, pinned to 0.9.7; creator references, external adaptation demonstrations and component source; engine notes, template notices and catalog provenance |
| MotionGit / adunext | Kinetic Tech source packaged as Presenter Tech; license and attribution |
| Hypit | Inspiration for agent-led viral-video cloning and editable variants; no runtime imported here |
| rea-video | Reference analysis and case studies for live-action unboxing and characters, code and screen footage; showcase attribution, no runtime imported here |
| OpenAI · Codex Originals | External brand-film inspiration; official campaign still and outbound viewing link |
| DeepSeek Harness / Super-agent prototype | Agent extensibility and continuing-task inspiration; the prototype is separate from OpenMotion's current runtime |
| Claude Motion / CapCut / ChatCut / OpenChatCut | Product references for agent-led creation, approachable AI editing and continued revision |
| OpusClip | Product reference for distribution and external scheduling; no built-in connector |
| GSAP / FFmpeg | Animation and media dependencies with versions retained in package.json and the runtime lock |
Asset sources · Additional showcase sources · Font notices · Studio license
The former HTML Anything application is preserved on the legacy branch. See the repository migration guide for the active branch and distribution boundaries.
