content / agent

ReelMimic

A local web app for planning and building 2D animations from reference videos with Claude Code or Codex.

At a glance

Purpose
A local web app for planning and building 2D animations from reference videos with Claude Code or Codex.
Runs in
Local agent with shell, Web service
Operating systems
macOS, Linux, Windows
Needs
Runtime: Node.js 22.18+, Python 3.10+, FFmpeg and Chrome; Needs internet: Yes; Needs accounts or API keys beyond your agent: Not stated
Files and data
Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type
Agent
Delivery
From GitHub
Version
Latest on the main branch
Access
Code on GitHub
Compatibility
The README requires Node.js 22.18+, Python 3.10+, FFmpeg, Chrome and either Claude Code or Codex CLI, logged in. The README says most testing happened on Windows (install.bat and start.bat); macOS and Linux should work but have had less testing (install.sh and start.sh). The README lists Traditional Chinese, English and Simplified Chinese for the interface. It also names Yating voices, Pixabay, Freesound, Openverse and Upload-Post.
External costs
According to the README, ReelMimic runs through your own Claude Code or Codex account, and the work counts toward that account's usage. API keys go in a secrets file. The README lists YATING_KEY for Yating voices used in narration, PIXABAY_KEY and FREESOUND_KEY as optional sources of more assets, and UPLOAD_POST_KEY as optional for posting through Upload-Post. It says Openverse works without a key. The README gives no prices. Your coding agent or model provider may charge for usage.
Permissions
The README says agents run locally through the user's logged-in Claude Code or Codex account and can run commands and render through Chrome. The README says CODEX_SANDBOX defaults to danger-full-access and workspace-write blocks the Chrome renderer. The README says ReelMimic accepts local reference videos and YouTube links and describes fetching online assets, with their source, author and licence logged. The README says API keys and paths go in ~/.reelmimic/secrets.json or a configured replacement path. The README names Yating narration and optional Pixabay, Freesound and Upload-Post keys, with Openverse used without a key. The README describes an optional post-video command: its default is a dry-run preview, while --send posts through Upload-Post and can schedule delivery. The README says --force can post a project with unresolved must-fix items.
Usage terms
MIT License, as stated in the repository. See its LICENSE file for the exact terms. The README adds that third-party skills and assets bundled in the repository keep their own licences, listed in THIRD_PARTY_NOTICES.md.
Interface
web

Code on GitHub

edenfunf/reelmimic

MIT

JavaScript2,419 stars259 forksLast pushed 12 Oct 2026 UTC

Show it a video you love. Get a new video in the same style. An AI crew (Claude Code or Codex) plans, builds and reviews it with you.

Topics: 2d-animation ai-agents ai-video animation claude-code codex multi-agent style-transfer

Public GitHub data fetched · 0 days old

View on GitHub ↗

What it does

The README describes ReelMimic as a local app for making 2D animations from a reference video and a brief. The README says ReelMimic accepts video files, phone recordings and YouTube links, and describes reference analysis followed by a storyboard, characters, assets and style frames for approval.

The README says multiple Claude Code or Codex agents build different parts of the video, finished shots go to another agent for review, and fixes include before-and-after screenshots. The README describes visible agent activity and timestamped comments on the result.

The README lists vector and motion graphics, hand-painted watercolor, crayon picture book, pixel art, paper cut-out stop-motion, whiteboard doodle and anime cel engines. The README says styles use Markdown files and the output is animation rather than live-action footage.

Who it is for

People who want to make 2D animated videos in the style of a reference video, using their own Claude Code or Codex account.

Example tasks

Drop in a reference video or paste a link, describe the video you want and choose Claude Code or Codex.
Chat about the plan, add screenshots or assets, then approve it to start production.
Open the Production line tab, which the README says shows each character and part of the video with review screenshots.
Leave a note at any second of the finished video and send all notes at once.
Add a new style by writing one Markdown file.

Getting started

You need Node.js 22.18+, Python 3.10+, FFmpeg, Chrome and a logged-in Claude Code or Codex CLI. Clone the repository, run ./install.sh (on Windows, double-click install.bat), then run ./start.sh (on Windows, double-click start.bat) and open the local address on port 4318. The README says the install script checks your setup and that you can run the check again with cd app && npm run doctor. API keys and paths go in a secrets file outside the repository, with the format shown in secrets.example.json. The README has the exact commands.

Limitations

According to the README, you need Node.js 22.18+, Python 3.10+, FFmpeg, Chrome and a logged-in Claude Code or Codex CLI. All work runs through that account and counts toward its usage, and the README says a job pauses if you hit a limit and can pick up where it stopped. The README says a 30 to 60 second video usually takes 1 to 3.5 hours after you approve the plan, and that watercolor and crayon are the slowest. The README limits the output to 2D animation rather than live-action footage of real people. The README says macOS and Linux should work but have had less testing than Windows, and that the five newer engines have had less real-world use than the first two. It says to make sure you have the rights to the videos you make. The repository can change at any time; check its README before you install.

Data practices

The README says production runs locally through the user's Claude Code or Codex account; model-provider data handling depends on that tool. The README says API keys and paths go in a home-folder secrets file outside the repository. The README says ReelMimic accepts online reference links and names Yating narration, optional Pixabay and Freesound asset sources, and keyless Openverse access. The README says online assets are logged with source, author and licence. The README describes posting through Upload-Post when the post-video command uses --send, including scheduled posting. The README does not mention telemetry.

Community experience

Not rated yet

Sign in to share your experience.

Comments 0

No comments yet.

Sign in to comment

Report a listing concern