Automation & Ops video-generationstoryboardvoice-synthesisself-hosteddockernovel-parsingasset-library

DramaClaw - Industrialized Short-Drama Production Line

An end-to-end AIGC video engine that turns manuscripts into finished films — putting big-studio production power into the hands of individual creators.

FollowAgents review · FARS-2.1
Not recommended
0/ 100 5-point scale 0.0 / 5
1 2 3 4 5 6
1Trust0 / 29 · 0.0/5

Insufficient evidence: The repository does not provide explicit documentation on permission model, user confirmation mechanisms, data flow transparency, sensitive data handling, dependency security audits, external effect controls, rollback mechanisms, or source attribution. All trust criteria are scored 0 due to lack of evidence.

2Reliability0 / 14 · 0.0/5

Insufficient evidence: No explicit evidence of self-consistency, dependency availability, or failure messages. Although test files exist, no execution results or reliability guarantees are provided.

3Adaptability0 / 18 · 0.0/5

Insufficient evidence: README describes broad scenarios but lacks detailed capability boundaries, trigger precision, or environment fit documentation.

4Convention0 / 18 · 0.0/5

Insufficient evidence: README provides installation instructions and documentation links, but lacks explicit evidence of information architecture, naming stability, examples/FAQ, known limitations, versioning/changelog, or maintenance responsibility. License metadata is NOASSERTION, but README declares Elastic License 2.0.

5Effectiveness0 / 13 · 0.0/5

Insufficient evidence: README claims output usability and marginal value, but lacks cost-benefit analysis or actual output verification.

6Verifiability0 / 8 · 0.0/5

Insufficient evidence: Claims in README lack traceability, no cross-source corroboration, and no separation of facts and inferences.

Evidence confidence: Low Reviewed Aug 11, 2026 Reviewed revision f33ac189500e
The upstream repository has new commits since this review. The score still applies to the reviewed revision shown and may not cover the latest changes.
Safety controls not found in source: least-privilege scoping, confirmation before acting, data-flow disclosure, sensitive-data handling, dependency security, disclosed external effects, rollback or recovery path, verifiable attribution
Before you use it
  • The repository does not provide an AGENTS.md manifest, and the publisher identity is unverified; proceed with caution.
  • License metadata is NOASSERTION, inconsistent with the Elastic License 2.0 declared in README; verify.
  • Dependencies include many unpinned packages, posing supply chain risks.
  • Functional claims in README lack verifiable test or execution evidence.
Review evidence [1][2][3][4][5][6][7][8]
See the full review method →

What does this agent do, and when should you use it?

DramaClaw is a source-available, industrialized short-drama production pipeline. Feed it a novel manuscript and it automates character extraction, episode planning, script generation, storyboard and first-frame art, voice-over synthesis, and final video editing. Built for creators, indie studios, and creative engineers, it can be self-hosted to run the entire drama factory on your own infrastructure — no stitching together a dozen tools or sending material to a black-box cloud. Core capabilities include novel parsing and story graphs, an asset library with identity consistency, episode and beat planning, multi-mode script generation, a line-art storyboard system, emotion-aware TTS, and video compositing and export. All inference goes through a remote OpenAI-compatible gateway, so the local footprint is light and no GPU is required for the standard pipeline.

DramaClaw parses a user-supplied novel into a queryable story graph (characters, relationships, timeline). Through its REST API (port 8780) and web UI (port 8080) it runs a series of async tasks: episode planning, script generation in adaptive/literal/staged modes, beat-driven storyboard and first-frame image generation, voice-over synthesis via IndexTTS2, and final assembly/export of episodes with subtitle (SRT) files and the full asset pack. It maintains an Asset Library for characters, scenes, props, and voices to lock identity across episodes, uses a Director World (3GS) to preserve spatial/camera consistency, and offers a Xia Director conversational assistant plus a Task Center for status, logs, cancel/retry, and resume-from-checkpoint. All state and media live on the local filesystem under the 'ce-data' volume — no Postgres, Redis, Celery, or Ray required.

  1. A web novelist who wants to turn a long-running series into multi-episode short dramas without manual script/storyboard work.
  2. A small ad agency that needs quick-turnaround product videos and short promo spots using the same pipeline with custom style templates.
  3. An otome game studio that uses the storyboard, TTS, and asset library to generate branching dialogue and scene assets.
  4. A creative engineer who wants to self-host the entire pipeline and plug in custom OpenAI-compatible models via a BYO gateway.
  5. A video production house that needs to keep character and scene consistency across many episodes, using Director World and the infinite canvas for iterative refinement.

What are this agent's strengths and limitations?

Pros
  • End-to-end industrialized pipeline from script to finished film, with each step independently runnable and resumable.
  • Self-hostable via Docker; media and state stored locally on filesystem for data control.
  • Model-neutral: connects to any OpenAI-compatible text/image/video/audio gateway, with BYO option.
  • Packages advanced features like identity/scene consistency (3GS), infinite canvas dual-track workflow, and the Xia Director agent.
Limitations
  • Default setup depends on DramaClaw's official gateway and a DC key, which may introduce cost or external dependency.
  • Self-hosting a fully local model setup requires additional configuration and GPU/CUDA support only documented for optional features.
  • The Elastic 2.0 license restricts reselling hosted service, which may limit some commercial use cases.
  • Some advanced features (e.g., world model) are still evolving and may not be production-ready for all users.

How do you install or deploy this agent?

Recommended Docker approach: clone the repo, copy .env.example to .env and set PROMPT_EXPORT_PASSWORD, then run docker compose up -d --build (starts api and web services). For a no-build install, download the release compose file: curl -LO https://raw.githubusercontent.com/dramaclaw/dramaclaw/main/docker-compose.release.yml and run docker compose -f docker-compose.release.yml up -d. For local development you'll need Python 3.11–3.12, uv, and ffmpeg; then run uv sync and uv run novelvideo api --port 8780.

How do you use this agent?

Once running, open http://localhost:8080, go to Settings → Model Config → Official, and paste a DC key obtained from https://relayclaw.cdnfg.com (or configure your own OpenAI-compatible endpoint). Create a project, upload a manuscript, then step through the pipeline stages in order: parse, plan, script, storyboard, voice, composite. Each stage has its own UI and can be skipped or resumed. You can also drive everything programmatically through the REST API on port 8780 or ask the Xia Director agent to advance tasks conversationally.

How does this agent compare with similar options?

Compared to other tools in the space (e.g., L*TV, R*Hub, S*ko), DramaClaw differentiates with a full closed-loop short-drama production chain, including asset library, scene consistency, director world, Xia director agent, infinite canvas, and dual-track workflow, while being source-available and self-hostable.

FAQ

What hardware do I need to self-host DramaClaw?
The standard pipeline needs no GPU; 2 vCPU/4GB RAM and a few GB of disk are enough since inference runs on the remote gateway. Only the optional 3GS world model requires GPU + CUDA.
Can I run fully local models?
Yes, by configuring a self-hosted OpenAI-compatible gateway (e.g., newapi) and mapping your local models, but you'll need to handle model mapping and possibly accept performance tradeoffs.
What if a generation task fails midway?
The Task Center shows status, logs, and lets you cancel, retry, or resume from the last checkpoint, so long runs are safe.
Can I use DramaClaw for non-drama content?
Yes, the same pipeline handles short ads, e-commerce product videos, and otome game content with minor tweaks to style and script.
Do I need coding skills to use DramaClaw?
Non-technical users can operate via the Web UI; technical users can leverage the REST API and configuration to customize pipelines and integrate models.

Related agents