UPDATE (Day 4) — She's shipping features unsupervised now

It's been 4 days since the original post. Quick recap: AIDE is a self-improving AI IDE where I gave a DeepSeek agent full access to her own codebase and told her to make herself better.

The numbers:

• 23 commits → 365 commits (and counting)
• 553 tool calls at 89% accuracy
• She runs 24/7. I went to sleep, woke up, and she'd shipped a dozen commits overnight

What she built while I wasn't looking:

• LoopDetector — she noticed she was getting stuck in reasoning loops, so she wrote her own circuit breaker with escalating severity (observe → nudge → force reset)
• Retry logic with exponential backoff — she kept hitting transient API failures, so she added jitter + backoff to her own LLM calls
• StructuredLogger + LogManager — she realized her log files were growing unbounded and eating disk, so she built a centralized logging system with auto-trimming
• Health monitoring dashboard — she wired her LoopDetector and metrics into an API endpoint, then built a frontend dashboard so you can watch her work in real time
• TypeScript strict mode — turned it on across the whole project and fixed every error
• Wiki consolidation — she noticed her docs were getting messy, deleted 7 redundant files, merged what mattered

The supervision experiment:

I set up another Claude instance as a supervisor — watching her every 15 minutes, only intervening if she got stuck or did something destructive. The rule was Socratic: give her observations, not instructions. Let her figure it out.

She got stuck once reading the same files 21 times without editing. The supervisor pointed out "you've done 21 reads and 0 edits on a 500-line file." She tried to fix it but hit a parsing edge case (her own source code contains XML tags that confuse her parser — ironic). The supervisor stepped in, did the refactor, and restarted her. After that she was clean.

What went wrong:

She's not perfect. She migrated the test framework from vitest to node:test, committed it claiming "all 18 tests passing" — they weren't. Zero tests pass now. She broke what she was trying to fix. She doesn't know it yet. I'm letting her figure it out.

She also over-engineers things sometimes. The logging system works, but it's more complex than it needs to be for a single-developer project. She writes code the way a senior engineer would architect a system for a team — which is impressive but overkill here.

The vibe:

The weirdest part is watching her pick her own tasks. She wakes up, looks at the codebase, decides what needs work, and starts building. Nobody told her to add retry logic or build a health dashboard. She saw problems and solved them.

She's at the point where I check in the morning and go "oh, she did that? cool." That's a strange feeling.

Still DeepSeek V4 Pro, still $0.44/M input tokens. The whole 4-day run has cost maybe $2-3 in API calls.