What they did
A Redditor in r/ClaudeCode saw their Mac had 25 GB free out of 228 and asked Claude Code to find out what was using the space. Earlier sessions had Claude check its own UI work by taking screenshots, and the capture script started Chrome with a fresh temporary profile each time. A week later the disk filled again and the poster had it look a second time.
How it went
The first pass found 157 leftover Chrome profiles, about 8.7 GB, plus a headless Chrome that had run orphaned for 27 hours. The second pass found 439 copies of the Chrome app that macOS makes on each launch. du reported 907 GB, which the disk could not hold; the copies share blocks, so only about 2 GB was real. The poster then added rules: capture scripts keep profiles in one folder and remove them in a finally block, the agent kills any Chrome it started, and it moves files to the trash instead of deleting them.
Worth knowing
None of this showed in a diff or a test. Commenters suggested a SessionEnd hook to clean the temp folder, noting its default time budget is short, and pointed out that temp profiles live under /var/folders and count as System Data. Several warned against letting an agent delete files on its own; have it write a cleanup script you read first.