# A year after a 100% AI coding mandate: four versions of everything

<!--
title: "A year after a 100% AI coding mandate: four versions of everything · Cork"
description: "An engineer's account of a year of agent-only coding: about 3x the code, four versions of every helper, and the two reviewers gone. Why coding agents rewrite helpers that already exist, why review missed it, and what to do about it."
canonical: "https://corkcli.com/blog/ai-coding-mandate-four-versions-of-everything"
last_updated: "2026-11-16"
published: "2026-11-16"
author: "Kevin Vera"
-->

An engineer's account of a year of agent-only coding: about 3x the code, four versions of every helper, and the two reviewers gone. Why coding agents rewrite helpers that already exist, why review missed it, and what to do about it.

By Kevin Vera · November 16, 2026 · [News](https://corkcli.com/blog/c/news) · 5 min read

On 7 November 2026 an engineer posting as u/gato5fication on r/ClaudeCode described what a year of agent-only coding did to their team's codebase. The title was "A year after the 100% AI mandate nobody understands our code", and it spread from there to Hacker News. The company isn't named, and we can't verify the account: on Hacker News the top reply argued the post itself read as AI-written, and a Reddit commenter called it possible "generated bait". We think it is worth reading anyway, because the failure at its centre is mechanical, and anyone running several coding agents on one repository can check their own code for it.

## What the post says

It is short, and most of it is worth quoting:

- **The mandate.** "A year ago leadership told us everything goes through agents now. Hand written code needed a reason."
- **The good half.** "It felt great for about 6 months, we shipped more than we ever had."
- **A year on.** "Now the codebase is around 3x the size it was and nobody can explain how most of it works."
- **The duplicates.** "The agents struggle too, they keep re-implementing helpers that already exist somewhere else because there are 4 versions of everything."
- **The reviewers.** "The two people who used to read every PR and push back left in the spring, one quit, one was 'restructured'."
- **The review bot.** "coderabbit still comments on every PR, but there's nobody left who can tell if a comment matters or not, so people just resolve them all."
- **The walk-back.** This month management started "quietly asking us to 'write more of it ourselves' again." The cost: "I spent 2 days on something I would have done in an afternoon in 2024."

## Why agents write a fifth version of a helper

Each agent session starts from its own context. It knows the files it has read and nothing else. To reuse a helper it has to find it first, which means guessing what it is called and searching for that. If the date formatter it needs lives in `utils/dates.ts` as `fmtDate` and the agent searches for `formatDate`, writing a new one is the cheapest move it can see.

Parallel agents make this worse. Two agents that both need a date formatter in the same hour can't find each other's, because neither has committed yet. Both write one, both pass review, and the codebase now has two. (We cover the ways to stop that in [how to keep AI coding agents from duplicating each other's work](https://corkcli.com/blog/stop-ai-coding-agents-duplicating-work).)

Then duplication feeds itself, which is the post's own point: the agents re-implement helpers "because there are 4 versions of everything." Once a search returns four candidates that behave slightly differently, the agent can't tell which is the real one, and writing a fifth looks safer than picking wrong.

It costs tokens as well as understanding. Every duplicate is more code that each later agent reads past or searches through. One commenter predicted the project "will continue to get more and more bloated until the token cost per change is extortionate." Where those tokens go when several agents share a repo, and how to cut them, is in [how to reduce token usage when running several coding agents](https://corkcli.com/blog/reduce-token-usage-multiple-coding-agents).

## Why review didn't catch it

Each duplicate passes review on its own: the new helper is small, correct and tested. Seeing that it is the fourth one takes knowing the rest of the codebase, which is the knowledge that left with the two reviewers. An AI reviewer comments on the diff in front of it, and the post shows what happens when nobody can sort those comments: all of them get resolved, so none of them count. (More on [reviewing pull requests from several AI agents at once](https://corkcli.com/blog/review-pull-requests-from-multiple-ai-agents).)

## What to do about it

The thread had plenty of advice, some of it contradictory. These are the parts that hold up:

- **Make agents search before they write.** One commenter's fix was an instruction to "search for existing functionality before implementing a new function." Put it in `CLAUDE.md` or `AGENTS.md`, and name the shared modules so the search has somewhere to start. It only works when the search finds the helper.
- **Keep a person on anything structural.** New shared helpers, new modules and new dependencies are where duplicates are born. Route those to someone who knows the codebase, even when the rest of the review is automated.
- **Track what every agent is changing, not only what got merged.** Duplicates appear while two agents are working in parallel. By the time both are merged, they are both in.
- **Count "shipped" and "understood" separately.** PRs merged is one number. How much of the code someone on the team can explain is another, and it was the one this team stopped measuring.
- **Find the duplicates you already have.** Copy-paste detectors such as jscpd and PMD's CPD find blocks that were copied. Re-implementations that do the same job with different code need a review pass, and an agent can do that pass if you give it one family of helpers at a time and the tests to keep it honest. One commenter with a codebase of about 600,000 lines, 40 to 50% of it documentation, said "not even a single function is duplicated anymore."

## Where Cork fits

The part a prompt can't fix is the parallel one: an agent can't search for a helper that another agent wrote ten minutes ago and hasn't committed. That's the problem Cork works on. When an agent starts or gets a prompt, Cork briefs it on the exact signatures, callers and recent changes of the code it is about to touch, including what other agents on the repo just wrote, whichever tool they run in. A note anchored to code ("use `fmtDate` in `utils/dates.ts`; the others are on their way out") reaches the next agent that touches it. Cork doesn't remove the duplicates you already have, and it doesn't replace a reviewer who knows the codebase.

## Sources

Checked 16 November 2026:

- u/gato5fication, "A year after the 100% AI mandate nobody understands our code", r/ClaudeCode, 7 November 2026, and its comments: https://www.reddit.com/r/ClaudeCode/comments/1xq2n3t/a_year_after_the_100_ai_mandate_nobody/
- Hacker News discussion of the post: https://news.ycombinator.com/item?id=50433079

## Frequently asked questions

### Why do AI coding agents duplicate code?

Each agent works from its own context and only reuses a helper it can find. If its search misses the existing one, or another agent wrote it and hasn't committed, writing a new one is the easiest move. Once there are several versions, the agent can't tell which is canonical, so it adds another.

### Does an AI code reviewer catch duplicate helpers?

Not reliably. A reviewer looks at the diff, and a duplicate helper is usually small, correct and tested. Spotting that it already exists elsewhere takes knowledge of the whole codebase.

### How do you find duplicated helpers already in a codebase?

Copy-paste detectors such as jscpd and PMD's CPD find copied blocks. Helpers that do the same job with different code need a review pass, by a person or by an agent given one family of helpers at a time and the tests that cover them.

## Related reading

- [Cork vs Graphite: coordinating agents before the PR, or reviewing after it](https://corkcli.com/blog/cork-vs-graphite): Cork vs Graphite: Graphite stacks, reviews and merges pull requests; Cork keeps parallel AI coding agents from colliding before a PR ever exists.
- [Nvidia's CEO fight has a board, a petition and the White House. Your AI agents have nobody.](https://corkcli.com/blog/nvidia-ceo-oversight-ai-agents): Days after Jensen Huang resigned, his possible return is being argued by Nvidia's board, its investors, a petition, analysts and Washington. The AI agents running on Nvidia's chips get none of that oversight. What a board for your agents would look like.
- [Your AI agent has a wallet now](https://corkcli.com/blog/chatgpt-wallet-ai-agent-payments): How ChatGPT Wallet lets an agent pay: a card added once, Face ID or a fingerprint for every purchase, and a payment token so neither the agent nor the store sees your card. OpenAI's plan is agents that buy on their own within limits you set. What should those limits look like?
- [Agent collision: what it is when AI coding agents overwrite each other](https://corkcli.com/blog/agent-collision): An agent collision is when two AI coding agents change the same code, or code that depends on each other, without knowing, so one breaks or erases the other.

[All articles](https://corkcli.com/blog.md) · [Cork in Markdown](https://corkcli.com/index.md) · [llms.txt](https://corkcli.com/llms.txt)

This page in HTML: https://corkcli.com/blog/ai-coding-mandate-four-versions-of-everything
