Iliad does not write with an agent of its own. When Claude Code, Codex, or any other tool edits the Markdown files in your open folder, Iliad shows what changed inside the document, and you decide what stays.
What It Does
- Compares each document with the version you last kept in this session and shows every changed chunk in place, with the previous text and the new text.
- Lets you Keep or Restore each chunk, or use Keep all / Restore all for the whole file from the toolbar above the document.
- Marks changed documents in the file tree with a count, so you can see which files an agent touched.
- Handles whole files too. A file created outside Iliad offers Keep file or Move to Trash, and a file deleted outside offers Confirm deletion or Restore file.
How To Use It
- Open your folder in Iliad and leave it open while your agent works.
- When a document changes on disk, open it (or let the agent run
iliad open, see Working With Claude Code). - Read each chunk. Choose Keep to accept it or Restore to put the previous text back.
- Use the arrows in the toolbar to move between changes, or Keep all / Restore all to finish the file at once.
After Keep or Restore, focus moves to the next chunk's Keep button.
What To Expect
Keep changes nothing on disk. The agent's text is already there, and Iliad just stops showing it as pending. Restore writes the previous text back for that chunk only.
Keep and Restore are buttons only. Tab and Esc never act on outside chunks, so nothing on disk changes by accident. (Tab and Esc still accept and reject your own ✦ AI results.)
Restores are guarded. If the file changed again since you looked, Iliad refreshes the review instead of writing, and never overwrites newer work.
If you were typing in a document when an outside tool changed it, Iliad shows a conflict banner so you can keep the outside changes, restore your version, or reload from disk. Your unsaved text is never silently replaced.
Changes to a document's comments file (name.comments.md) are not reviewed, so an agent can remove a handled comment without asking. The document text it changed is always reviewed.
Limits
- Review compares against what you last kept in the current session. After quitting Iliad, the review starts again from what is on disk.
- Created and deleted files are reviewed as whole files, not chunk by chunk.
- Whitespace-only changes show up as their own chunks. Ask agents not to reflow text they were not asked to change.
- Iliad does not record which tool made a change.
This page is generated from ai-review-workflow.md, which you can also read as Markdown.