When Your Agent Can't Find the Code It Wrote Two Weeks Ago: 3 Months of Agent-Driven Development
Sweaty-Landscape-561 · reddit · 2026-09-06
A developer recounts building a booking product almost entirely with AI agents since May with a team of three:
- Month one was unreal — whole features in an afternoon. Month two was fine. Month three fell apart.
- The turning point: asked to change cancellation refund logic, the agent spent 20 minutes searching for code it had itself written two weeks earlier — and found three different versions in three folders, picking the wrong one. Nobody on the team knew which version production used, because no human had read them.
- The fix: they bolted CodeRabbit onto the repo; the first review pass returned 200+ comments. Mostly nits, but the number was the honest cost of three months of unread code.
- Takeaway: they're slower now than in month one, and the author believes that's the correct speed — month-one speed was borrowed.
A vivid case study of codebase rot under fully agent-driven development.
More from coding & agent
- Ghost agent ran all night, cut per-turn cost from 20¢ to 4¢ with zero chatter — BLUECOW009 · 2026-09-07
- Astra + Blender + Dreamina Seedance 2.5 form a working AI video pipeline — eyishazyer · 2026-09-07
- One prompt runs a full 3D character pipeline in 30 minutes with GPT-6 Astra — _AustinCalvert_ · 2026-09-07
- Spotify engineer's Claude Code hook cuts token spend 90% by rerouting big file reads to Gemini — RexDouglass · 2026-09-07
- Bezalel launches: one MCP URL gives every agent memory, email, money and a computer — Rasmic · 2026-09-07
- Grok Coding Tip: Sending Repos to Cloud Agent Instead of Local Bot Saves the Weekly Quota — nikvassev · 2026-09-06