I Asked It to Document My Projects. It Outsourced the Job to Itself.

TL;DR: A small moment that told me more about where agent tooling was heading than any release note did.

Small thing, but it stuck with me.

I had a folder full of projects and no good summary of any of them. So I asked Claude Code to go into each project folder and write up a summary document. Straightforward chore — the kind of thing you put off for six months and then do badly in one sitting.

It came back with:

Now launching parallel agents to survey and generate PROJECT_SUMMARY.md for every project.

It had decided, without being asked, that this was a job for several workers rather than one. So it spun up parallel agents, gave each one a project, and had them work simultaneously.

It outsourced the job. To itself.

Why this landed

I’ve spent my career around systems that scale by adding workers, and the hard part was never the idea. It was the plumbing — dispatch, coordination, collecting results, handling the one that fails. That’s where the effort goes.

Watching a tool make that decision on its own, correctly, for a task I’d framed as a single chore, was the moment a particular door visibly opened. Not because parallelism is novel. Because the decision to parallelize had moved down a layer, into the thing doing the work.

The practical read

The lesson I took wasn’t “wow, parallel agents.” It was about how I frame requests.

I’d asked for the chore the way I’d have done it: one project, then the next, then the next. The tool saw past my framing to the actual structure of the work — a set of independent tasks with no ordering constraint — and treated it accordingly.

Which suggests a small discipline worth having: describe the goal, not the sequence. If I’d written “first do project A, then project B,” I’d have gotten exactly that, serially, and never known I’d left anything on the table. My instinct to specify the order was a habit from an era when the order was mine to manage.

I catch myself doing that constantly. Explaining how when I only needed to explain what, and quietly capping the result at my own imagination of the method.

The summaries, incidentally

Were fine. Genuinely useful, and I still refer to them.

But I remember the dispatch line, not the documents. Sometimes the thing you learn from a chore has nothing to do with the chore.

The projects, experience and opinions here are mine. AI helped me turn my notes and build records into this piece and polished it for Cairoglyphics.ai.