I Built a Free Safety Scanner for Claude Code Setups — Here's Why I Had To

I can't write code. That's not a metaphor or false modesty. I'm a non-engineer who started using Claude Code about three months ago. I've shipped a game, published 30+ technical articles, and built a multi-agent system that keeps working while I sleep — and I haven't typed a single line of code myself. Which means I had a problem. When you can't read what's running, you can't tell if it's safe. The Incident That Started All This One afternoon I was watching Claude Code work through a refactoring task. It had been running autonomously for about 40 minutes. Then I saw it: rm -rf ./backup . The command ran. The backup directory was gone. It wasn't catastrophic — the files were recoverable from git. But I sat there realizing something uncomfortable: I had been running this system for weeks without ever thinking about what it was allowed to do. No dangerous command protection. No gate on external actions. No session checkpoint if things crashed. I'd set up a lot of things. But I had no idea