An agent that plans a season, against a scene that returns an episode
One page describes the agent turning an idea, a script or a show bible into a season plan, episode by episode. The other states that writing a scene returns an episode. A plan and a deliverable are different things to be handed. As of 2026-09-22.
| Point at issue | invideo AI | Showrunner Studio |
|---|---|---|
| What comes back | A season plan | An episode |
| What performs the work | An agent | Not stated |
| What the buyer still has to do | Make the episodes | Check what was invented |
Inclusion rule. One cell is a claim and one is documented. The contrast is between producing a plan and producing an instalment, which are often sold in the same sentence. Order. The plan first, then the deliverable.
1A plan is the part a production can usually make itself
Deciding that a novel becomes twenty-four episodes is editorial work a story editor does in a day. Making twenty-four episodes is the expensive part. A product that returns the plan has automated the cheaper half, which is worth having and worth naming accurately.
Accepting a show bible as input is the most specific thing on that page: it is a professional document, and naming it says the vendor is addressing people who have already done the development.
2An episode handed back raises the authorship question immediately
If one scene becomes an episode, most of the episode was written by the product. That is either the point or the problem, depending on who is paying and what they expect to own, and neither page addresses how much a writer controls.
For an adaptation with a plot to deliver, it is the first thing to settle. For a channel producing volume, it is the reason to buy.
3Agent and not stated are both weaker than they look
An agent is an arrangement of prompts and tools; naming one says nothing about what the plan consists of, where it is stored or what a user may change. The other page names no mechanism at all and simply states the result.
The register grades them differently because one describes an output a reader can hold and the other describes an intention. Both leave the revision question open.
4The wording both sides published
- Script to episodesThe agent is described as turning an idea, script or show bible into a season plan, episode by episodevendor claim
- Script to episodesWriting a scene is stated to return an episode, and a show started in any genre is described as being shaped into a seasona scene in and an episode out
5The same column, read for a third tool
On the split into episodes, SceneMixer's published page puts it in one line: One upload analysed into characters, scenes, props and episodes
. Its reading here, One upload read once, with the episode structure falling out of it, sets out what that line settles for a series and what it leaves to a production run.
6Sources
Read from the microdrama page at invideo.io and the home page at showrunnerstudio.com, checked 2026-09-12 and 2026-09-22 respectively. The full column is on script to episodes; the single readings behind this contrast are invideo AI and Showrunner Studio. Other contrasts filed here: AI Dramas and SceneMixer, Pexo and SceneMixer, Topview and Anijam.