Comparing AI Rewrites with the Original: Accept, Reject, Merge
Read added, deleted and modified blocks, accept or reject passage by passage, protect your own input, and catch five common mis-edits so you make the final call.
In this article 9 sections
The most dangerous moment in AI revision isn’t the model writing badly; it’s when you click overwrite without looking.
In a 2,000-character chapter, AI may fix three wordy spots, and may also casually change a character’s catchphrase, delete a piece of foreshadowing, or explain a deliberate blank in full. Choosing only “yes” or “no” for the whole chapter means accepting a pile of side effects for the sake of three good edits.
A steadier way is to split the rewrite into change blocks: for additions, check whether they truly add information; for deletions, check whether they wrongly harm clues; for replacements, check whether tone and facts have drifted. AI proposes the plan; the author signs off passage by passage.
What Do the Three Colors in the Diff Panel Mean?
The panel splits the original and the rewritten result by line into several change blocks, with the common types being added, deleted and modified.
- Added: AI put in content the original didn’t have.
- Deleted: content in the original was taken out of the new version.
- Modified: the expression at the same position was replaced.
When looking at “modified”, don’t just compare whether the words are prettier. Check at least three layers: whether the facts are the same, whether the character’s attitude is the same, and whether the narrative function is the same.
For example, the original is “She put the key back on the table”, rewritten as “She hesitated for a moment, then gently set the key, a symbol of freedom, back on the table”. The text is fuller, but hesitation and symbolic meaning have been added. If later text is going to reveal she had long made up her mind, this polish creates a contradiction.
What Happens When You Accept or Reject a Change Block?
Accepting means keeping AI’s new content in this block; the new text in the editor doesn’t change, and the block disappears from the pending list.
Rejecting means restoring this block to the original text while keeping the other changes already accepted. The system locates and replaces by block rather than reassembling the whole chapter, so content you added elsewhere won’t vanish wholesale because you rejected one block.
If you happen to keep writing by hand on the same line AI modified, the system may be unable to safely separate “AI’s rewrite” from “your new input”. In that case the panel aborts the current rejection, refreshes the comparison, and saves the canvas content into a local draft for protection. After you see the prompt, check again; don’t click repeatedly.
When Is “Accept All” or “Reject All” Appropriate?
The all-at-once actions suit only scenarios where the intent is very clear.
“Accept All” suits format cleanup, punctuation unification, and an explicitly requested switch in narrative person throughout, provided you have read through the result. “Reject All” suits cases where the model misunderstood the task, for example when you asked to trim and it continued with new plot instead.
For rewrites touching character tone, foreshadowing, timeline and settings, we suggest handling block by block. Spending ten more seconds on each block beats overwriting the whole chapter and then hunting for the old text in version history.
You can review in this order:
- Handle deleted blocks first, confirming no facts or foreshadowing were removed.
- Then look at added blocks and reject new settings with no basis.
- Finally look at expression replacements and check the characters’ voices.
- After processing, read through from the top once more to confirm the blocks connect naturally.
If I Watch the Diff While Writing by Hand, Will They Overwrite Each Other?
You can keep editing, but you should know the boundaries.
The diff panel reads the canvas’s live content. Your input that falls outside a change block should be kept when accepting or rejecting that block; when your input is mixed on the same line as the target block, the system prioritizes protecting recoverability rather than pretending it can separate them precisely.
A steadier practice: confirm block by block first, then do large stretches of handwriting. If you really have to edit while viewing, start a new line where possible and don’t keep writing in the middle of a highlighted change line. When a conflict prompt appears, first go to “Version History → Local Drafts” to confirm the protected content.
How Do “Content Preview and Merge” and Passage-by-Passage Diff Differ?
Passage-by-passage diff suits local rewrites of an existing chapter. Content Preview and Merge suits a complete generated result, for example when an agent generated a whole chapter and you must decide whether to create a new chapter or replace the target chapter.
The merge dialog shows the generated content and the current content side by side, with two tabs: content and summary. Replace mode uses the target chapter’s current version as the save baseline; if someone else or another task has already updated the chapter, the version guard prevents the old result from silently overwriting the new content.
You can set the decision standard like this:
- The new generated content is an alternative plan: create a new chapter and keep both versions to compare.
- You clearly want to rewrite the current chapter: choose Replace, but first look at the summary and the factual changes.
- You only want some passages from it: don’t merge the whole chapter; copy them into a local rewrite task or use passage-by-passage diff.
When Reviewing AI Revisions, What Problems Are Easiest to Miss?
The easiest to miss is “reads smoothly, but the facts have changed”.
We suggest checking five items every time:
| Check item | Typical mis-edit |
|---|---|
| Character stance | A cold character suddenly explains all their motives proactively |
| Time and place | Night polished into early morning, the journey shortened |
| Item state | A broken item works again |
| Information access | A character voices a secret they shouldn’t know |
| Foreshadowing blank | A hint explained outright, so the later twist fails |
After finishing a long novel’s revisions, you can also run the Whole-Book Consistency Check to see whether local polishing caused cross-chapter contradictions. If you worry about an AI tone, use the Submission Compliance Center to locate high-risk passages, and don’t wash the whole chapter’s style flat just to lower a score.
What Is a Steadier AI Revision Workflow?
Limit the task first, then generate, then confirm passage by passage, and finally recheck.
The instruction you give AI should state clearly what must not change. For example: “Only compress repeated explanation; keep the characters’ dialogue and the order of events unchanged; add no new settings; keep the last two sentences of the chapter as they are.” The clearer the no-change items, the fewer invalid blocks in the diff panel.
After receiving the result, scan the deleted blocks first, then accept passage by passage; after everything is handled, read through the context. Recheck structural changes with pacing analysis, and wrap up the text before publishing with the proofreading checklist.
Why Should a Rewrite That “Looks Better” Be Rejected?
The original reads: “Zhou Cen didn’t take the glass. He looked at the lipstick mark on the rim and asked where she had been last night.” AI changed it to: “Zhou Cen coldly refused the glass, his sharp gaze falling on the bright red lipstick mark on the rim, and demanded to know her whereabouts last night.”
The new version is smoother and fuller, yet commits three overreaches: it explains “didn’t take” as coldness, an ordinary observation as sharpness, and one question as an interrogation. If later text is going to reveal that Zhou Cen was actually worried about her, the relationship has been written dead too early.
In handling it, you can accept the fact-related clarification of “the lipstick mark on the rim” and reject the emotional characterization and the replacement with “demanded”. This is the value of the diff panel: not comparing which passage is more ornate, but separating expression optimization from plot judgment so you decide each.
If many such overreaches appear in one round of rewriting, don’t fix block by block only to find at the end that the whole direction was wrong. Reject everything, go back to the prompt and add “do not infer emotions and motives that aren’t written”, and regenerate, which is usually faster. Block-by-block review suits results that are mostly right with only a few local trade-offs.
Keep the original task and the failure reason before regenerating, so the next version can converge in a targeted way, rather than switching models and trying luck again.
FAQ
Q1: Does accepting one change block immediately overwrite the whole chapter?
No. Accepting a single block only confirms that local new content, and the other change blocks can still be decided separately. The final authority is what the editor currently shows; read through again after processing.
Q2: After rejecting a change, where did the text I just typed go?
Input outside the block should be kept. If your input and the target change line can’t be safely separated, the system protects the canvas into a local draft and asks you to choose again. You can retrieve it in the local drafts area of version history.
Q3: Can I still recover after Accept All?
You can check version history and local drafts, but don’t treat recoverability as a reason to skip review. Local drafts are unavailable across devices, and whether a version exists also depends on save state.
Q4: After the AI rewrite finishes, why does it still show the old text?
Chapter sync may not be complete, or there may be an update conflict. Don’t resubmit the rewrite; first refresh the current chapter or choose to load the latest as the page prompts. The system gives a protection prompt when local edits might be overwritten.
Q5: How do I get back text that was overwritten by mistake?
Stop editing first, open the Novel Text Versions and Local Draft Recovery Guide, and check in the order of server version history, local drafts and conflict prompts.