ReelMimic Style-Mimicking Video Studio
Feed it a video you love; get a brand-new animation built in the same style.
- Source repo
- edenfunf/reelmimic
- Stars
- ★ 2.7k
- Last updated
- 1d ago
- License
- MIT
- Primary language
- JavaScript
- FA score
- 50/100 · Major gaps
At a glance
- Works with
- Portable with changesCodex · Claude Code
- You'll need
- Typical use
- A solo creator who wants the pacing and camera moves of a phone clip applied to their own original characters
- Main limitation
- Slow turnaround: a 30–60 s video typically takes 1–3.5 hours after plan approval, with watercolor and crayon the slowest
- Source review
- 50/100 · Major gaps
What does this agent do, and when should you use it?
ReelMimic is a locally run, browser-operated studio that turns a reference video into an original animation that borrows its style. You drop in a file, a phone recording or a YouTube link, describe what you want, and it first breaks the reference down into shot count, shot lengths, BPM, transitions, colours, framing and camera moves. It then presents a plan of storyboard, characters, assets and style frames for you to discuss and approve. Production is split across up to 6 AI agents working in parallel, and every finished shot is handed to a separate agent for review, with fixes backed by before-and-after screenshots. It runs entirely through your own Claude Code or Codex account, renders 2D animation through seven drawing engines, and can push the finished cut to social platforms via Upload-Post.
After ingesting a dropped file, phone recording or YouTube link, ReelMimic derives shot count, shot lengths, BPM, transitions, colours, framing and camera moves, then generates a plan covering storyboard, characters, assets and style frames, which you can revise through the side chat (text or screenshots). On "Approve and start", work is split into units executed by up to 6 concurrent agents; each completed shot goes to a fresh agent for review, and every fix must ship with before-and-after screenshots that the reviewer checks. The Production line tab shows where each character and each part of the video stands. Seven drawing engines are available — vector/motion graphics (built on HyperFrames), hand-painted watercolor (built on painted-animation), crayon picture book, pixel art, paper cut-out stop-motion, whiteboard doodle and anime cel — and each style is a Markdown file, so adding one needs no code. Assembly relies on FFmpeg, the Chrome renderer and a Python toolchain, and a finished project can be published with npm run post-video -- <project id> --platforms tiktok,instagram,youtube, which only actually sends with --send.
- A solo creator who wants the pacing and camera moves of a phone clip applied to their own original characters
- An indie music-video team needing quick hand-painted or crayon-style animation
- A marketer replicating the cadence and transitions of an existing brand animation for a new product film
- A developer who wants the whole pipeline to run locally on their own Claude Code or Codex quota without uploading source footage
- A tinkerer adding custom drawing styles or rendering engines, describing styles in Markdown
- A content operator who needs to push the finished animation to TikTok, Instagram and YouTube
How do you install or deploy this agent?
Requirements: Node.js 22.18+, Python 3.10+, FFmpeg, Chrome, and a logged-in Claude Code or Codex CLI.
git clone https://github.com/edenfunf/reelmimic.git && cd reelmimic
./install.sh # on Windows, double-click install.bat
./start.sh # on Windows, double-click start.batThen open <http://localhost:4318>. The install script checks your setup and can be re-run any time:
cd app && npm run doctorAPI keys and tool paths live outside the repo in ~/.reelmimic/secrets.json; the format is shown in secrets.example.json:
{
"YATING_KEY": "Yating's Taiwanese Mandarin voices, for narration",
"PIXABAY_KEY": "",
"FREESOUND_KEY": "",
"FFMPEG_DIR": "",
"CHROME_PATH": "",
"CODEX_BIN": "",
"PYTHON": "",
"CODEX_SANDBOX": "danger-full-access",
"BUILDERS": 6,
"MAX_AGENTS": 12,
"PORT": 4318
}How do you use this agent?
On the home page, drop in a reference video or paste a link, describe what you want, and pick Claude Code or Codex. Wait for the breakdown and plan, then request changes in the chat panel on the right; if the plan asks for something (lyrics, say), supply it or skip it, and hit "Approve and start". During production, the Production line tab tracks each character and each part of the video along with review screenshots. When it finishes, scrub to any second and leave a note, then send all notes at once.
To publish a finished cut that has passed final review:
npm run post-video -- <project id> --platforms tiktok,instagram,youtube
npm run post-video -- <project id> --platforms tiktok --at 2026-10-05T18:00 --tz Europe/Madrid --sendWithout --send it is a dry run and nothing leaves your machine; re-running the same video will not post it twice.
What are this agent's strengths and limitations?
- Parallel multi-agent production with cross-review: up to 6 agents work at once and each finished shot is reviewed by a different agent, so nobody grades their own output
- Fixes must come with before-and-after screenshots that the reviewer verifies, avoiding one-shot generate-and-done
- Seven 2D drawing engines plus Markdown style files, so new styles need no code
- Runs on your own machine through your own Claude Code or Codex account, so source footage is not uploaded to a third party
- Strong observability: each agent's reasoning, commands and inspected frames are visible, with a full log
- Slow turnaround: a 30–60 s video typically takes 1–3.5 hours after plan approval, with watercolor and crayon the slowest
- 2D animation only, and it explicitly will not produce live-action footage of real people
- Tested mostly on Windows; macOS and Linux have had less testing
- The five newer drawing engines are young and have had less real-world use than the first two
- Codex defaults to the danger-full-access sandbox (workspace-write blocks the Chrome renderer), and everything is bound to a Claude Code or Codex account with its usage limits
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| ReelMimic Style-Mimicking Video Studio This agent | 50 · Major gaps | — | ★ 2.7k | 1d ago | JavaScript | Codex · Claude Code |
| ArcReel Video Creation Workspace | 52 · Major gaps | Self-hosted serviceFree + model costs | ★ 5.5k | today | Python | OpenAI API · Claude API |
| Image-to-Editable-PPT Skill | 53 · Major gaps | Agent plugin / skillFree + model costs | ★ 2.9k | 27d ago | Python | Codex |
| OpenMontage Video Studio | 48 · Major gaps | CLIFree + model costs | ★ 68k | 1d ago | Python | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
README and SECURITY.md show secrets stored outside the repo at ~/.reelmimic/secrets.json, the server binding to 127.0.0.1 by default, and social posting requiring an explicit --send with dry-run default — all positive. However, CODEX_SANDBOX defaults to danger-full-access, granting the agent full filesystem and command execution, which weakens least privilege (deducted); data flow is described only in prose with no verifiable flow diagram or code-level evidence (deducted); requirements.txt pins no versions and there is no audit or vulnerability-scanning evidence (deducted); rollback is limited to resuming a paused job, with no artifact or config reversion described (deducted).
The README is internally consistent about workflow, engine count, runtime, and account usage, with no contradictions found (credited). But dependencies are listed by name without version pinning, and Node/Python/FFmpeg/Chrome must be installed externally, so availability depends on the environment (deducted); failure messaging is only evidenced in smoke.sh as exit codes and assertions, with no product-level error or recovery guidance (deducted).
The README clearly states the 2D-only scope, seven drawing engines, no live-action of real people, runtime ranges, and account-usage limits (credited); audience and first-video steps are well covered (credited). But trigger conditions — when an existing style matches versus when a new-style proposal is generated — are vague, with no precise decision rule (deducted); environment fit is primarily Windows-tested with less macOS/Linux coverage, i.e. partial (deducted).
The README is well structured with install, settings, docs index, and third-party notices, and the MIT license file is complete (full marks). But there is no version number or CHANGELOG (0); maintenance responsibility rests on a single email in SECURITY.md and the publisher is unverified (deducted); naming stability shows a migration from CLONE_STUDIO_SECRETS to REELMIMIC_SECRETS, indicating a rename (deducted).
Output is a playable video with per-second comments and batch submission, giving good usability (credited); it adds value over raw Claude Code/Codex use through style breakdown, multi-agent division of labor, and cross-review (credited). But a 30–60s video takes 1–3.5 hours and consumes the user's own AI account quota, making cost-benefit heavy for ordinary users, with no cost estimate or optimization evidence (deducted).
Most capability claims (multi-agent, review screenshots, style learning) have no corresponding code or tests in the provided files; only smoke.sh covers the vendored skill's eval harness, which is thin evidence (deducted); cross-source corroboration is limited to partial agreement among README, SECURITY.md, and CI config, with no independent confirmation (deducted); separation of fact from inference relies on prose alone, without marking what is verified versus intended (deducted).
- CODEX_SANDBOX defaults to danger-full-access, giving the agent full filesystem and command execution; prefer workspace-write or explicit grants.
- requirements.txt pins no dependency versions and no audit or vulnerability-scanning evidence is provided, posing supply-chain risk.
- README claims about multi-agent collaboration, review screenshots, and style learning lack code or test corroboration; static review cannot confirm real implementation.
- Publisher identity is unverified and maintenance rests on a single email in SECURITY.md, leaving the update path and long-term commitment unclear.
- No version number or CHANGELOG, plus a rename from CLONE_STUDIO_SECRETS to REELMIMIC_SECRETS, so upgrades and compatibility need care.
- Running consumes the user's own Claude Code/Codex quota, and a 30–60s video takes 1–3.5 hours, making cost relatively high.