Your AI agent worked for an hour. Its chat shows the files it edited, and git status shows what changed in the project. Neither shows the log a command wrote to C:\tmp, the cache a build left in your user folder, or the test file a script dropped next to the project.
An AI agent, such as Claude Code, Codex or Cursor, writes many of its files through the programs it runs: a shell, node.exe, python.exe, a build tool. CapyWatcher records each new file with the program that wrote it and the program that started that one, so History can list a whole session.
See every file the session made
- Before the session, open CapyWatcher and select Tracked folders in the left column. Check the project folder and the places the agent writes to outside it, such as
C:\tmpand your user folder, as Choosing folders to track shows. - Let the agent work.
- Select History in the left column.
- In the search field, type the agent’s program name, such as
claude.exe. The list keeps the files the agent wrote itself and the files of every program it started, since the search looks in the Process and Started by columns too. - In the Time range list, choose the range that covers the session, such as Last 24 hours.
- Read the list. File gives each file’s full path, and Process names the program that wrote it.
- Select Export CSV to save the list for later, or to compare two sessions.
Filtering the list explains the search and the lists, and Exporting history the file you get.
Find the agent’s program name
The name to search for is the agent’s process, the name of its program file while it runs. If you don’t know it, right-click a file you know the agent made and select CapyWatcher: who created this file?. The answer’s Started by line names the agent, as Who created this file? shows. The search also finds paths that hold the name, such as the agent’s own .claude folder, which is usually what you want too.
Only the programs it ran
To leave out the files the agent wrote with its own tools, clear the search and choose the agent in the Parent process list instead. The list then keeps only the files made by programs it started, such as a build or a test run.
Choose what to track
Your user folder holds AppData, where programs write all the time, and a project holds folders that build tools fill with thousands of files, such as node_modules or target. Uncheck those in Tracked folders to keep History readable, or hide a program that floods the list.
Important
History lists new files, not changes inside files: for edits to the project’s files, use git diff. A file the agent made and removed again shows as a muted row. The app records only the folders you track, from the moment you track them, while monitoring is on. After the free trial, without a license, the Process and Started by columns read “Shows with a license” until you enter a license key.