The person behind CapyWatcher.

I’m a real person and a developer who works alone. I’ve spent the last 13 years building WordPress and WooCommerce sites, most of it on performance optimization: hunting caching bottlenecks and taking milliseconds off page load times. Along the way I’ve also run web servers and worked in technical SEO, affiliate marketing and paid ads.

In early 2025 I started building with AI agents, and it changed how I work. I’ve built web apps with React, Tailwind CSS and Supabase, run them on Cloudflare Workers and Tunnels, and made a roguelike card game in React, inspired by Slay the Spire, where AI agents write new content and encounters as you play. I ship something almost every day now.

Away from the screen, I’m out in nature, deep in a PC game, or playing progressive metal to stay in a flow state.

Why I built CapyWatcher

I build with AI agents on my Windows computer a lot, and now and then they put files in the wrong place. One joins a whole folder path into a single folder name. Another writes to C:\tmp instead of the project’s own .\tmp\. Windows doesn’t say which program created a file, so finding the cause meant guessing.

So I built the tool I wanted. Right-click a new file, and CapyWatcher shows which program created it and which AI agent started that program. Or start from the program, and its history lists every file it created.

It works the way I want my own tools to work. It watches only the folders you choose, and the history stays on your computer. Only two checks go online, the update check and the license check, and there’s no account, no email, no ads and no analytics.

I build it the way I build everything now. I decide what it does, AI agents write most of the code, and I test every change before it ships. The content disclosure explains how.

CapyWatcher is a paid app, because that’s how I keep working on it without ads or selling data. You can try it for 7 days first, with no email and no account. The first release is in the works.

See pricing and the free trial