Tracy records supported changes made to your site in the Site changes tab: requests you make in the chat or in a comment, supported edits made in the CMS admin, and supported changes the site makes on its own. Each row says what changed, when, where it came from and who made it, when available. EmDash has no file history; its admin log covers pages and posts, not menus, settings or media.
Does Tracy ask before it changes my site?
Not for ordinary requests. Tracy makes the change and you review it afterwards, in Site changes and on the site itself. That is a deliberate choice: the value of Tracy is not a confirmation button, it is that every recorded change is visible and can be undone where supported. If you would like a plan before anything is touched, say so in your request, for example: “Tell me what you would change on the Services page before you change it.”
What does the Site changes tab show?
Open the Site changes tab of your site in Tracy. It lists every recorded change, newest first, in four columns:
- Description: what changed, for example an updated page or a number of changed files.
- Time: when it happened.
- Source: where the change came from.
- By: the person or system that made it.
Older changes load with Show more. Use the Source filter to see one kind of change at a time. Backups you create appear in the same list, so you can read the history as known good points with the work in between.
What do the sources mean?
| Source | What it means |
|---|---|
| Chat | A request typed in the chat on this site |
| Comment | A comment on the page sent to Tracy with Ask Tracy to edit |
| CMS admin | An edit made in the WordPress, Joomla or EmDash admin, as reported by the CMS. By shows the CMS user when available. No before and after is kept. EmDash reports pages and posts, not menus, settings or media. |
| Automatic | Something the site did on its own, such as a scheduled task |
| Tracy update | Tracy updating its own connector or files on the site |
| Restore | An undo or a restore made from Site changes |
| Unknown | Files changed and the source could not be told |
How do I see exactly what changed?
Open a row from the chat or from a comment to see what Tracy did in that request:
- Files Tracy changed. On WordPress and Joomla, each available file opens in a Diff that shows the exact lines that moved. EmDash has no file history.
- Content Tracy wrote. Pages, posts and other content Tracy saved in the site’s database during that request.
From the same row, Open chat goes back to the conversation (for the person who typed the request), and Open comment goes to the comment on the page.
How do I undo one change?
- File changes on WordPress and Joomla. Open the row’s menu and choose “Undo file changes…” where available. Tracy asks you to confirm. Only eligible files that change touched go back; later changes to those files can block Undo. Database content is not restored, and the undo itself appears in Site changes with the source Restore.
- Content Tracy wrote. Undo from Site changes is not available for content yet. Choose “Ask Tracy to revert” on the row instead: Tracy receives the request in the chat you have open on that site, with the details of the change attached. Open a chat on the site first. On WordPress and Joomla, Tracy keeps a record of the content it writes to help it revert that change; later edits can block Undo. On EmDash, request Undo is unavailable; ask Tracy to change the content back.
- Many changes at once. Restore a backup instead. See Undo and backups.
What about EmDash sites?
Tracy does not keep a file history for EmDash sites. Changes to the site’s code and uploaded files do not appear in Site changes and cannot be undone there. Content Tracy writes still appears. In the EmDash admin, edits to pages and posts are tracked; menus, settings and media are not recorded by EmDash.
How should I review an AI edit?
- Read the rows from your request and check that each one matches what you asked for.
- Open the Diff for file changes, and check the page itself.
- Before the next large change, create a backup with a clear title. Tracy drafts the backup notes from the changes since the previous backup; edit them freely.
What Site changes does not show
- A before and after for admin edits. Edits made in the CMS admin are listed with who made them, but no before and after is kept.
- File history on EmDash, as explained above.
- A guarantee. Seeing a change makes it easier to catch a mistake. It does not make mistakes impossible, which is why undo and backups exist.
Frequently asked questions
Does every text edit appear in Site changes?Text Tracy writes appears under the request that wrote it, as Content Tracy wrote. Edits made in the WordPress, Joomla or EmDash admin appear with the source CMS admin, without a before and after. On EmDash, only edits to pages and posts are recorded.
Can I see changes made in the WordPress or Joomla admin?Yes. They are listed with the source CMS admin, and By shows the admin user who made them.
Can I use Site changes for a client report?Yes. Filter by source to show the work for a client, and when you create a backup, Tracy drafts notes from the changes since the previous backup. You can edit the notes.
Can I undo a text change Tracy made?Choose Ask Tracy to revert on that row. On WordPress and Joomla, Tracy can use its record to help revert that change; later edits can prevent an exact reversal. To put the site back to an earlier point, restore a backup within its supported scope. EmDash backups restore database and media, not template code.