Continuity Director
Twenty continuity, directing, quality, runtime, collaboration, export, and reliability nodes with a bilingual ComfyUI dashboard.
Nodes (20)
An append-only ledger for who approved what, and when
One storyboard in, a full shot chain with takes and seeds out
A character sheet your prompts can't quietly drift away from
Diff two production states and get a list of exactly what changed
Record the exact runtime and models a run needs to be reproducible
Which takes can run in parallel, in what order
Ship the whole production as one portable, hash-verified JSON package
Give every request a stable fingerprint so double-submits don't double-run
Where your whole production becomes one hashable document
Move old payloads to a new schema version without breaking their hash
Title, aspect ratio, fps
A yes/no gate so bad takes never reach the export
Crash mid-batch and resume without re-running everything
How the last frame of one shot becomes the first frame of the next
A retry schedule that's exponential, bounded, and the same every time
Keep your hero standing in the same room across every take
Prompt, camera, duration, and seed pinned down
Let the numbers pick your best take instead of your gut
When two people edit the same production, something has to reconcile
Check a package's integrity without running a single line of it
Continuity Director
Continuity Director is a public, installable ComfyUI custom-node package for repeatable AI video production. It turns project rules, identity constraints, scenes, shots, references, quality metrics, execution dependencies, retries, checkpoints, approvals, and export state into structured production data.
[!IMPORTANT] Continuity Director does not replace a video model and cannot guarantee pixel-perfect identity. It makes continuity decisions, failures, and handoffs inspectable and reproducible.
Project stewardship
| Item | Status |
|---|---|
| Repository visibility | Public |
| Primary maintainer | @xinjian0101 |
| Maintenance model | Active maintainer-led open source |
| Current release | v0.8.42 maintained preview |
| Latest maintenance | 20 sequential hardening iterations covering validation, scheduling, retries, checkpoints, hashing, packaging, and frontend rollback |
| Maintenance evidence | v0.8.42 iteration log |
| Governance | GOVERNANCE.md |
| Maintainers | MAINTAINERS.md |
| Roadmap | ROADMAP.md |
| Release process | docs/RELEASING.md |
| Security | SECURITY.md |
| Adoption evidence | docs/ADOPTION.md |
Public Issues, pull requests, CI, changelog entries, automatic release publication, scheduled health checks, and Dependabot updates provide verifiable maintenance evidence.
What v0.8.42 hardens
- Whitespace and malformed JSON input handling.
- Collection normalization, deduplication, and path-ignore behavior.
- Manifest, storyboard, seed, duration, Take, and dependency validation.
- Finite-safe quality scoring and retry schedules.
- Deterministic execution plans and order-preserving checkpoints.
- Deletion-aware three-way merge diagnostics.
- Stable no-op migrations and explicit hash verification reasons.
- Canonical environment locks and reproducible, symlink-safe ZIP output.
- Stronger release validation and rollback-safe frontend node creation.
Production workflow
flowchart LR
A[Project / Character / Scene Locks] --> B[Shot Lock]
B --> C[Manifest Builder]
C --> D[Batch Director]
D --> E[Execution Plan]
E --> F[Quality Gate / Take Ranker]
F --> G[Audit / Merge]
G --> H[Verified Export Package]
R[Reference Handoff] --> D
V[Retry / Checkpoint / Environment Lock] --> E
The dashboard action Add starter chain inserts and connects the primary production path using a size-aware layout and rolls back partial creation failures.
Node map
| Stage | Nodes | Purpose | |---|---:|---| | Continuity locks | 5 | Project, character, scene, shot, and manifest state | | Directing | 2 | Storyboard expansion and reference handoff | | Quality | 3 | Thresholds, Take ranking, and continuity comparison | | Runtime and collaboration | 3 | Execution planning, audit events, and merge | | Export | 1 | Portable verified production package | | Reliability | 6 | Verification, migration, retries, checkpoints, idempotency, and environment lock |
<details> <summary><strong>Complete 20-node catalog</strong></summary>CDProjectLock, CDCharacterLock, CDSceneLock, CDShotLock, CDManifestBuilder, CDBatchDirector, CDReferenceHandoff, CDQualityGate, CDTakeRanker, CDContinuityReport, CDExecutionPlan, CDAuditEvent, CDThreeWayMerge, CDExportPackage, CDVerifyPackage, CDMigratePayload, CDRetryPolicy, CDQueueCheckpoint, CDIdempotencyKey, CDEnvironmentLock.
Installation
Git
From ComfyUI/custom_nodes:
git clone https://github.com/xinjian0101/continuity-director.git ComfyUI-ContinuityDirector
Restart ComfyUI, then search for nodes beginning with CD · or open the Continuity Director sidebar.
Release ZIP
Download continuity-director-v0.8.42.zip and its checksum from GitHub Releases. Extract the included ComfyUI-ContinuityDirector folder into ComfyUI/custom_nodes, then restart ComfyUI.
Update
cd ComfyUI/custom_nodes/ComfyUI-ContinuityDirector
git pull
Build locally
python scripts/build_release.py
Output: dist/continuity-director-v0.8.42.zip.
First production run
- Open the Continuity Director sidebar.
- Select English, 中文, or bilingual mode.
- Click Add starter chain.
- Configure Project, Character, Scene, and Shot locks.
- Build a manifest and provide storyboard JSON to Batch Director.
- Generate an execution plan.
- Apply quality and reliability nodes before export.
Example inputs are available in examples/.
Validation
python -m compileall -q .
python scripts/smoke_import.py
python scripts/maintainer_health.py
PYTHONPATH=tests python -m unittest discover -s tests -p "test_*.py"
python scripts/validate_release.py
python scripts/build_release.py --check
node tests/frontend_smoke.mjs
node tests/reliability_frontend_smoke.mjs
Documentation
- Documentation hub
- 20-iteration maintenance log
- Architecture
- Interface and localization
- Ecosystem value
- Adoption evidence
- Release process
- Administrator setup
- Maintainers
- Governance
- Roadmap
- Contributing
- Security
- Support
- Changelog
Compatibility and security
- Python 3.10–3.12 is tested in CI.
- Imported JSON is declarative data and is not executed.
- Production packages must not contain credentials.
- Integrity hashes detect changes; they do not provide authorization.
- External models, operating systems, ComfyUI installations, and third-party nodes remain separate trust boundaries.
Contributing
Bug reports, compatibility reports, adoption reports, documentation fixes, and focused feature proposals are welcome. Review CONTRIBUTING.md and CODE_OF_CONDUCT.md, then use the structured Issue forms.
License
Released under the MIT License.