How to see exactly what ChatGPT Work changed in a folder

Why the chat summary isn’t a file history

When ChatGPT Work finishes a task, it tells you what it did: “I renamed the invoices, merged the two spreadsheets, and deleted the duplicates.” That summary is genuinely useful, but it is a description of what the tool intended to do - not an independent, verifiable record of what actually happened to every file on disk.

The gap matters more than it sounds. A summary can quietly leave things out: a file that got touched as a side effect, a rename that collided with an existing name, a folder that ended up emptier than the wording implied. It also can’t show you the content of a change - which exact numbers moved in a spreadsheet, which paragraph was rewritten, which rows disappeared. To answer “what actually changed here?” with confidence, you need something that watched the folder, not just the conversation.

That is the whole idea behind a folder timeline. CoworkRestore saves quiet, read-only versions of the folder as changes settle. Comparing two of those versions tells you what actually changed between them - regardless of how the task was described afterward.

Open the CoworkRestore timeline

Everything below assumes CoworkRestore was already watching the folder when ChatGPT Work ran. If it wasn’t, there’s no captured history to open - CoworkRestore can only show what it recorded, never reconstruct the past. Skip to how to undo ChatGPT Work file changes for what’s still possible in that case.

1. Open CoworkRestore from the menu bar. Click the CoworkRestore icon in your Mac’s menu bar. The folders you’ve added show up in the list.
2. Pick the folder ChatGPT Work was editing. You’ll see its timeline of saved versions, with the most recent at the top.
3. Find the versions from around the session. Match the timestamps to when ChatGPT Work ran. When you use automatic folder watching, CoworkRestore saves versions as edits settle, so you’re looking for the rows whose times line up with the task.
4. Open a version to see the list of changed files. You’ll get every file that was added, modified, or deleted between that version and the one before it - just the file names and what happened to each. No wall of code, no guessing.

Additions, modifications, and deletions (how each appears)

Open a version and the changed-files list sorts everything into three plain categories. Each one answers a different question you might have walked in with.

• Added. A file that exists now but didn’t before. This is where those “three new files I didn’t ask for” show up - a report ChatGPT Work generated, a new copy of a spreadsheet, a folder it created to sort things into.
• Modified. A file that already existed and whose contents changed. This is the most common and the easiest to miss by eye, because the file name is identical - only the inside is different.
• Deleted. A file that was there before and is gone now. Seeing a deletion listed here is often the first solid confirmation that something you expected to keep actually went away.

A reorganize task can produce all three at once: a rename usually reads as one file deleted and one added rather than a single “renamed” entry, because on disk that’s exactly what happened. If the list looks busier than the chat summary suggested, that mismatch is the point - it’s showing you the real shape of the change.

Comparing text files (see the lines that came and went)

For plain-text files - notes, Markdown, CSV exports, code, plain.txt - click a modified file to see the version from the saved timeline next to the version on disk now. CoworkRestore highlights what actually differs: the lines that were added and the lines that were removed, side by side.

This is where the “summary vs. reality” distinction pays off. Instead of trusting “I tidied up the notes,” you can read the specific lines that changed and decide, line by line, whether each edit was what you wanted. Reading is free - nothing on disk moves while you browse.

Comparing Office documents, PDFs, and images (open the previous version alongside the current one in their usual Mac app)

Word documents, Excel and Numbers spreadsheets, PowerPoint and Keynote decks, PDFs, and images aren’t plain text, so a line-by-line highlight doesn’t make sense for them. The honest way to compare these is visual: open the previous version and the current version side by side in the app you’d normally use, and look.

From a saved version in CoworkRestore, you can open or save out the earlier copy of one of these files and let it launch in its usual Mac app - the earlier .xlsx in Excel, the earlier PDF in Preview. Put it next to the current file on disk and the difference is right there: the row that moved, the chart that changed, the page that disappeared. It takes one more step than a text comparison, but it keeps you honest for exactly the documents where a wrong change is easiest to overlook.

Review before you restore anything

The reason to look first is that seeing what changed is usually enough to settle the question - and it lets you decide from facts instead of from a summary. Once you’ve read the changes, you have three honest options:

• Keep everything. Close CoworkRestore. Nothing you did while browsing changed a single file.
• Undo specific files. If a handful of changes are wrong but the rest are fine, walk through how to undo ChatGPT Work file changes. That’s the guide for keeping the good edits and rolling back the rest, one file at a time.
• Undo a cleanup that went the wrong way. If what you’re looking at is a reorganize-and-rename pass that went sideways - files moved into the wrong folders, names that don’t make sense - the playbook is a little different. Jump to ChatGPT Work organized my folder incorrectly.

The point of reviewing first is that you never have to commit to a recovery plan before you understand what happened. Read the change. Then decide.