In the **Text** tab of the AI Generation window (`Cmd+Shift+G`), ask the AI to build your story, not to tell it to you. It works in the graph you have in front of you: blocks appear and wire themselves together while it answers. --- [â–ļī¸ Video: the AI assistant that builds the graph](https://celestory-docs-videos.netlify.app/en/panorama-ia/assistant-ia-qui-construit-le-graphe.html) ## ⚠ī¸ The Model You Pick Must Be Able to Use Tools Not all of them can. When yours cannot, a banner warns you: it cannot touch the graph and will just answer in the conversation. đŸ”ē Switch model before sending your request. --- ## 🧱 Building the Story - **Adding, removing and renaming blocks**, within the limits of your subscription. - **Connecting two points**, flow (`in` / `out`) as well as values, and **disconnecting** them. - **Writing the content of an input**: the text of a **Narrator** or an **Alert**, a number. - **Setting the options of a Choice block**: each one becomes an output, wired up in the same move. - **Creating, renaming and removing characters**, then **writing the lines** of a **Dialogue** or **Choice with dialogue** block. A line with no character becomes narration. - **Creating, renaming and removing variables** (Text, Number, Boolean, Date, Single select, Multiple select) and **pointing an input at one**, so the story remembers. For a Single select or Multiple select, it supplies the list of options at the same time, and can set the variable's starting value. - **Writing the page of an HTML5 block** (mini-game, form, simulation), if your plan allows it. - **Configuring an integration block**: on a **Baserow** block, it offers the databases, then the tables, and wires the block to the one you name. ## 🗂ī¸ Organising and Navigating - **Moving a block**, **grouping blocks** into a named group, editing or removing that group (the blocks stay). - **Showing a block**: it centres and selects it to point it out to you. - **Listing the project's graphs**, working on a different one, or **creating a module** with its graph and its start block. - **Reading back** the graph and the content of an input, then **checking the project**: what would stop the story from running, outputs that lead nowhere, inputs that read nothing, HTML5 pages with no way out. - **Saving the project** to the server. Before that, its work only lives in your browser. - **Publishing the project**, with your approval each time (see below). đŸ”ē It cannot create a connection the editor would refuse: the same checks apply to it. --- ## 🚀 Publishing Your Project Ask it to publish, and it does what the "Publish my project" window would do, without you leaving the conversation. It starts by checking which formats your account can use and what each one needs (title, app name, icon...), then it **checks the project**: if it has errors that would stop it from running, it explains them and does not publish. **Nothing is published without your confirmation.** - **In the Creator chat**, a panel appears above the input area with a summary: format, version, title, app name, start module or menu, link protection (without the password), whether the "Made with Celestory" badge is left out, and whether the link arrives by email. The message says: "Nothing is published unless you click Publish." Two buttons: **Publish** or **Cancel**. A refusal is final for that turn, and with no answer after 5 minutes it counts as refused. - **Through an MCP client** (Claude Desktop, for example), the confirmation is your client's own. Beware: a client set to allow everything will not ask you anything. The formats the assistant can publish are those of the "Publish my project" window that are built without going through the team: **Direct link**, **PWA**, **Web**, **Windows**, **MacOS** and **Linux**. It is still bound by your subscription: Direct link is open to everyone, PWA, Web and desktop apps need a Pro subscription, and protecting the link with a password needs a Business subscription. The other formats in the window (Steam, app stores, SCORM, VR) are prepared **on request** by the Celestory team: the assistant tells you so, it does not publish them. It then gives you the link (Direct link) or tells you the download link is coming by email (the other formats), with the published version. It can also check later on a publication in progress, the online link and the version number. đŸ”ē To protect a direct link, the link must already exist: the assistant refuses to ask for protection on the first publication, so that a link you believe is protected is never put online in the clear. Only give it a password you chose for this: it travels through the conversation. đŸ”ē It runs one publication at a time, and tries at most three publications per turn. --- ## 🔎 Everything It Does Is Shown Every action is written on a line in the conversation, in plain English: "Adding the character Alex", "Setting 3 choices", "Saving the project". Unfold it for the detail; a failure shows in the error colour. This is deliberate: you must be able to read what was done. --- ## ✍ī¸ An Example Request > Create the beginning of my story: the hero arrives in front of a locked door, Nora speaks to him, then a three-way choice: knock, pick the lock, walk away. Each branch leads to a short scene. Put the whole thing in a group called "Prologue". No need to specify the graph: it is the one that is open. --- ## ↩ī¸ Undoing a Whole Turn Under the message that started the work, an **Undo this turn** button puts the project back as it was before: the unit being undone is the complete turn, not each individual change. **Redo this turn** puts it back as the assistant left it. đŸ”ē That restore **also overwrites whatever you changed by hand since** that message, and empties your usual undo history: your earlier steps are gone. --- ## 🚧 Known Limits - **Layout stays imperfect.** It is supposed to lay its graph out from left to right, but nothing guarantees it: blocks can overlap. Ask it to move them. - **Progress during the turn.** Blocks appear in the graph before the conversation comments on them: do not conclude too early that nothing is happening. - **It does not know the text already written.** It knows which blocks exist, not what they contain: it reads an input back before changing it, and a rewrite replaces the entire content. - **Turns are bounded.** After twelve rounds of tool calls, it stops; what it has built stays in the graph. - **Characters have no image**: a name, a biography, nothing more. - **The options of a Single select or Multiple select variable cannot be changed from the conversation** once the variable exists: give it the full list in the request, or change them by hand. - **Publishing does not cover every format**: see the "Publishing Your Project" section. --- *Available from Creator version 6.1.* *Documented version: v2* --- → Next step: read the **Choice** block page again, then ask the assistant to complete a branch you left open.