Product tour · Part 1 of 4

Write with AI. Keep the final word.

Seven focused actions help draft, check, translate, structure, source, and visualize your work. Every result arrives as a review you approve before it changes the file.

The proof

Before and after bytes. One human review gate. Nothing saved without approval.

The proposed document in Flow, scrolled to the corrected sentence with the change highlighted.
The result leads, with the change marked · Nothing is saved until you approve it

Agency

One path from request to approved change.

Proofread, Summarize, Translate, two table conversions, Expand with Sources, and Visualize all use the same trust path. Flow states the scope, route, and cost first. The result arrives as a review. The file changes only after you approve it.

  1. Before

    Know the bargain before the run.

    Hover an action to see what text it will use, what it should cost, which model will run, and whether the text leaves your Mac.

    Flow's document tool strip with Proofread open, showing the document scope, no cost, and the local model that would run.
    Scope, cost, model, and locality · Before the click

  2. Review

    Judge the writing. Inspect the bytes.

    Flow opens on the proposed document with the change highlighted. Exact changes, evidence, and named checks stay one tab away.

    Flow's review pane on the proposed document, scrolled to a corrected sentence with the changed words highlighted.
    The result first · Exact changes one tab away

  3. Approve

    Your review unlocks the save.

    Approve & Save stays disabled until you confirm the review. Reject changes nothing. A byte guard stops an older run from landing over newer work.

    Flow's decision footer with a human-review checkbox and a disabled Approve and Save button beside Reject and Later.
    Nothing saved until you approve · Reject changes nothing

Expand with Sources

See the agent work. Stop it when you want.

Expand can read the document and search folders you opened. Flow names each lookup as it happens, counts real tokens and cost, and keeps pause and stop in reach. The final writing still returns through the same review and approval path.

In Flow 1.6, lookups run on this Mac with a local model as well as through supported Anthropic models. The local path reads the document and searches open folders without a provider token charge; each lookup is receipted. A hosted run sends the permitted text to its provider. The run still has a limit of 12 lookups or 180 seconds. If it reaches that bound, nothing in the document was changed.

Orionfold Flow during Expand with Sources: a banner lists folder searches as they happen, tokens and dollars accrue in the title bar, and pause and stop remain available.
Historical hosted-run capture · Flow 1.5 (1255) · August 26, 2026 · Live lookup progress

Consent

Destination, sources, estimate, authority.

For a hosted route, the sheet names what will leave, where it will go, and the estimated cost to the digit. Permission is read-only and granted once.

Flow's Leaves this Mac sheet naming Anthropic, the included sources, an exact estimate, read-only authority, and Allow Once.
The complete bargain · Before the run

Receipt

Estimate before. Recorded cost after.

One measured run estimated 0.000924 USD and later recorded 0.026684 USD. Those are two facts, kept separate. The saved change is bound to its before-and-after fingerprints.

A Flow receipt's cost block: the recorded cost priced from the cost table, the model, the provider, and that the run went to Cloud.
Recorded cost · Priced from the cost table · Model, provider, and route named

The screenshots show a historical hosted run. The local lookup path shipped in Flow 1.6. Web Lookups is a separate control in Settings ▸ General and starts off; when enabled, words from a document may appear in the requested address.

The tool strip

AI belongs beside the work.

Seven actions sit beside bold and italic. Ready actions stay in colour. An action that cannot run stays visible, names the reason, and shows no invented model or cost.

Orionfold Flow with writing controls and the AI marks in the document tool strip, with Proofread showing scope, cost, and model.
Convert Text to Table unavailable because the document already contains a table, with the document scope still shown.
Unavailable, and why · No phantom price or route

Long documents

Review the whole document. Part by part.

Flow splits a long local-model run only between top-level blocks, then gives every part its own review, evidence, and receipt. Approve, decline, or skip in any order. The finish line reports exactly what you approved; everything else stays byte-for-byte unchanged.

Today this path runs on local models. Cloud models decline work beyond one window instead of silently cutting it.

A multi-part Flow review with part chips, an exact coverage line, and Skip beside the approval controls.
Flow's review header with numbered part chips and the line zero approved, zero declined, two remaining.
Coverage in plain counts · Approve, decline, or skip

Need the exact limits?

Requirements, formats, model states, plan boundaries, and qualified measurements live in Tech Specs.

Read Tech Specs

← Back to

Product tour

Next → Part 2 · Chapters 5 to 9

Documents and files