PonoLens guide

How to check which files an AI coding agent changed

An AI agent can change many files quickly. Review those changes before you keep or share them.

Start with the prompt

Open Prompt History in PonoLens and choose the prompt you want to review. When the AI tool reported file activity, the details page connects that prompt to files it created, edited, or removed.

Check the Data Trail

The Data Trail shows the individual actions PonoLens observed. Open an item to see its full details, including a reported path and action when those were available.

  1. Find the prompt and note its time.
  2. Review the files listed under that prompt.
  3. Open related Data Trail items for more detail.
  4. Open the changed files in your editor and read the actual code.
  5. Run your normal tests before keeping the work.
A missing file is not proof that nothing changed. Some AI tools do not report every file action. PonoLens records reported evidence and does not use Git as the only source of file activity.

Look for unexpected changes

Pay extra attention to configuration files, environment files, dependency lists, deployment scripts, database migrations, and files outside the project folder. If a change is unclear, ask the agent to explain it, then verify the file yourself.

Read next

What to do after pasting an API key into an AI chat →