EpisodeReel

Serial work: what each tool documents about continuity

Episode boards developed first, then a pilot brought to life

The page gives developing characters, story arcs and episode boards, then bringing the pilot to life, as a use of the board. Pilot is the operative word: the described work ends at the first episode, and a season is implied rather than stated. As of 2026-09-22.

Why a pilot is the easy instalmentThe first episode has no continuity obligations: nothing has to match, no face has drifted and the audience has no memory to contradict. The register exists because of episode nine.BoardsCharacters, story arcs andepisode boards developed on ashared surface.a planA pilotThe first instalment, withnothing yet established tocontradict.one episodeEpisode nineWhere a face has drifted, aroom has moved and canon canbe broken.What the page does and does not reachAn episode board is a real artefact a team can rearrange and disagree with, and it producesthe plan rather than the instalments.
Fig. 1 Stating the pilot as the milestone is honest about scope and leaves the column unanswered.
Luma Agents on the split into episodes, in the wording the page uses. Read 2026-09-22.
PointWhat the vendor's page statesHow this file reads it
The sentenceCharacters, story arcs and episode boards, then a pilotDocumented, as a described use
What it namesA board as the working surface, and a pilot as the outputA place and a milestone
What it leaves outEpisodes two to sixtyThe part where serial production becomes hard

Inclusion rule. Three points per reading: the sentence as the vendor published it, the thing that sentence names, and what it declines to settle. Nothing here is inferred from an interface or a demo. Order. From the published sentence, to what it names, to what it leaves open.

1A pilot is the easy episode and everybody knows it

The first episode has no continuity obligations. Nothing has to match, no face has drifted yet, and the audience has no memory to contradict. Every tool in this market can make a pilot; the register exists because of what happens at episode nine.

Stating the pilot as the milestone is honest about scope. It also means the column's actual question, what happens to a run of episodes, is not answered on this page.

2Boards are a real artefact and a partial answer

An episode board is something a team can look at together, rearrange and disagree with, which is more than a text box offers. Story arcs on the same surface put the season-level thinking somewhere visible.

What the board does not do, as described, is produce the episodes. It produces the plan for them, and the plan is the part a production is usually most able to make itself.

3Where this sits in the column

What the vendor publishes on the split, entry by entryEvery entry on the split column, with this one marked.What the vendor publishes on the split, entry by entryWhat the vendor publishes on the splitAI Drama Generator — What the vendor publishes on the split: The narrative stated to be structured automatically into episodes, scenes, dialogue and beatsAI Drama GeneratorAI Dramas — What the vendor publishes on the split: Nothing published on a script being split; scenes are written one at a time by the userAI DramasAnijam — What the vendor publishes on the split: Multi-episode short drama and one-to-two-minute micro drama both stated as supportedAnijamArcloop — What the vendor publishes on the split: Recurring episodes with consistent characters given as the outputArcloopcharacter.app — What the vendor publishes on the split: Story setup and connected Scenes named as stagescharacter.appCrano AI — What the vendor publishes on the split: Repeatable episode structures described as something the user buildsCrano AIDramaSo — What the vendor publishes on the split: A season of up to 60 episodes stated as plannable from one premiseDramaSoDramily — What the vendor publishes on the split: Episode scripts drafted from an idea, with a project stated to run to 120 episodesDramilyGenra — What the vendor publishes on the split: Structured episode outlines and scene breakdowns, described on the vendor's blogGenraGoogle Flow — What the vendor publishes on the split: Nothing publishedGoogle Flowinvideo AI — What the vendor publishes on the split: An agent plans a season episode by episodeinvideo AIKling AI — What the vendor publishes on the split: Nothing publishedKling AILTX Studio — What the vendor publishes on the split: Organised per production, no episode structureLTX StudioLuma Agents — What the vendor publishes on the split: Characters, story arcs and episode boards developed on the board, then a pilotLuma AgentsMedeo — What the vendor publishes on the split: Turning one story into numbered parts, recap clips and next-episode teasersMedeoNovi AI — What the vendor publishes on the split: Serialized mini-dramas stated to be creatable from scripts, novels or story outlinesNovi AIOpenArt — What the vendor publishes on the split: A director feature stated to structure a story into episodes and scenesOpenArtPexo — What the vendor publishes on the split: An open loop at the end of one cut carries the cast into the nextPexoPopShort AI — What the vendor publishes on the split: A script or novel uploaded into Drama Canvas, with characters, scenes and props extractedPopShort AISceneMixer — What the vendor publishes on the split: One upload analysed into characters, scenes, props and episodesSceneMixerShowrunner Studio — What the vendor publishes on the split: A written scene stated to return an episode, and a show shaped into a seasonShowrunner StudioStoryShort — What the vendor publishes on the split: Scene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhangerStoryShortTopview — What the vendor publishes on the split: Nothing publishedTopviewTrendShort — What the vendor publishes on the split: A script, draft or outline broken into shots, beats and visual prompts, one level below episodesTrendShortVidu — What the vendor publishes on the split: Nothing publishedVidu
Fig. 2 Every entry on the split column, with this one marked.
The split into episodes column with Luma Agents marked. Rows read between 2026-09-12 and 2026-09-22.
ToolWhat the vendor publishes on the split
AI Drama GeneratorThe narrative stated to be structured automatically into episodes, scenes, dialogue and beats
AI DramasNothing published on a script being split; scenes are written one at a time by the user
AnijamMulti-episode short drama and one-to-two-minute micro drama both stated as supported
ArcloopRecurring episodes with consistent characters given as the output
character.appStory setup and connected Scenes named as stages
Crano AIRepeatable episode structures described as something the user builds
DramaSoA season of up to 60 episodes stated as plannable from one premise
DramilyEpisode scripts drafted from an idea, with a project stated to run to 120 episodes
GenraStructured episode outlines and scene breakdowns, described on the vendor's blog
Google FlowNothing published
invideo AIAn agent plans a season episode by episode
Kling AINothing published
LTX StudioOrganised per production, no episode structure
Luma AgentsCharacters, story arcs and episode boards developed on the board, then a pilot
MedeoTurning one story into numbered parts, recap clips and next-episode teasers
Novi AISerialized mini-dramas stated to be creatable from scripts, novels or story outlines
OpenArtA director feature stated to structure a story into episodes and scenes
PexoAn open loop at the end of one cut carries the cast into the next
PopShort AIA script or novel uploaded into Drama Canvas, with characters, scenes and props extracted
SceneMixerOne upload analysed into characters, scenes, props and episodes
Showrunner StudioA written scene stated to return an episode, and a show shaped into a season
StoryShortScene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhanger
TopviewNothing published
TrendShortA script, draft or outline broken into shots, beats and visual prompts, one level below episodes
ViduNothing published

Inclusion rule. Every entry on this file appears below. A vendor stating that work is organised some other way is recorded as publishing something; silence is recorded as silence. Order. Alphabetical by tool name.

4The wording itself

  • Script to episodes
    Developing characters, story arcs and episode boards and then bringing the pilot to life is given as a use of the boardboards and a pilotLuma Agents, product page / recorded 2026-09-22
  • Script to episodes
    An open loop set at the end of one cut is described as carrying the cast straight into the next so a whole season stays consistentcut to cut rather than script to seasonPexo, micro drama page / recorded 2026-09-22

5Sources

Read from the product page at lumalabs.ai, checked 2026-09-22. The whole column is on script to episodes and this vendor on every column is on Luma Agents; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the cross-episode cast, the shape of the deliverable. Other readings of the same column: OpenArt, AI Drama Generator.