Script
Writing and managing the episode screenplay in Fountain format.
The Script page is where you write and manage the screenplay for an episode. Screenplays are written in Fountain format -- a plain-text markup language designed for screenwriting.
The three modes
The page is not tabbed: it shows one of three modes at a time, and the button at the top right switches between them.
View
The default. Displays the screenplay as formatted script pages. A resizable side panel lists the episode's Scenes -- each with its scene number as a button -- so you can jump to any scene in a long script. A scene number shown in red, or as a ?, means the heading has no stable #N# number yet.
Edit
A raw text editor for writing Fountain markup directly. Use Save to persist changes, Cancel to discard. Fountain Syntax Help opens the syntax reference, and while the script is still empty a Load Template button inserts a starter structure.
Saving is what updates everything downstream -- there is no separate parse or analyse button here. The AI pass over the finished draft is run from Review Screenplay on the Screenplay Review page.
A script that is not in Fountain yet
If you wrote the script somewhere else -- in a word processor, or as plain prose -- paste it into the
editor and ask the assistant to convert it. It rewrites the whole script in the form this app reads:
scene headings with their #N# numbers, character cues, dialogue and parentheticals, and any
paragraph that is none of those left where it is as an action line. It does not invent scenes,
characters or dialogue your draft does not contain, and it does not quietly drop anything it cannot
classify. Paste its answer back over the draft and Save -- that save is what creates the scenes and
picks up the characters.
Change Source
Links the screenplay to an external source:
- Google Docs -- paste a sharing URL; the platform fetches the latest version on refresh
- Final Draft XML -- upload a
.fdxfile export - Local file -- upload a Fountain
.fountainfile
With a source linked, the button at the top right becomes Refresh, which pulls the latest version in; pulling a document in re-parses it exactly as saving does. Its dropdown carries Change source and Edit local copy. Unlinking removes the connection and returns to local editing.
A screenplay you write in the app has no external source to pull from, so it has no Refresh -- the button is Edit, with Change source on its dropdown, and Save is what updates everything downstream.
Assets are not created here
The panel beside the text lists the episode's scenes only. While you are drafting, a heading is often still a placeholder -- so a name in the script is not yet a name worth creating an asset from.
The check that every character and location the script names exists as an asset runs in Script Analysis, after the AI pass has had a chance to tell a new name from a spelling of an existing one. Each unresolved name is shown there with the line it came from, and can be created in one click. You can also create one from the scene that needs it -- see Scenes.
Scene parsing
Whatever changes the stored screenplay parses it: saving the editor, refreshing from a linked document, and importing a Final Draft file all do the same work. There is no separate button for it.
- Each scene heading (e.g.
INT. KITCHEN - DAY #1#) becomes a scene entry in the episode's scene list - The scene text (action lines and dialogue) is stored separately and used for AI generation
- The
Title:on the screenplay's title page becomes the episode's name -- unless you have renamed the episode yourself, in which case your name is kept - Dialogue is extracted onto each scene, so lines you can record appear without any AI step
- A scene whose text did not change is left completely alone, including its shots
- A scene the screenplay no longer mentions is shelved, not deleted -- it keeps its media and comes back if its scene number reappears
Scene numbers are scene identity. The #1# at the end of a heading is what ties a scene to
everything already attached to it. Inserting a scene between 1 and 2 should number it 1b rather
than renumbering the rest; renumbering makes the platform treat every scene after the change as a
different scene.
Shots come from the scene, not from here
Shots are generated one scene at a time, from the scene's own band on the shot list -- not from the Script page. That keeps a screenplay edit from regenerating shot work across a whole episode.
Generating a scene's shots also fills in the scene's location and cast. Each shot then inherits those, and only carries its own where it genuinely differs -- a close-up on one character in a two-hander, or a cutaway to another part of the set. Change the location on the scene and every shot that inherits it follows.
Screenplay Review
The Screenplay Review page runs an AI analysis of the full screenplay. You can configure the review instructions at the project level and run the analysis at any time. Results stream in and are rendered as markdown. A timestamp shows when the last review was generated.