Rewrite and polish a selection

A line that loses its tension, a beat that lands too softly, wording you can taste but cannot fix: that is selection work. The range is exact, and these few lines are what changes. Anything that crosses chapters or modules—“the turn in this chapter is weak”, “align the foreshadowing in chapters 3 and 7”—belongs in the chat, where the proposal can list every affected item.

The four actions pull in different directions: rewrite finds another phrasing, expand thickens a skeleton you already wrote, condense takes the water out, polish leaves the content alone and works on the surface. “Harder, fewer adjectives” belongs in the note box; swapping actions will not get you there.

1. 1
   Select

   Drag across one or several lines in the script. Selection may cross nodes; the range you get is the text you chose.
2. 2
   Right-click

   Right-click the selection. The top half of the menu holds rewrite / expand / condense / polish. Dragging with the left button never pops a floating bar—you ask for it when you want it.
3. 3
   Add one requirement

   Type what must stay and what must change in the box under the actions, then press Enter. Leave it empty and the action’s default lean applies.
4. 4
   Read the proposal

   The request enters the agent chat while your selection stays highlighted; the card reads “AI rewriting…” and can be stopped at any time. Anything that would write into the script comes back as a pending proposal, with a field-by-field before / after comparison on the card.
5. 5
   Not happy? Ask again on the same draft

   Under the proposal is one line: tell it what to change and press Enter to get another version built on this one. You do not restate the range from scratch.

• “Apply changes” puts the text into the script and onto the project undo stack as one edit—undo once and the whole card steps back, including any other operations on it.
• “Do not apply”, or simply closing the card, leaves the script exactly as it was. “Adjust proposal” adds your note and asks for another pass.
• Proposals expire. An old card shows “Proposal expired”; “Update and continue” regenerates it against the project’s current state instead of pressing an old draft over your newer edits.
• If the project changed elsewhere before you confirmed, the whole card is refused rather than silently merged.

Expansion and continuation obey the script’s heading grammar: chapter, scene and scene setting headings and character lines all have a fixed shape. A malformed result is refused for the whole operation, so no half a name ever becomes a character card.

Script patches keep each line’s identity—rewriting text does not turn the line into a brand-new node. When a proposal genuinely changes a line’s type or its speaker, the card lists the new type and target character separately from the text diff, so you see it before you confirm.

• No valid selection, no action entries: select text first.
• Esc, clicking elsewhere, or choosing other text clears the old highlight and range.
• These actions need a signed-in cloud account. If a passage is too long for the model to handle, it says so instead of truncating and sending.
• Custom quick actions and the prompt-snippet library are gone. What exists is these four actions plus one free-text requirement.

How proposals work and what they may touch: AI collaboration overview and What AI may write.