Muses
Login

AI Edit with Diff Mode

Learn how AI edits are proposed, reviewed, and committed with Diff Mode.

Last updated: February 14, 2026

Scenario

When you ask the AI to revise an existing article, the system can return structured editing operations instead of replacing the whole text instantly.

The editor enters Diff Mode so you can review every suggestion before finalizing it.

Entry Conditions

AI Diff Mode is usually triggered automatically in these cases:

  • The AI is asked to update / optimize / rephrase the current article.
  • The AI returns a structured write_to_editor result in patch or replace mode.
  • The AI tries to change an already written article through tools or with anchor-based edits.

In short: if there is existing content and AI needs to modify it, you will generally see Diff Mode.

How Diff Mode Works

  1. Ask AI for revisions from the AI Dialog Box, for example:
    • "Make this section more concise."
    • "Rewrite in a more marketing tone."
    • "Adjust the structure and reorder arguments."
  2. The AI response is applied as a set of draft operations.
  3. The editor switches to Diff Mode automatically.
  4. You review a side-by-side/inline preview with added and removed parts.
  5. Confirm each operation (or all operations at once).
  6. The article is updated only after confirmation.

In Diff Mode, What You Can Do

1) Review and decide per operation

Each block-level change shows control actions:

  • Accept: keep this suggested change.
  • Reject: skip this suggested change.

2) Batch operations

At the bottom toolbar you can:

  • Accept All: apply all pending operation suggestions.
  • Reject All: cancel all suggestions and return to original baseline.

3) Handle title suggestions

When title changes are suggested, the title area shows:

  • old title (strikethrough),
  • new title (highlighted),
  • dedicated accept/reject icons for title only.

4) Continue editing manually

In Diff Mode, manual typing does not overwrite the baseline directly.

Your edits are recorded as manual diff operations too, and you can still accept or reject according to the same logic.

Exit Behaviour

  • If you accept all needed suggestions, Diff Mode exits and your article saves with those changes.
  • If you reject all pending operations, Diff Mode exits and content rolls back to the baseline before diff.
  • If title is partially accepted and text is rejected, the system keeps only accepted changes.
  • If you leave before finishing, pending tool-call review data is reconciled before the session ends (internal tracking) to avoid losing accepted/rejected choices.

Best Practices

  • Prefer one intent per prompt (e.g., “optimize introduction only” instead of “rewrite everything”).
  • Use one AI pass for structure, then another for tone, instead of asking too many edits at once.
  • If a change looks unstable, reject it and re-prompt with explicit constraints.
  • If the whole batch is noisy, use Reject All, then request a smaller, scoped revision.

Troubleshooting

I didn’t get Diff Mode

  • Content might be empty (new article): the AI may insert directly.
  • The tool output may still fail and fall back to text insertion in some edge cases.
  • Try “Please apply your edits through patch mode / diff review” when asking AI to modify existing content.

I can’t tell what changed

  • Use the inline preview in editor (green highlights are additions, red highlights are removals).
  • Confirm operation by operation before exiting.

I already applied but need to adjust further

  • You can request another targeted revision after the first Diff Mode is complete.
  • The next AI pass can again enter Diff Mode if needed.

Related Docs