I don't use a project management tool anymore. Just GitHub.
I set the direction, test the flows myself, and log every bug as an issue. Then I give one prompt to my lead agent: "go through all the bugs and fix them." It spins up a sub-agent per issue, each in its own worktree. Twenty issues in, and in under an hour I have twenty PRs pointing at my base branch.
That part feels like magic.
Then the merging starts
Merge three PRs and the fourth has conflicts. Fix those, and the sixth breaks. Features are worse than bugs, because they touch more files. Every merge waits on CI. The writing took an hour. The merging takes the rest of the day.
It's not just me
Anthropic shared that merges into their monorepo went from about 2,500 a day in May to over 30,000 in September. Their tooling couldn't keep up, so they built their own source control system, Scion. Their words: writing code isn't the bottleneck anymore. Managing it after it's written is.
To be fair, Scion is internal only, and Anthropic says Git is still fine for most teams. Most of us aren't merging 30,000 changes a day.
The flow needs a rethink
The flow we use was built for humans opening a few PRs a day. Agents open twenty in an hour. Stacked PRs help a bit, but merging, conflicts and CI all need a rethink.
The bottleneck moved. The tools haven't caught up yet.
Top comments (0)