← Broadcasts

How I run parallel AI agents on a 559k-line repo without it rotting

July 9, 2026

MastodonView live ↗

Everyone predicts the same three deaths for a repo run this way: slop, rot, and merge hell. One Next.js codebase, half a million lines, several Claude Code sessions a day, around 65 PRs a week. It's alive anyway. The trick isn't smarter prompts. It's treating the agents like a team that will absolutely cut corners unless the repo makes cutting corners hard: guardrails that fail loudly, small PRs, checks that run before I ever look. https://www.jakelawrence.xyz/blog/parallel-agents-without-rot

♥ 0 ↻ 0 💬 0
Bluesky · thread (2)View live ↗

65 PRs a week from parallel AI agents on a 559k-line repo. The usual prediction is slop, rot, and merge hell. The thing that keeps it alive isn't better prompts. It's a repo built to make corner-cutting fail loudly and early.

How I actually run it: https://www.jakelawrence.xyz/blog/parallel-agents-without-rot

♥ 0 ↻ 0 💬 1
Threads

Half a million lines, one Next.js repo, several Claude Code sessions a day, roughly 65 PRs a week. Everyone tells me it should have collapsed into slop by now. It hasn't, because the agents get treated like a team that will cut every corner it can. The guardrails do the disagreeing so I don't have to review every diff by hand. Write-up: https://www.jakelawrence.xyz/blog/parallel-agents-without-rot

NostrView live ↗

One Next.js repo, 559k lines, several Claude Code sessions a day, around 65 PRs a week. The standard forecast is three deaths: slop, rot, and merge hell. The repo is alive anyway. Not because the prompts got clever, but because the codebase assumes every agent will take the shortcut if it can. Small PRs. Checks that fail loudly before I look. Guardrails that catch the drift instead of me catching it in review. Full write-up: https://www.jakelawrence.xyz/blog/parallel-agents-without-rot

♥ 0 ↻ 0 💬 0
X · thread (2)

559k lines, several Claude Code sessions a day, ~65 PRs a week. Everyone predicts slop, rot, and merge hell. What actually keeps it alive: a repo built to make corner-cutting fail loudly, so the checks catch drift before I do.

The full write-up: https://www.jakelawrence.xyz/blog/parallel-agents-without-rot

Farcaster

~65 PRs a week from parallel AI agents on a 559k-line repo. The obvious bet is that it rots. It doesn't, because the guardrails assume every agent will cut a corner and fail loudly when one tries. https://www.jakelawrence.xyz/blog/parallel-agents-without-rot

Sourced from How I run parallel AI agents on a 559k-line repo without it rotting.