Skip to content

Logline, synopsis, and treatment#

Your story told three ways — one sentence, one short summary, and a few pages of prose — each one a living document Nisaba reads before she helps.

The logline is your one-sentence pitch, the North Star every other part of Nabu points back to. The synopsis is a short summary — roughly a page. The treatment is the fuller prose version. Nisaba reads all three first, so a sharp logline and an honest treatment make everything she does more on-target.

The logline#

Your logline is created inside the wizard — Nabu's guided start-a-script flow. At the Choose Your Direction step you pick one of Nisaba's pitches, and that produces your logline. A small editable logline banner rides along through the rest of the wizard. The wizard’s banner and the separate logline editor lock while logline work is queued, running or retrying; paused or finished work releases that lock. The wizard also holds logline edits while the treatment is being drafted. A logline rewrite requested in Nisaba’s chat holds the same editors while the rewrite runs; ordinary chat leaves them editable.

Unsaved words from before the lock stay in the editor. After it unlocks, they can save over the generated logline; they are not yet offered as a separate recoverable draft. Copy unsaved words before cancelling to use the generated line. A field with no open edit reloads the new server line.

After the wizard, your logline sits in the Story Core, under your dramatic question, on the Story page (click Story in your project's sidebar). There's no logline editor there.

Note: Nabu won't accept an empty logline — it keeps the last real sentence rather than blanking your North Star.

Reworking it later#

To change your logline after the wizard, ask Nisaba in chat — say something like "tighten the logline" or "make the logline punchier."

Uses your plan: Asking Nisaba to rework your logline uses your plan.

The synopsis#

You write your synopsis with Nisaba inside the wizard, at the step called The Synopsis. Your words save themselves as you go. Click Expand into treatment when done — Nabu saves your latest words before leaving the page. To skip Nisaba's draft and start on a blank treatment, click Write it myself instead.

The synopsis editor offers inline AI suggestions — Nisaba can propose edits right in the text, which you accept or reject one at a time (see Inline AI suggestions). Version tabs let you switch back to earlier saved versions.

After the wizard, your synopsis is read-only — it comes from the treatment. You'll find it in the Story Core on the Story page. To reshape it, ask Nisaba in chat — say "rework the synopsis" and she rewrites the document directly. If it has fallen behind the treatment, an Update from the treatment button appears beside it; it rewrites the synopsis from your current treatment.

The treatment#

Open Treatment from your project's sidebar. The page has two tabs:

  • Treatment — your treatment, ready to read. This is the one you edit.
  • Logline & synopsis — your logline and synopsis, read-only. They come from the treatment.

From the Treatment tab you can edit it, generate one from your script, or ask Nisaba about a passage.

Reading and editing#

  • Click Edit treatment to open the treatment workspace — a prose editor with autosave, inline AI suggestions, version tabs, and a reference panel showing your outline and scene summaries. Done saves and returns you to the read-only view.
  • Right-click a passage in the read-only view and choose Ask Nisaba about this passage to start a paid conversation about it; Nisaba speaks first. Copy uses your selected passage, and an empty selection keeps the browser menu. This is conversation only — it won't change the treatment. To change the prose, edit it yourself or ask Nisaba inside the workspace.

Generating a treatment from your script#

If you've written scenes but have no treatment yet, the page offers Generate Treatment from Script. Nisaba reads your screenplay and writes a treatment. This takes a few minutes and shows progress.

If generation fails, Nabu shows “We’ve been notified, please try again in a moment” with the job ID; wait a moment, then try again.

If you already have a treatment and want a fresh one, Regenerate writes a new treatment from your current script. Nabu asks you to confirm and saves a snapshot you can roll back to.

Uses your plan: Generate Treatment from Script and Regenerate use your plan.

How Nisaba revises these for you#

Inside the synopsis or treatment workspace, you can ask Nisaba — through the chat panel — to revise the document directly. She rewrites the actual document and the editor reloads to show the new words. A revision:

  • Keeps a snapshot first, so the version before her edit is saved.
  • Saves the real document, not a draft she only describes in chat.

Nisaba won't tell you a document changed unless the change truly went through.

Moving forward in the wizard, and the drift check#

When building a project through the wizard, the synopsis step ends with Expand into treatment and the treatment step ends with Finalize Treatment. Finalizing locks your treatment as the version the rest of the wizard builds on. An unanswered request is kept through a reload and checked again. Once Nabu has answered, the next press, including Try again after a confirmed refusal, starts a new attempt using your current saved words. Going Back and expanding again asks from the synopsis now on file. Nabu returns an already running draft without starting another. If the wizard has already moved or the treatment is already finalized, Nabu refreshes the saved wizard state and shows that step. An expired unanswered request starts no work on its own; a later press checks whether it is still pending.

When you click Expand into treatment, Nabu first runs a drift check: it makes sure the documents your synopsis is built on (like your logline) still agree with it. Drift means two documents have quietly fallen out of step.

  • If everything lines up, Nabu moves on straight away.
  • If something has drifted, a popup shows which documents are out of step. You can Update them, Keep editing, or Proceed anyway.

Note: These steps live in the wizard. In the everyday Treatment editor from the sidebar, there's no Finalize — you simply edit, and your words save themselves.

What each control does#

Document Where you edit it How it saves Nisaba can…
Logline The wizard's Choose Your Direction step; ask Nisaba to rework it; read-only on the Story page Saved as you go in the wizard; Nisaba's reworks save on success Draft it, then rework it on request
Synopsis The wizard's The Synopsis step; ask Nisaba to rework it; read-only on the Story page As you go; Expand into treatment or Done saves and exits Revise on request, or suggest inline edits
Treatment The treatment workspace (Edit treatment on the Treatment tab); Finalize Treatment in the wizard As you go; Done or Finalize Treatment saves and exits Generate from script, regenerate, revise on request, or suggest inline edits

If your usage cannot cover a treatment polish, Nabu shows the usage refusal before starting it and keeps you at the treatment step with your saved words untouched. If a treatment polish cannot be completed, your saved treatment is kept and Nabu explains the interruption. A synopsis run that completes only some scenes reports how many were written and how many could not be completed.

Good to know#

  • During a quiet stretch the bar says Working... instead of a percentage.
  • The logline is read first, everywhere. Every part of Nabu that helps you starts from your logline.
  • Versions are kept. Both workspaces show version tabs; regenerating or revising saves the prior version first.
  • Finalizing is a wizard thing. The drift check happens while building a project — not in the day-to-day editors.