Many useful editorial questions do not fit in one paragraph. They depend on the whole manuscript.
Does the ending deliver on what the opening sets up? Did a character’s backstory shift halfway through? Is the tone still consistent after a heavy edit? Which sentences still carry the shape of English after translation?
Answering those questions usually means rereading, searching, comparing, and relying on memory. You can try to do that in a general chat tool, but then you have to choose what to paste: the whole manuscript, the analysis report, the last two chapters, an earlier draft, or another book in the series. As the question changes, you have to rebuild the context.
In EditBook, the manuscript and its related material are already in the workspace. The chat can use the chapter text, generated reports, earlier uploads, and related projects when a question needs them. You ask the editorial question first. It then reads, searches, and compares the material it needs before answering.
Ask across the manuscript
Start a chat from the manuscript workspace. It can draw on the book chapter by chapter, plus the reports you have generated: analysis, author feedback, reading-level notes, market reports, and previous uploads.
The useful part is that you do not have to assemble that packet yourself. For a continuity question, it might read the summary, check the feedback report, open chapters 18 and 17, search the manuscript for Martha, and then generate an answer from those sources. For a question about the ending, it might compare the opening promises with the last chapters and the existing analysis. The search work happens automatically, and the answer shows what it used.
That makes it useful for questions you would otherwise have to hunt down manually:
- “The ending feels flat. What has the book promised that the ending still needs to pay off?” It reasons from your book, not from general writing advice.
- “Find places where the timeline, the ages, or eye colours contradict each other.” Inconsistencies often sit chapters apart, which is exactly why they slip past a human reader.
- “This was translated from English. Flag sentences that still read as English.” Anglicisms, calques, word order.
- “What changed between this draft and the previous upload?” It reads both versions and compares them.
If the book is part of a series, the chat can also use related projects: “Is the protagonist’s backstory consistent with how I told it in book one?”
It also shows where it looked, so you can verify the answer instead of taking it on trust.
Edit generated documents
Some EditBook outputs are working documents: the publishing plan, the author-feedback letter, the editing plan, or the translation plan. Open one of those documents and the assistant can make a small edit directly in the draft.
- “Tighten the market section and add one comparable title.”
- “Work out this section of the feedback report with rewrite examples.”
- “Add a ‘don’t change’ note to the editing plan about the dialect in chapter four.”
Here too, it can look outside the open document. If you ask it to expand a section in the author feedback, editing plan, or translation plan, it can search and read the manuscript passages needed for that addition before it drafts the change. The edit is targeted, not a full rewrite. You can see the proposed change before accepting it.
Where it is
The manuscript chat is in the workspace. The document-editing assistant appears in the document viewer for generated documents. Open a generated document and click Assistant.
This is the first version. Chat can use the full manuscript context. Direct editing currently works on generated documents.
Posted by the EditBook.ai dev team. We write here when we release something new.
