A rewrite can solve the wrong problem
When a document contains AI chat residue, the tempting move is to ask another AI tool to rewrite the whole chapter. Sometimes that helps. Often it creates a new draft with a different rhythm, different emphasis, and new details to verify.
If the real problem is role labels, Markdown clutter, filler phrases, repeated setup, or inconsistent spacing, a full rewrite may be more risk than repair.
Reviewable cleanup keeps the author in control
A reviewable cleanup workflow shows candidates before changing text. You can accept a removal, reject it, adjust the rule, or save the preset for the next chapter.
Awtter is designed around that review loop. The goal is not to replace the writer's voice. The goal is to remove non-document residue and make the draft easier to revise, organize, and export.
Snapshots make cleanup safer
Even controlled cleanup needs recovery. Before a batch cleanup, import overwrite, or structural change, create a snapshot or backup. That lets you restore the earlier version if a cleanup pass catches too much.
This is one reason cleanup belongs inside the document workspace. The same place that stores the chapter can store the snapshot, metadata, notes, and export status.
Use rewrites for prose problems, cleanup for residue
If a paragraph is unclear, underdeveloped, or factually wrong, it may need revision or rewriting. If it contains assistant chatter, pasted prompt text, duplicated headings, or formatting noise, it needs cleanup.
Separating those jobs helps authors move faster. Clean the residue first, then spend revision energy on the actual book.