AI coding loops can copy the worst habits in old code

r/ClaudeAIJun 10, 2026 · 3d ago

like Claude can move very fast when they run in , but they may also copy bad habits from an existing codebase. In one real project, an agent loop was used on a client’s core product and delivered four features in one week. The looked clean, automated checks passed, and the team was pleased at first.

later found that all four features used an old pattern the team had been trying to remove for two years. That old pattern appeared in more than 40 files, while the newer pattern appeared in only about 6. The AI followed what it saw most often, not what the team intended.

On a new project, instructions can guide the AI more clearly, but on an old project, the code itself becomes the strongest instruction. The result can be working features that look successful while quietly adding back the the team was trying to reduce.

Radar's take

This is directly useful for using Claude Code, Codex, Cursor, or similar tools on real products. AI can help ship faster, but speed becomes risky when the project already contains old shortcuts, half-finished migrations, or patterns you no longer trust.

The practical move is simple: before letting an agent loop work across a repo, write down what it must avoid and show it the newer files it should copy. For sensitive areas like login, payments, security, and data handling, do not rely only on passing tests or a clean-looking diff.

Key points

can speed up feature work, but they can also repeat old coding habits.
AI tends to copy the patterns that appear most often in the codebase.
An old pattern in 40-plus files can outweigh a newer pattern in only a few files.
Working code and passing automated checks do not prove the AI followed the right design direction.
Before using AI on an old project, document which patterns to avoid and which files are good examples.

Read original ↗