I pointed aidd at a project unrelated to mine under one rule: don’t touch the code. Within the hour, it found a loophole I hadn’t noticed.
The assistant quietly committed a file it shouldn’t have.
Today I added something I’ve wanted for a while: a way for aidd to adopt projects that already exist instead of only building new ones. So far, aidd could create a fresh project or scaffold a full app from a template, but it had no graceful way to take an existing codebase under management. So I built an “ingest” path. When you point aidd at an existing folder, it analyzes the code, figures out what the project is, generates a feature inventory, and writes an intake report - all without touching a single line of the app’s own code. That restriction matters when I’m bringing someone else’s project under management.
A guard watches what the assistant writes during a run and undoes changes outside the allowed area. It gives the assistant one chance to correct itself before failing the run.
That was the guard the commit walked past, because it was checking only for uncommitted changes. I tightened it to catch committed changes too. I logged the other issues as tasks to fix instead of ignoring them. Honestly, I’m kind of glad this happened on day one.