How AI Assist Works
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
AI Assist connects FlowBoard to a language model that you choose. The model proposes text or changes, and you review each proposal before anything in your document changes. FlowBoard works fully without it.
AI Assist is not available on iPad and iPhone. To start, set up a connection.
The modes
Section titled “The modes”| Mode | Use it to | It can change | It can’t |
|---|---|---|---|
| Draft | Draft new scenes or beats as cards | Adds new cards where you started it | Change existing cards |
| Rewrite | Change the wording of a card, several cards or a selection | The text you rewrite | Add or change tags, dates or other metadata, or story structure |
| Edit | Have the model plan changes to cards and boards | The text, position and tags of the cards it’s allowed to change, copies of them, cues, placeholders and headings, splits into several cards, new cards, boards, columns and groups | Change cards it only reads, split story cards, or change the story tags of existing cards: scene IDs, connections, routes and presentation directives |
| Ask | Get answers about your story | Nothing. Ask is read-only | — |
| Story Map proposals | Continue a scene, bridge scenes, expand a scene into choices or repair Story Health, from Edit in Story Map | New scene cards, connections between scenes, and story tags | Change the text of existing cards. The model writes only the prose of a new scene, and FlowBoard adds its story tags |
Each mode has its own tab in the AI Assist panel, and each tab keeps its own request and result. Draft, rewrite and ask covers the panel, Draft, Rewrite, Ask and Story Map. Edit cards and structure covers Edit, and Example requests shows what to ask for in each mode.
Can change and Can read
Section titled “Can change and Can read”Every request keeps two things apart:
- Can change says what the request is allowed to modify. It follows from where you opened AI Assist and the Scope you choose, for example this card’s text, the selected text only, cards and structure in “Act 1”, or for Ask nothing.
- Can read lists the supporting information the model receives, one chip per item. A chip marked ✎ is also what can change; every other chip is only read.
Adding supporting context does not give AI permission to change that context. If you add All cards — full text to an Edit request about one card, the model can use every card to plan its change, but the plan can still only change that card and add new content created from it. Content that can change may be moved or copied to another column or board; that doesn’t make the cards already there changeable.
What the context chips send
Section titled “What the context chips send”| Chip | What the model receives |
|---|---|
| Document overview | Every board and column, and the first line of every card. Not the cards’ full text |
| All cards — full text | The full text of every card in the document. A model with a small context receives as many whole cards as fit, and AI Assist says so |
| Previous card in column, Next card in column | The card above or below in the same column. In a branching story, that isn’t necessarily the previous or next scene |
| Leads from …, Leads to … | A scene that can come directly before or after this one in the story, one chip for each. Branches are alternatives, not one history |
| Route: … — all beats | The full text of every scene on that route, including later ones |
| Character: … — identity only | The character’s name and ID, nothing more |
| Character sheet: … | The card that defines the character, for example in your Reference column |
| Story Health diagnostics | FlowBoard’s own Story Health findings for the cards you ask about. Offered in Ask when there are some |
| Rest of this card | When you rewrite selected text: the card around the selection. Only the selection is rewritten |
| Story organization: … | What acts, sequences, scenes and beats are in this document, as set in Story organization. Sent with every Draft, Edit and Ask request, and always included |
From Story Map, a request can also carry Reading path, Story Health diagnostics, Selected relationship, Route details or Reader order, named for what the map adds.
Some starters add the context they need. Their chips appear with a line saying what the starter added, and you can remove any that are optional before you send. Nothing is sent that AI Assist doesn’t show.
Context warnings
Section titled “Context warnings”When your instruction seems to need context that isn’t included, AI Assist says so, for example “Mara’s character sheet isn’t included.”, with a button such as Add character sheet. It also points out what AI Assist never sends: comments on cards, images, importance, due dates and tints. Warnings look for a few common phrasings only, so they don’t catch every request, and they never stop you from sending one.
You review every change first
Section titled “You review every change first”Nothing is applied until you choose to apply it:
- Draft: you see each proposed card and select Insert.
- Rewrite: you see a comparison of the old and new text and select Accept.
- Edit: you see the plan step by step and select Apply.
- Story Map: you check that you reviewed the changes, then select Apply reviewed changes.
A proposal you apply is one step that Cmd+Z undoes. If the document changes after you start a request, you can still read the result, but to apply changes, start a new request.
What FlowBoard checks before it applies a change
Section titled “What FlowBoard checks before it applies a change”Before a proposal can be applied, FlowBoard checks it against your document. When a check fails, the proposal or the step is blocked with the reason, and your document stays as it was.
- The card you review is the card FlowBoard stores. FlowBoard reads a proposed card the way it reads a card you type. If part of a tag or other metadata wouldn’t be stored as written, for example because a quote mark inside a quoted value isn’t escaped, the card is refused. Edit shows a new card the way FlowBoard will store it.
- Generated cards can’t carry a link ID. Links and embedded instances find a card by its
::id:mk-…, so a proposed card that brings one is refused. - A step changes only what its review shows. A tag step changes the tags and nothing else on the card: collapse state, importance, dates, tints and comments stay as they are. A step that would change more than its review shows is refused.
- The result must survive saving. FlowBoard checks what the change would look like after the document is saved and reopened. If anything would come back different, such as a name that the file would read differently, the change isn’t applied.
- The story must stay intact. A proposal that would break the story, for example by reusing a scene ID or deleting a scene that another scene follows, is blocked, and the review lists the problems.
These checks cover what FlowBoard can verify in the document. Whether the proposed text says what you want is for you to judge in the review.
What a request sends
Section titled “What a request sends”Your documents are files on your Mac, and FlowBoard works with them there. AI Assist is the one part of FlowBoard that sends your writing elsewhere, and only when you use it.
- When: FlowBoard contacts the model server when you test a connection or send a request. Before a request, it may also ask the provider how much text the model accepts and what it costs. While a background AI job runs, FlowBoard checks on it until the result is ready.
- What: your instruction, the context shown as chips under Can read, and your story style if you set one. The context depends on where you opened AI Assist, the Scope you choose and the context you add or leave out. Show context preview shows the text the model receives. Requests contain text only: images, PDFs and audio files aren’t sent.
- Where: to the model server of the connection you chose. A local server on your Mac, such as Ollama or LM Studio, keeps the request on your Mac. A cloud provider receives the request and handles it under its own terms.
- Nothing carries over. Each request stands on its own. The model doesn’t see your earlier requests or its earlier answers, so a follow-up question needs its context again.
FlowBoard keeps API keys in your Mac’s Keychain, never in the document. See Your API key.
What AI Assist can’t do yet
Section titled “What AI Assist can’t do yet”- Change the story structure of existing scenes: choice labels, conditions, music and background directives, and connections. Story Map’s proposals add new scenes and connections, and Draft can draft new scenes with conditions. Change existing ones yourself: see Build a branching story and Variables and conditions.
- See images, sprites or audio. The model receives file names, not the media.
- Read comments, importance, due dates or tints on your cards.
- Read or write your story translations (Settings → Story Translation).
- Know what happened in a Play Mode session. For a path through the story, follow it in Story Map’s Linear view and use Ask → Reading path.
- Arrange the Story Map layout.
- Rename or delete boards and columns. Edit can add them.
- Remember earlier requests. Each request stands on its own. The panel keeps earlier requests and their results for you to read, and Recent instructions can put something you wrote before back in the field, but the model sees none of it.
- Set up AI Assist connects FlowBoard to a model.
- Example requests shows what each mode is good for.