Script editor overview

Understand cover and screenplay views, screenplay node types, derived entities, and safe editing habits.

Cover and screenplay are two views

The Script dimension contains the title-page cover and the screenplay editor. Cover fields describe the document; screenplay nodes describe the film. Keep marketing notes and planning prose out of the screenplay when they cannot be represented on screen.

Screenplay structure is semantic

Laper does not treat a script as a plain rich-text document. Paragraphs have screenplay roles such as scene heading, action, character, dialogue, parenthetical, transition, and related production forms. Their roles drive formatting, navigation, entity derivation, and export.

A scene heading is especially important. Editing it can update the scene's location and time context. A character cue can connect dialogue to a project character. If you paste text as undifferentiated action paragraphs, those relationships cannot be inferred reliably.

Use the cursor as context

The current selection and cursor give both the interface and AI a precise working range. Select the lines you want revised when the request concerns exact wording. Leave a collapsed cursor inside a scene when the request concerns that scene. Name a different episode or scene explicitly when the target is not visible.

Keep changes reviewable

Prefer one dramatic purpose per edit. Ask the AI to preserve named lines, characters, or beats when they must survive. After a large insertion, verify:

• the new scene is in the intended episode and order;
• headings contain the correct location and time;
• character cues use existing identities where appropriate;
• action remains filmable rather than explaining private thoughts;
• the outline still matches the actual sequence.

Collaborative edits enter the same document whether made by keyboard or AI. Version history is the right checkpoint before a wide rewrite; a second copy of the browser tab is not.