Something on a post reads differently than you remember, and you want to know what changed and when. WordPress keeps every save, but the revisions screen shows you two columns of highlighted text and leaves you to squint at the differences. What you actually want is a plain answer: what moved between then and now.
This reads the history and hands you that answer, and it cannot alter either version.
Show me what changed on [the "Refund policy" page] since an earlier version.First, list its revisions newest first, with who saved each one and the date,so I can pick the version to compare against. This is read only, changenothing.
Once I pick an earlier revision, read it and compare it against the currentpage. Tell me in plain terms what is different: what was added, what wasremoved, and any lines that were rewritten. Do not restore or edit anything;I only want to understand the change for now.Why this is safe to run
Both abilities behind this prompt are reads. Listing the revisions returns metadata only, and reading one pulls its body just so the agent can diff it against the current post. Neither call writes, so the live post and the old revision both stay exactly as they are.
Restoring is deliberately not part of this. It is a separate write ability with its own approval step, so comparing never risks flipping the post back by accident. You look first, understand the change, and only reach for a restore as a distinct, intentional move. The revision reads stay off until you enable them, and every call is checked against your edit access to the post.
Already connected? Skip the paste. Ask your agent for the “compare a post to an earlier revision” recipe, or just name the post and tell it to show you what changed, and it runs the same read-only comparison on your own site.