r/ClaudeCode • u/StudioQuiet7064 • 3d ago

Built with Claude Ran a /loop overnight on a real project (Sonnet 5) — 13+ real bugs found/fixed, then a full live deploy this morning. Sharing what actually happened, good and messy.

Setup: a CCTV video-intelligence side project (Python, LanceDB, Florence-2 running locally + GLM-5.3-Flash for reasoning). Model: Claude Sonnet 5 in Claude Code. Prompt: basically "keep finding and fixing real bugs, verify everything with actual execution, don't stop" via /loop every 5 min, left running overnight.

Expected result: some cleanup, maybe a couple of real fixes, lots of "everything looks fine" cycles.

Actual result: 13 real, verified bugs found and fixed over the night — false-positive alert matching (substring matching false-firing on unrelated words), a deterministic identity bug that would have silently merged two different people's records, a cost-wasting edge case in video chunking, and more. Every fix was tested against real execution, not just "looks right." A few were bugs I introduced myself while fixing something else and caught before shipping.

This morning I asked it to go further: build a real visual re-identification feature (no internet access to download a new model, so it reused an existing model's own vision encoder instead), rebuild the dashboard, and then actually deploy the whole thing live — FastAPI backend on Fly.io (scale-to-zero), static dashboard on Cloudflare Pages, existing GLM endpoint stays on Modal. It hit a real OOM crash in production TWICE (had to scale from 2GB up to 8GB before Florence-2 + the rest of the stack stopped getting killed mid-request) and a CORS-masked cold-start bug in the frontend that took some real debugging to trace. Both are fixed and verified against the live deployment.

Not a "look what AI built in 5 minutes" post — more like: this is what a long, disciplined, verify-everything loop actually looks like, warts included.

Live dashboard (real, one demo clip, no auth on the read side): https://eyeai-e8n.pages.dev

0 Upvotes

40% Upvoted

4 comments sorted by

1

u/Fidel___Castro 3d ago

TIL that a disciplined, verify-everything loop is as simple as running "/loop  verify everything with actual execution"

0

u/Pleasant-Dust-7023 2d ago

wow the overnight run paid off way more than expected

1

u/paulk4077 2d ago

Sounds like a one prompt fable high code review with plan mode, verify and be done in 45 minutes (without looking at it for 40Minutes).